Codeunit 2581 "Dim Correction Run"

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

Properties

Events published

• OnAfterUpdateGLEntry(var GLEntry: Record "G/L Entry"; var TempDimCorrectionSetBuffer: Record "Dim Correction Set Buffer"; var Result: Boolean; DimensionCorrectionEntryNo: Integer; var TempInvalidatedDimCorrection: Record "Invalidated Dim Correction" temporary) (integration): Integration event raised after updating a G/L entry during dimension correction processing.
• OnUpdateGLEntryOnAfterUpdateGlobalDimFromDimSetID(var GLEntry: Record "G/L Entry") (integration): Integration event raised after updating global dimensions from dimension set ID.

Procedures

• RunDimensionCorrection(var DimensionCorrection: Record "Dimension Correction"): Processes dimension correction by updating all affected G/L entries with new dimension values.

Plus 3 local procedures.

Triggers

OnRun

Relations

• runs on Table 472 “Job Queue Entry”

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 2580 “Dimension Correction Mgt” (6 calls: RunDimensionCorrection → GenerateSupportingTables, RunDimensionCorrection → ScheduleUpdateAnalysisViews, RunDimensionCorrection → SetStatusInProgress, …)
• Codeunit 408 “DimensionManagement” (1 call: UpdateGLEntry → UpdateGlobalDimFromDimSetID)

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