reportFinanceofficial - Microsoftderived - from the source, no model text

Report 91 "Export Consolidation"

Base Application · Microsoft.Finance.Consolidation

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Codeunit 439 "Export F/O Consolidation" (calls, 3 links)Export F/O ConsolidationCodeunit 411 "Dimension Buffer Management" (calls, 2 links)Dimension Buffer ManagementCodeunit 419 "File Management" (calls, 2 links)File ManagementCodeunit 432 "Consolidate" (calls, 2 links)ConsolidateCodeunit 4030 "Client Type Management" (calls)Client Type Management

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.

Base Application · Microsoft.Finance.Consolidation · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Export Consolidation
UsageCategory Tasks
ApplicationArea Suite

Events published

  • OnAfterGLEntryOnAfterGetRecord(var GLEntry: Record "G/L Entry"; var TempSelectedDim: Record "Selected Dimension" temporary) (integration): Integration event raised after processing G/L Entry record during consolidation export. Enables custom post-processing of G/L entry data and dimension handling.
  • OnBeforeGLEntryOnAfterGetRecord(var GLEntry: Record "G/L Entry"; var TempSelectedDim: Record "Selected Dimension" temporary) (integration): Integration event raised before processing G/L Entry record during consolidation export. Enables custom pre-processing of G/L entry data and dimension selection.

Procedures

  • InitializeRequest(NewFileFormat: Option; NewFileName: Text): Initializes export parameters for consolidation data export processing. Sets file format and output filename for the consolidation export operation.

Plus 7 local procedures.

Triggers

OnInitReport, 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.

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

Evidence 1 sources