Codeunit 5274 "Create Shipping Data"

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

Procedures

• DHL(): Code[10]
• Fedex(): Code[10]
• OwnLog(): Code[10]
• UPS(): Code[10]
• CFR(): Code[10]
• CIF(): Code[10]
• CIP(): Code[10]
• CPT(): Code[10]
• DAF(): Code[10]
• DDP(): Code[10]
• DDU(): Code[10]
• DELIVERY(): Code[10]
• DEQ(): Code[10]
• DES(): Code[10]
• EXW(): Code[10]
• FAS(): Code[10]
• FCA(): Code[10]
• FOB(): Code[10]
• PICKUP(): Code[10]
• OverNight(): Code[10]
• NextDay(): Code[10]
• Standard(): Code[10]

Plus 3 local procedures.

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 5182 “Contoso Shipping” (3 calls: InsertShipmentMethod → InsertShipmentMethod, InsertShippingAgent → InsertShippingAgent, InsertShippingAgentService → InsertShippingAgentService)

Called by

• Codeunit 5418 “Create Sales Document” (4 calls: CreateOpenSalesDocuments → DHL, CreateOpenSalesDocuments → Fedex, CreateOpenSalesDocuments → NextDay, …)
• Codeunit 5692 “Create Extended Sales Document” (4 calls: CreateOpenSalesDocuments → DHL, CreateOpenSalesDocuments → Fedex, CreateOpenSalesDocuments → OverNight, …)
• Codeunit 5203 “Foundation Module” (1 call: CreateSetupData → (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 Shipping Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.