Codeunit 5207 "Create Location"

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

Procedures

• EastLocation(): Code[10]
• MainLocation(): Code[10]
• OutLogLocation(): Code[10]
• OwnLogLocation(): Code[10]
• WestLocation(): Code[10]

Plus 2 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 5699 “Contoso Inventory” (2 calls: CreateLocation → InsertLocation, CreateTransferRoute → InsertTransferRoute)

Called by

• Codeunit 5381 “Create Transfer Orders” (5 calls: OnRun → EastLocation, OnRun → MainLocation, OnRun → OutLogLocation, …)
• Codeunit 5387 “Create Inventory Posting Setup” (5 calls: UpdateInventoryPostingSetup → EastLocation, UpdateInventoryPostingSetup → MainLocation, UpdateInventoryPostingSetup → OutLogLocation, …)
• Codeunit 5420 “Create Purchase Document” (3 calls: OnRun → EastLocation, OnRun → MainLocation, OnRun → WestLocation)
• Codeunit 4787 “Create Whse Location” (1 call: TransitLocation → OwnLogLocation)
• Codeunit 4790 “Create Common Location” (1 call: MainLocation → MainLocation)
• Codeunit 5680 “Inventory Module” (1 call: CreateMasterData → (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 Location"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.