Codeunit 1211 "Payment Export Gen. Jnl Check"

Base Application · Microsoft.Bank.Payment · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnPaymentExportGenJnlCheck(var GenJournalLine: Record "Gen. Journal Line"; var Handled: Boolean) (integration): Integration event that allows customization of payment export validation logic. This event is raised during general journal line validation to allow external extensions to add custom validation rules.

Procedures

• AddFieldEmptyError(var GenJnlLine: Record "Gen. Journal Line"; TableCaption2: Text; FieldCaption: Text; KeyValue: Text): Adds a field empty error to the payment file error log for a general journal line.
• AddBatchEmptyError(var GenJnlLine: Record "Gen. Journal Line"; FieldCaption: Text; KeyValue: Variant): Adds a batch-related empty field error to the payment file error log for a general journal line.

Plus 2 local procedures.

Triggers

OnRun

Relations

• runs on Table 81 “Gen. Journal Line”

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.

• Codeunit 20107 “AMC Bank Exp. CT Valid.” (3 calls: CheckIsoCodeValues → AddFieldEmptyError, OnRun → (object), OnRun → AddFieldEmptyError)
• Codeunit 1206 “Pmt Export Mgt Gen. Jnl Line” (1 call: CheckGenJnlLine → (object))
• Codeunit 1272 “Exp. Validation Gen. Jnl.” (1 call: OnRun → (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: "codeunit", object_name: "Payment Export Gen. Jnl Check"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.