Codeunit 5295 "Create Payment Method"

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

Procedures

• Account(): Code[10]
• Bank(): Code[10]
• Bnkconvdom(): Code[10]
• Bnkconvint(): Code[10]
• Card(): Code[10]
• Cash(): Code[10]
• Check(): Code[10]
• Giro(): Code[10]
• Intercom(): Code[10]
• Multiple(): Code[10]
• PayPal(): Code[10]

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” (1 call: OnRun → Cash)
• Codeunit 5569 “Contoso Payments” (1 call: OnRun → InsertBankPaymentMethod)

Called by

• Codeunit 5259 “Create Sust. Purchase” (2 calls: CreatePurchaseInvoiceWithGL → Cash, CreatePurchaseInvoiceWithItem → Cash)
• Codeunit 5319 “Create Vendor Template” (2 calls: OnRun → Bank, OnRun → Cash)
• Codeunit 5562 “Create Customer Template” (2 calls: OnRun → Bank, OnRun → Cash)
• Codeunit 5418 “Create Sales Document” (1 call: CreateSalesInvoicesToPost → Cash)
• Codeunit 5420 “Create Purchase Document” (1 call: OnRun → Cash)
• Codeunit 5635 “Bank Module” (1 call: CreateSetupData → (object))
• Codeunit 5688 “Create Extended Purch Document” (1 call: OnRun → Cash)
• Codeunit 5692 “Create Extended Sales Document” (1 call: CreateSalesInvoicesToPost → Cash)

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 Payment Method"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.