Codeunit 1220 "SEPA CT-Export File"

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

Properties

Events published

• OnBeforeBLOBExport(var TempBlob: Codeunit "Temp Blob"; CreditTransferRegister: Record "Credit Transfer Register"; UseComonDialog: Boolean; var FieldCreated: Boolean; var IsHandled: Boolean) (integration): Integration event raised before BLOB export operation during credit transfer file creation. Enables custom file handling or modification of export parameters.
• OnBeforeExtport(var GenJnlLine: Record "Gen. Journal Line"; XMLPortID: Integer; var Result: Boolean; var IsHandled: Boolean) (integration): Integration event raised before starting SEPA credit transfer export process. Enables custom export handling or validation before standard processing.

Procedures

• FeatureName(): Text + BC24 (internal)
• Export(var GenJnlLine: Record "Gen. Journal Line"; XMLPortID: Integer): Boolean: Exports SEPA credit transfer data from general journal lines to XML format. Creates credit transfer register entry and manages file output to server or client.
• EnableExportToServerFile(): Enables export to server file instead of client download.

Plus 1 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 4100 “Temp Blob” (2 calls: Export → CreateOutStream, SetCreditTransferRegisterToFileCreated → ToRecordRef)
• Codeunit 1278 “Exp. User Feedback Gen. Jnl.” (1 call: OnRun → SetExportFlagOnGenJnlLine)
• Codeunit 419 “File Management” (1 call: Export → BLOBExport)

Called by

• XMLport 1000 “SEPA CT pain.001.001.03” (1 call: OnPreXmlPort → FeatureName)
• XMLport 1001 “SEPA CT pain.001.001.09” (1 call: OnPreXmlPort → FeatureName)

Countries that replace it

NL

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