Codeunit 440 "IC Setup Diagnostics"

Base Application · Microsoft.Intercompany.Setup · BC23-30 · source at ea08af5e · facts from BC29

Procedures

• GetPartnerSetupId(): Code[20]: Returns the identifier used for partner setup diagnostic category.
• InsertPartnerSetupDiagnostics(var TempParentSetupDiagnostic: Record "Intercompany Setup Diagnostic" temporary; var TempChildrenSetupDiagnostic: Record "Intercompany Setup Diagnostic" temporary): Validates intercompany partner configuration and generates diagnostic findings. Checks partner setup completeness and configuration consistency.
• InsertICPartnerPartnerSetupDiagnostics(ICPartner: Record "IC Partner"; var TempChildrenSetupDiagnostic: Record "Intercompany Setup Diagnostic" temporary; var Status: Option): Validates specific intercompany partner configuration and generates diagnostic findings. Checks partner account setup, connection details, and configuration consistency.
• GetMappingSetupId(): Code[20]: Returns the identifier used for mapping setup diagnostic category.
• InsertMappingSetupDiagnostics(var ParentSetupDiagnostic: Record "Intercompany Setup Diagnostic" temporary; var ChildrenSetupDiagnostic: Record "Intercompany Setup Diagnostic" temporary): Validates intercompany chart of accounts and G/L account mappings. Checks mapping completeness and configuration requirements for account synchronization.
• UpdateStatus(var OldStatus: Option; NewStatus: Option): Updates diagnostic status with higher severity level when new issues are found. Ensures overall status reflects most severe diagnostic finding.

Plus 5 local procedures.

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.

• Page 9051 “Intercompany Setup Diagnostics” (4 calls: OnInit → InsertMappingSetupDiagnostics, OnInit → InsertPartnerSetupDiagnostics, SetupStyleExprs → GetMappingSetupId, …)

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