Codeunit 5319 "Create Vendor Template"

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

Procedures

• VendorCompany(): code[20]
• VendorEUCompany(): code[20]
• VendorPerson(): 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 5206 “Create Payment Terms” (3 calls: OnRun → PaymentTermsCOD, OnRun → PaymentTermsDAYS14, OnRun → PaymentTermsM8D)
• Codeunit 5252 “Create Posting Groups” (2 calls: OnRun → DomesticPostingGroup, OnRun → EUPostingGroup)
• Codeunit 5295 “Create Payment Method” (2 calls: OnRun → Bank, OnRun → Cash)
• Codeunit 5473 “Create VAT Posting Groups” (2 calls: OnRun → Domestic, OnRun → EU)
• Codeunit 5568 “Create Vendor Posting Group” (2 calls: OnRun → Domestic, OnRun → EU)
• Codeunit 5661 “Contoso Vendor Templ” (1 call: OnRun → InsertVendorTempl)

Called by

• Codeunit 5394 “Purchase 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 Vendor Template"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.