codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 1208 "Pmt Export Mgt Cust Ledg Entry"

Base Application · Microsoft.Bank.Payment

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 1210 "Payment Export Mgt" (calls, 5 links)Payment Export MgtCodeunit 103 "Cust. Entry-Edit" (calls)Cust. Entry-EditCodeunit 1213 "Pmt. Export Cust. Ledger Check" (calls)Pmt. Export Cust. Ledger Check

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Permissions TableData “Cust. Ledger Entry” = rm

Events published

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

Procedures

  • ExportCustPaymentFileYN(var CustLedgerEntry: Record "Cust. Ledger Entry"): Exports customer payment file with user confirmation if entries were previously exported. This procedure prompts the user if re-exporting already exported entries.
  • ExportCustPaymentFile(var CustLedgerEntry: Record "Cust. Ledger Entry"): Exports customer payment file after validation without user prompts. This procedure validates and exports customer ledger entries for payment processing.
  • ExportCustLedgerEntry(var CustLedgerEntry: Record "Cust. Ledger Entry"): Processes customer ledger entries for export to payment file format. This procedure creates the data exchange entries and export file for customer payments.
  • PreparePaymentExportDataCLE(var TempPaymentExportData: Record "Payment Export Data" temporary; CustLedgerEntry: Record "Cust. Ledger Entry"; DataExchEntryNo: Integer; LineNo: Integer): Prepares payment export data from customer ledger entry information. This procedure converts customer ledger entry data into payment export format for refund file generation.
  • EnableExportToServerTempFile(SilentServerMode: Boolean; ServerFileExtension: Text[3]): Enables export of payment files to server temporary location. This procedure configures customer payment export to use server-side temporary files.
  • GetServerTempFileName(): Text[1024]: Gets the file name of the server temporary file used for customer payment export. This procedure returns the path to the temporary file created during customer 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.

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 Cust Ledg Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources