codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 232 "Gen. Jnl.-Post+Print"

Base Application · Microsoft.Finance.GeneralLedger.Posting

Across versions

  1. BC23present
  2. BC241 procedures added, 1 events added
  3. BC25-30unchanged

Neighbourhood 6 connected objects and pages

Table 81 "Gen. Journal Line" (relates to)Gen. Journal LineCodeunit 13 "Gen. Jnl.-Post Batch" (calls, 2 links)Gen. Jnl.-Post BatchCodeunit 1373 "Batch Posting Print Mgt." (calls)Batch Posting Print Mgt.Codeunit 250 "Gen. Jnl.-Post via Job Queue" (calls)Gen. Jnl.-Post via Job QueueCodeunit 27 "Confirm Management" (calls)Confirm ManagementCodeunit 9080 "Journal Errors Mgt." (calls)Journal Errors Mgt.

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.GeneralLedger.Posting · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Gen. Journal Line

Events published

  • OnAfterPostJournalBatch(var GenJournalLine: Record "Gen. Journal Line") (integration): Integration event raised after successfully posting journal batch operations. Enables post-processing or cleanup after journal lines have been posted.
  • OnAfterConfirmPostJournalBatch(var GenJournalLine: Record "Gen. Journal Line"; var IsHandled: Boolean) (integration): Integration event raised after confirming journal batch posting with the user. Enables modification of confirmation behavior or additional validation after user confirmation.
  • OnBeforePostJournalBatch(var GenJournalLine: Record "Gen. Journal Line"; var HideDialog: Boolean) (integration): Integration event raised before starting journal batch posting operations. Enables custom validation, preprocessing, or dialog suppression before posting begins.
  • OnGenJnlLineSetFilter(var GenJournalLine: Record "Gen. Journal Line") (integration): Integration event raised when applying filters to journal lines during posting operations. Enables customization of journal line filtering logic or addition of custom filter criteria.
  • OnCodeOnBeforeLinesSuccessfullyPostedMessage(GenJournalLine: Record "Gen. Journal Line"; var IsHandled: Boolean) (integration): Integration event raised before displaying successful posting messages to the user. Enables customization or suppression of standard posting success notifications.
  • OnAfterOnRun(var GenJournalLine: Record "Gen. Journal Line") (integration): Integration event raised after completing the OnRun trigger processing. Enables final cleanup or logging operations after journal posting and printing completion.
  • OnBeforePrintJournalBatch(var GenJournalLine: Record "Gen. Journal Line"; var IsHandled: Boolean) + BC24 (integration): Integration event raised before printing journal batch reports. Enables custom print handling or suppression of standard journal batch printing.

Procedures

2 local procedures, no public ones.

Triggers

OnRun

Relations

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.

Countries that replace it

ES

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "Gen. Jnl.-Post+Print"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources