Report 6250 "Auto Posting Errors"
Base Application · Microsoft.Finance.GeneralLedger.Journal
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Finance.GeneralLedger.Journal · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Auto Posting Errors |
Events published
OnBeforeOnAfterGetGenJnlLinePostingDate(var GenJournalLine: Record "Gen. Journal Line"; var ErrorText: array[50] of Text[250]; var ErrorCounter: Integer; var IsHandled: Boolean)(integration): Integration event that occurs before validating posting date after retrieving general journal line data. Allows custom validation of posting date logic and error message handling.OnBeforeCheckPostingDateFAFields(var GenJnlLine: Record "Gen. Journal Line"; var ErrorText: array[50] of Text[250]; var ErrorCounter: Integer; var IsHandled: Boolean)(integration): Integration event that occurs before checking posting date and fixed asset field validation. Allows custom handling of posting date validation for fixed asset related journal lines.
Procedures
TestPostingType(): Tests posting type consistency between journal line account types and document types. Validates that customer accounts are not used with purchase documents and vendor accounts are not used with sales documents.InitializeRequest(NewShowDim: Boolean): Initializes the report request parameters for controlling dimension display. Sets up whether dimensions should be shown in the error report output.
Plus 35 local procedures.
Called by
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.
- Page 6250 “Data Sync Status” (1 call:
PostingErrors → (object))
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: "report", object_name: "Auto Posting Errors"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.