Codeunit 234 "Gen. Jnl.-B.Post+Print"
Base Application · Microsoft.Finance.GeneralLedger.Posting
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Posting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Gen. Journal Batch |
Events published
OnAfterPostJournalBatch(var GenJournalBatch: Record "Gen. Journal Batch")(integration): Integration event raised after successfully posting a journal batch, before printing operations begin. Enables custom processing or validation after posting but before document printing.OnBeforePostJournalBatch(var GenJournalBatch: Record "Gen. Journal Batch"; var HideDialog: Boolean)(integration): Integration event raised before starting journal batch posting operations. Enables custom validation, preprocessing, or dialog suppression before posting begins.
Procedures
JournalWithPostingErrors(): Boolean: Returns whether any journal batch encountered posting errors during the batch posting and printing process.
Plus 1 local procedures.
Triggers
OnRun
Relations
- runs on Table 232 “Gen. Journal Batch”
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 13 “Gen. Jnl.-Post Batch” (1 call:
Code → (object)) - Codeunit 1373 “Batch Posting Print Mgt.” (1 call:
Code → PrintJournal) - Codeunit 230 “GenJnlManagement” (1 call:
Code → GetJournalSimplePageModePreference) - Codeunit 250 “Gen. Jnl.-Post via Job Queue” (1 call:
Code → EnqueueGenJrnlLineWithUI) - Codeunit 27 “Confirm Management” (1 call:
Code → GetResponseOrDefault)
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.-B.Post+Print"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.