Codeunit 179 "Reversal-Post"
Base Application · Microsoft.Finance.GeneralLedger.Reversal
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Reversal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Reversal Entry |
Events published
OnBeforeGLRegPostingReportPrint(var ReportID: Integer; ReqWindow: Boolean; SystemPrinter: Boolean; var GLRegister: Record "G/L Register"; var Handled: Boolean)(integration): Integration event raised before printing the G/L register posting report, allowing customization of report settings.OnBeforeOnRun(var ReversalEntry: Record "Reversal Entry")(integration): Integration event raised before starting the reversal posting process, allowing preprocessing of reversal entries.OnRunOnBeforeDeleteAll(var ReversalEntry: Record "Reversal Entry"; Number: Integer)(integration): Integration event raised before deleting reversal entries after successful posting.OnRunOnAfterConfirm(var ReversalEntry: Record "Reversal Entry"; var Handled: Boolean; PrintRegister: Boolean; HideDialog: Boolean)(integration): Integration event raised after user confirmation, allowing custom handling of the reversal process.OnRunOnAfterCreateTxt(PrintRegister: Boolean; var Txt: Text[1024]; WarningText: Text[250])(integration): Integration event raised after creating confirmation text, allowing customization of user messages.OnRunOnBeforeCheckEntries(var ReversalEntry: Record "Reversal Entry")(integration): Integration event raised before validating reversal entries, allowing custom pre-validation logic.
Procedures
SetPrint(NewPrintRegister: Boolean): Sets whether to print the G/L register after posting reversal entries.SetHideDialog(NewHideDialog: Boolean): Sets whether to hide confirmation dialogs during reversal posting.
Triggers
OnRun
Relations
- runs on Table 179 “Reversal 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 17 “Gen. Jnl.-Post Reverse” (1 call:
OnRun → Reverse)
Called by
- Table 179 “Reversal Entry” (3 calls:
ReverseEntries → (object),ReverseEntries → SetHideDialog,ReverseEntries → SetPrint) - Page 183 “Reverse Transaction Entries” (2 calls:
Post → (object),Post → SetPrint)
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: "Reversal-Post"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.