codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 1231 "SEPA DD-Fill Export Buffer"

Base Application · Microsoft.Bank.DirectDebit

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 1226 "Payment Export Data" (relates to)Payment Export DataCodeunit 1232 "SEPA DD-Prepare Source" (calls)SEPA DD-Prepare SourceXMLport 1010 "SEPA DD pain.008.001.02" (calls)SEPA DD pain.008.001.02XMLport 1011 "SEPA DD pain.008.001.08" (calls)SEPA DD pain.008.001.08

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.DirectDebit · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Payment Export Data
Permissions TableData “Payment Export Data” = rimd

Events published

  • OnBeforeGetDDExportImportSetup(BankAccount: Record "Bank Account"; var BankExportImportSetup: Record "Bank Export/Import Setup"; var IsHandled: Boolean) (integration): Integration event that allows customization of the direct debit export/import setup retrieval process. Subscribers can provide alternative logic for determining the appropriate setup configuration.
  • OnBeforeInsertPaymentExportData(var PaymentExportData: Record "Payment Export Data"; var TempDirectDebitCollectionEntry: Record "Direct Debit Collection Entry" temporary) (integration): Integration event that allows customization of payment export data before insertion. Subscribers can modify export data fields or add additional validation logic.

Procedures

  • FillExportBuffer(var DirectDebitCollectionEntry: Record "Direct Debit Collection Entry"; var PaymentExportData: Record "Payment Export Data"): Fills the payment export data buffer with information from direct debit collection entries. Validates entries through the configured check codeunit, retrieves mandate and customer information, and formats data according to SEPA direct debit standards for XML export processing.

Plus 2 local procedures.

Triggers

OnRun

Relations

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.

Called by

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: "SEPA DD-Fill Export Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources