Codeunit 5568 "Create Vendor Posting Group"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Purchases
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 6 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Purchases · BC29-30 · source at ea08af5e · facts from BC29
Procedures
Domestic(): Code[20]EU(): Code[20]Foreign(): Code[20]
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 5208 “Create G/L Account” (9 calls:
OnRun → ApplicationRounding,OnRun → InvoiceRounding,OnRun → OtherCostsofOperations, …) - Codeunit 5132 “Contoso Posting Group” (1 call:
OnRun → InsertVendorPostingGroup)
Called by
- Codeunit 5539 “Create Vendor” (3 calls:
OnRun → Domestic,OnRun → EU,OnRun → Foreign) - Codeunit 5319 “Create Vendor Template” (2 calls:
OnRun → Domestic,OnRun → EU) - Codeunit 5256 “Create Sust. Vendor” (1 call:
OnRun → Domestic) - Codeunit 5394 “Purchase 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 Vendor Posting Group"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.