Report 90 "Import Consolidation from DB"

Base Application · Microsoft.Finance.Consolidation · captioned “Consolidation Report (same environment)” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnCheckConsolidDatesOnBeforeConfirmConsolidationDates(var IsHandled: Boolean; StartDate: Date; EndDate: Date) + BC24 (integration): Integration event raised before confirming consolidation dates during database import validation. Enables custom date validation logic and confirmation handling during consolidation processing.

Procedures

• SetConsolidationProcessParameters(ConsolidationProcess: Record "Consolidation Process"; BusinessUnit: Record "Business Unit") + BC27 − BC27 (internal)
• GetConsolidate(var ConsolidateToGet: Codeunit Consolidate) + BC27 (internal)

Plus 7 local procedures.

Triggers

OnPostReport, OnPreReport

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 27 “Confirm Management” (2 calls: CheckConsolidDates → GetResponseOrDefault, CheckDatesToFiscalYear → GetResponseOrDefault)
• Page 456 “No. Series” (1 call: OnPreReport → (object))
• Report 17 “Consolidated Trial Balance” (1 call: OnPostReport → (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: "report", object_name: "Import Consolidation from DB"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.