Report 5707 "Batch Post Transfer Orders"

Base Application · Microsoft.Inventory.Transfer · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnCodeOnBeforePostTransferOrder(var TransferHeader: Record "Transfer Header"; var TransferOrderPost: Enum "Transfer Order Post"; var IsHandled: Boolean) (integration)
• OnRunPostBatchTransferOrderOnAfterPost(var TransferHeader: Record "Transfer Header"; var TransferOrderPost: Enum "Transfer Order Post"; var ErrorMessageHandler: Codeunit "Error Message Handler") + BC25 (integration)

Procedures

• RunPostBatchTransferOrder(var TransferHeader: Record "Transfer Header") (internal)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 28 “Error Message Management” (3 calls: RunPostBatchTransferOrder → Activate, RunPostBatchTransferOrder → LogErrorMessage, RunPostBatchTransferOrder → PushContext)
• Codeunit 29 “Error Message Handler” (2 calls: RunPostBatchTransferOrder → HasErrors, RunPostBatchTransferOrder → NotifyAboutErrors)
• Codeunit 5706 “TransferOrder-Post (Yes/No)” (2 calls: RunPostBatchTransferOrder → (object), RunPostBatchTransferOrder → SetParameters)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "report", object_name: "Batch Post Transfer Orders"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.