Codeunit 413 "AnalysisViewEntryToGLEntries"

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

Events published

• OnGetGLEntriesOnAfterGLEntrySetFilters(var GLEntry: Record "G/L Entry"; var AnalysisView: Record "Analysis View"; var AnalysisViewEntry: Record "Analysis View Entry") (integration): Integration event raised after setting filters on G/L Entry record during drill-down process. Enables custom filtering logic for G/L entries retrieved from analysis view entries.
• OnAfterGetGLEntryIfDateCompressionNone(var AnalysisViewEntry: Record "Analysis View Entry"; var TempGLEntry: Record "G/L Entry" temporary) (integration): Integration event raised after retrieving G/L entry when date compression is disabled. Allows custom processing of G/L entries in non-compressed analysis view scenarios.
• OnAfterGetGLEntries(var AnalysisViewEntry: Record "Analysis View Entry"; var TempGLEntry: Record "G/L Entry" temporary) (integration): Integration event raised after completing G/L entry retrieval process. Enables final processing or validation of retrieved G/L entries from analysis view drill-down.
• OnGetGLEntriesOnBeforeCopyGLEntries(var AnalysisViewEntry: Record "Analysis View Entry"; var IsHandled: Boolean) (integration): Integration event raised before copying G/L entries during analysis view drill-down process. Allows custom handling or skipping of standard G/L entry retrieval logic.

Procedures

• GetGLEntries(var AnalysisViewEntry: Record "Analysis View Entry"; var TempGLEntry: Record "G/L Entry"): Retrieves G/L entries that correspond to an analysis view entry for drill-down functionality. Applies appropriate filters based on analysis view configuration and dimension settings.
• GetCFLedgEntries(var AnalysisViewEntry: Record "Analysis View Entry"; var CFForecastEntry: Record "Cash Flow Forecast Entry"): Retrieves cash flow forecast entries that correspond to an analysis view entry for drill-down functionality. Applies appropriate filters based on analysis view configuration and cash flow dimension settings.
• DimEntryOK(DimSetID: Integer; Dim: Code[20]; DimValue: Code[20]): Boolean: Validates whether a dimension set entry matches expected dimension value for analysis view filtering. Checks if the dimension value in a dimension set matches the required value for analysis view drill-down.
• GetGlobalDimValue(GlobalDim: Code[20]; var AnalysisViewEntry: Record "Analysis View Entry"; var GlobalDimValue: Code[20]): Boolean: Retrieves global dimension value from analysis view entry for specified dimension code. Maps analysis view dimension codes to corresponding dimension values for filtering purposes.

Plus 1 local procedures.

Triggers

OnRun

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 410 “Update Analysis View” (2 calls: GetCFLedgEntries → DimSetIDInFilter, GetGLEntries → DimSetIDInFilter)

Called by

• Codeunit 2621 “Stat. Acc. Analysis View Mgt.” (2 calls: GetStatisticalLedgerEntry → DimEntryOK, GetStatisticalLedgerEntry → GetGlobalDimValue)
• Table 365 “Analysis View Entry” (2 calls: DrillDown → GetCFLedgEntries, DrillDown → GetGLEntries)
• Report 28 “Dimensions - Detail” (1 call: PrintDetail → GetGLEntries)
• Report 852 “Cash Flow Dimensions - Detail” (1 call: PrintDetail → GetCFLedgEntries)

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