Codeunit 4796 "Create Whse Orders"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Warehousing · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• CreateOrdersScenarioSilver(): Simple Logistics Scenario - Receiving / Shipping Multiple Orders with Whse. Receipt / Shipment
• CreateOrdersScenarioWhite(): Advanced Logistics Scenario - Crossdocking, Breakbulk. Movement with Advanced Warehousing

Triggers

OnRun

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 4781 “Contoso Purchase” (4 calls: CreateOrdersScenarioSilver → InsertPurchaseHeader, CreateOrdersScenarioSilver → InsertPurchaseLineWithItem, CreateOrdersScenarioWhite → InsertPurchaseHeader, …)
• Codeunit 5124 “Contoso Sales” (4 calls: CreateOrdersScenarioSilver → InsertSalesHeader, CreateOrdersScenarioSilver → InsertSalesLineWithItem, CreateOrdersScenarioWhite → InsertSalesHeader, …)
• Codeunit 5142 “Contoso Utilities” (3 calls: CreateOrdersScenarioSilver → AdjustDate, CreateOrdersScenarioWhite → AdjustDate, CreateOrdersScenarioWhite → AdjustPrice)
• Codeunit 5130 “Create Common Unit Of Measure” (1 call: CreateOrdersScenarioWhite → Bag)

Called by

• Codeunit 5140 “Warehouse Module” (1 call: CreateTransactionalData → (object))

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: "codeunit", object_name: "Create Whse Orders"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.