Codeunit 5183 "Contoso Allocation Account"

ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers · BC29-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• SetOverwriteData(Overwrite: Boolean)
• InsertAllocationAccount(AllocationAccountNo: Code[20]; Name: Text[100]; AccountType: Option; DocumentLineSplit: Option)
• InsertAllocationAccountDistribution(AllocationAccountNo: Code[20]; LineNo: Integer; AccountType: Option; Share: Decimal; Percent: Decimal; DesinationAccountType: Enum "Destination Account Type"; DestinationAccountNo: Code[20]; GlobalDimension1Code: Code[20]; GlobalDimension2Code: Code[20])

Called by

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 5426 “Create Allocation Account” (2 calls: OnRun → InsertAllocationAccount, OnRun → InsertAllocationAccountDistribution)

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: "Contoso Allocation Account"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.