Codeunit 1212 "Pmt. Export Vend. Ledger Check"

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

Properties

Events published

• OnPmtExportVendorLedgerCheck(var VendorLedgerEntry: Record "Vendor Ledger Entry") (integration): Integration event that allows customization of vendor ledger entry validation logic for payment export. This event is raised during vendor ledger entry validation to allow external extensions to add custom validation rules.
• OnCheckEmptyPmtInfoVendorLedgerEntry(var VendorLedgerEntry: Record "Vendor Ledger Entry"; var Handled: Boolean) (integration): Integration event that allows customization of payment information validation for vendor ledger entries. This event is raised during empty payment information checks to enable custom validation logic.

Procedures

7 local procedures, no public ones.

Triggers

OnRun

Relations

• runs on Table 25 “Vendor Ledger Entry”

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 1207 “Pmt Export Mgt Vend Ledg Entry” (1 call: ExportVendorPaymentFile → (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: "Pmt. Export Vend. Ledger Check"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.