Codeunit 5387 "Create Inventory Posting Setup"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Inventory
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 5 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Inventory · BC29-30 · source at ea08af5e · facts from BC29
Procedures
UpdateInventoryPostingSetup()
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 5207 “Create Location” (5 calls:
UpdateInventoryPostingSetup → EastLocation,UpdateInventoryPostingSetup → MainLocation,UpdateInventoryPostingSetup → OutLogLocation, …) - Codeunit 5208 “Create G/L Account” (4 calls:
OnRun → ResaleItems,OnRun → ResaleItemsInterim,UpdateInventoryPostingSetup → ResaleItems, …) - Codeunit 5136 “Contoso Posting Setup” (2 calls:
OnRun → InsertInventoryPostingSetup,UpdateInventoryPostingSetup → InsertInventoryPostingSetup) - Codeunit 5229 “Create Inventory Posting Group” (2 calls:
OnRun → Resale,UpdateInventoryPostingSetup → Resale)
Called by
- Codeunit 5680 “Inventory Module” (2 calls:
CreateMasterData → UpdateInventoryPostingSetup,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 Inventory Posting Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.