XMLport 1000 "SEPA CT pain.001.001.03"
Base Application · Microsoft.Bank.DirectDebit
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Bank.DirectDebit · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | SEPA CT pain.001.001.03 |
Events published
OnSpecifyRemittanceTextSeparatorText(var SeparatorText: Text)(integration)OnBeforePassVariableRmtInf(PaymentExportData: Record "Payment Export Data"; var RemittanceText: Text; var IsHandled: Boolean)(integration)
Procedures
4 local procedures, no public ones.
Triggers
OnPreXmlPort
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 8703 “Feature Telemetry” (2 calls:
OnPreXmlPort → LogUptake,OnPreXmlPort → LogUsage) - Codeunit 1220 “SEPA CT-Export File” (1 call:
OnPreXmlPort → FeatureName) - Codeunit 1221 “SEPA CT-Fill Export Buffer” (1 call:
InitData → FillExportBuffer)
Countries that replace it
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: "xmlport", object_name: "SEPA CT pain.001.001.03"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.