Codeunit 1206 "Pmt Export Mgt Gen. Jnl Line"

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

Properties

Events published

• OnBeforeInsertPmtExportDataJnlFromGenJnlLine(var PaymentExportData: Record "Payment Export Data"; GenJournalLine: Record "Gen. Journal Line"; GeneralLedgerSetup: Record "General Ledger Setup") (integration): Integration event raised before inserting payment export data from general journal line. This event allows customization of payment export data before it is processed.
• OnBeforeCreateGenJnlDataExchLine(DataExch: Record "Data Exch."; GenJournalLine: Record "Gen. Journal Line"; LineNo: Integer; var LineAmount: Decimal; var TotalAmount: Decimal; var TransferDate: Date; var Handled: Boolean) (integration): Integration event raised before creating general journal data exchange line. This event allows customization of data exchange line creation for payment export.
• OnBeforePaymentExport(BalAccountNo: Code[20]; DataExchEntryNo: Integer; LineCount: Integer; TotalAmount: Decimal; TransferDate: Date; var Handled: Boolean) (integration): Integration event raised before payment export operation starts. This event allows customization of the payment export process before file generation.
• OnCheckGenJnlLine(GenJournalLine: Record "Gen. Journal Line") (integration): Integration event raised during general journal line validation for payment export. This event allows external extensions to perform additional validation on journal lines.

Procedures

• ExportJournalPaymentFileYN(var GenJnlLine: Record "Gen. Journal Line"): Exports journal payment file with user confirmation if lines were previously exported. This procedure prompts the user if re-exporting already exported journal lines.
• ExportJournalPaymentFile(var GenJnlLine: Record "Gen. Journal Line"): Exports journal payment file without user prompts. This procedure validates and exports general journal lines for payment processing.
• ExportGenJnlLine(var GenJnlLine: Record "Gen. Journal Line"; var CreditTransferRegister: Record "Credit Transfer Register"): Processes general journal lines for export to payment file format. This procedure creates data exchange entries and credit transfer entries for payment export.
• PreparePaymentExportDataJnl(var TempPaymentExportData: Record "Payment Export Data" temporary; GenJnlLine: Record "Gen. Journal Line"; DataExchEntryNo: Integer; LineNo: Integer): Prepares payment export data from general journal line information. This procedure populates payment export data with vendor, employee, and bank account details for payment processing.
• EnableExportToServerTempFile(SilentServerMode: Boolean; ServerFileExtension: Text[3]): Enables export to server temporary file with specified settings. This procedure configures payment export to save files on the server instead of client download.
• GetServerTempFileName(): Text[1024]: Retrieves the server temporary file name for payment export. This procedure returns the path of the temporary file created on the server during payment export.

Plus 3 local procedures.

Triggers

OnRun

Relations

• runs on Table 81 “Gen. Journal Line”

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: CreateGenJnlDataExchLine → CreatePaymentLines, EnableExportToServerTempFile → EnableExportToServerTempFile, ExportGenJnlLine → CreateDataExch, …)
• Codeunit 1211 “Payment Export Gen. Jnl Check” (1 call: CheckGenJnlLine → (object))
• Codeunit 1278 “Exp. User Feedback Gen. Jnl.” (1 call: ExportGenJnlLine → (object))

Countries that replace it

RU

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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 Gen. Jnl Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.