codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 5394 "Purchase Module"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Purchases

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 12 connected objects and pages

Codeunit 5193 "Contoso Demo Tool" (calls)Contoso Demo ToolCodeunit 5272 "Create Purchase Payable Setup" (calls)Create Purchase Payable SetupCodeunit 5313 "Create Vendor Bank Account" (calls)Create Vendor Bank AccountCodeunit 5319 "Create Vendor Template" (calls)Create Vendor TemplateCodeunit 5420 "Create Purchase Document" (calls)Create Purchase DocumentCodeunit 5443 "Create Over-Receipt Code" (calls)Codeunit 5539 "Create Vendor" (calls)Create VendorCodeunit 5568 "Create Vendor Posting Group" (calls)Create Vendor Posting GroupCodeunit 5622 "Create Return Reason" (calls)Create Return ReasonCodeunit 5663 "Create Purchase Dim. Value" (calls)Create Purchase Dim. ValueCodeunit 5666 "Post Transfer Data" (calls)Post Transfer DataCodeunit 5689 "Create Posted Purchase Data" (calls)

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Procedures

  • RunConfigurationPage()
  • GetDependencies(): List of [enum "Contoso Demo Data Module"]
  • CreateSetupData()
  • CreateMasterData()
  • CreateTransactionalData()
  • CreateHistoricalData()

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.

Implements

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

Evidence 1 sources