Report 92 "Import Consolidation from File"
Base Application · Microsoft.Finance.Consolidation
Across versions
- BC23-25present
- BC261 procedures added, 1 procedures changed
- BC27-28unchanged
- BC291 procedures removed
- BC30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Finance.Consolidation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Import Consolidation from File |
Procedures
SetParameters(NewFileFormat: Enum "Business Unit File Format"; NewFilePath: Text; NewGLDocNo: Code[20])+ BC26: Sets consolidation import parameters for file-based data processing. Configures file format, file path, and document number for consolidation import from file.SetGenJnlBatch(NewGenJnlBatch: Record "Gen. Journal Batch"): Sets general journal batch for consolidation import processing. Associates imported consolidation transactions with specific journal batch for posting.
Plus 1 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 432 “Consolidate” (8 calls:
OnPostReport → (object),OnPostReport → SetDocNo,OnPostReport → SetGenJnlBatch, …) - Codeunit 27 “Confirm Management” (1 call:
OnPreReport → GetResponseOrDefault) - Codeunit 419 “File Management” (1 call:
GetFileName → GetFileName)
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 File"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.