Codeunit 244 "Item Jnl.-B.Post+Print"
Base Application · Microsoft.Inventory.Posting
Across versions
- BC23-25present
- BC261 procedures added
- BC27-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Inventory.Posting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Item Journal Batch |
Events published
OnAfterPostJournalBatch(var ItemJournalBatch: Record "Item Journal Batch")(integration)OnBeforePostJournalBatch(var ItemJournalBatch: Record "Item Journal Batch"; var HideDialog: Boolean)(integration)OnBeforePrintItemRegister(ItemRegister: Record "Item Register"; ItemJnlTemplate: Record "Item Journal Template"; var IsHandled: Boolean)(integration)OnBeforePrintWhseRegister(WarehouseRegister: Record "Warehouse Register"; ItemJnlTemplate: Record "Item Journal Template"; var IsHandled: Boolean)(integration)
Procedures
JournalWithPostingErrors(): Boolean+ BC26
Plus 3 local procedures.
Triggers
OnRun
Relations
- runs on Table 233 “Item 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 23 “Item Jnl.-Post Batch” (3 calls:
Code → (object),Code → GetItemRegNo,Code → GetWhseRegNo) - 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: "Item Jnl.-B.Post+Print"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.