Codeunit 1207 "Pmt Export Mgt Vend Ledg Entry"

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

Properties

Events published

• OnBeforeInsertPmtExportDataJnlFromVendorLedgerEntry(var PaymentExportData: Record "Payment Export Data"; VendorLedgerEntry: Record "Vendor Ledger Entry"; GeneralLedgerSetup: Record "General Ledger Setup") (integration): Integration event that allows customization of payment export data before insertion from vendor ledger entries. This event enables modifications to payment export data during vendor payment file generation.
• OnBeforePaymentExportVendorLedgerEntry(BalAccountNo: Code[20]; DataExchEntryNo: Integer; LineCount: Integer; TotalAmount: Decimal; TransferDate: Date; var Handled: Boolean) (integration): Integration event that allows customization of vendor ledger entry payment export processing. This event enables custom handling of the payment export process for vendor entries.
• OnBeforeCreateVendLedgerDataExchLine(DataExch: Record "Data Exch."; VendorLedgerEntry: Record "Vendor Ledger Entry"; LineNo: Integer; var LineAmount: Decimal; var TotalAmount: Decimal; var TransferDate: Date; var Handled: Boolean) (integration): Integration event that allows customization of vendor ledger data exchange line creation. This event enables custom processing before creating data exchange lines for vendor payments.

Procedures

• ExportVendorPaymentFileYN(var VendorLedgerEntry: Record "Vendor Ledger Entry"): Exports vendor payment file with user confirmation if entries were previously exported. This procedure prompts the user if re-exporting already exported vendor entries.
• ExportVendorPaymentFile(var VendorLedgerEntry: Record "Vendor Ledger Entry"): Exports vendor payment file after validation without user confirmation. This procedure performs validation and exports vendor ledger entries for payment processing.
• ExportVendLedgerEntry(var VendorLedgerEntry: Record "Vendor Ledger Entry"): Processes vendor ledger entries for payment export and creates data exchange lines. This procedure handles the core export logic for vendor payment files.
• PreparePaymentExportDataVLE(var TempPaymentExportData: Record "Payment Export Data" temporary; VendorLedgerEntry: Record "Vendor Ledger Entry"; DataExchEntryNo: Integer; LineNo: Integer): Prepares payment export data from vendor ledger entry information. This procedure converts vendor ledger entry data into payment export format for file generation.
• EnableExportToServerTempFile(SilentServerMode: Boolean; ServerFileExtension: Text[3]): Enables export of payment files to server temporary location. This procedure configures the payment export to use server-side temporary files.
• GetServerTempFileName(): Text[1024]: Gets the file name of the server temporary file used for payment export. This procedure returns the path to the temporary file created during payment export.

Plus 4 local procedures.

Triggers

OnRun

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 1210 “Payment Export Mgt” (5 calls: CreateVendLedgerDataExchLine → CreatePaymentLines, EnableExportToServerTempFile → EnableExportToServerTempFile, ExportVendLedgerEntry → CreateDataExch, …)
• Codeunit 113 “Vend. Entry-Edit” (1 call: SetExportFlagOnVendorLedgerEntries → (object))
• Codeunit 1212 “Pmt. Export Vend. Ledger Check” (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 Mgt Vend Ledg Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.