Language: Deutsch · English
5.3 SEPA: From v1.2 to v2.0
Update from v1.2 to v2.0: dedicated Creditor/Debitor Reference attributes, a new SEPA Export File BO and the required data migrations.
HOW-TO INTEGRATORS STAND: JUL 2026 GILT FUER NUCLOS 4.2026.X
Auf dieser Seite
Machine-translated – under review
This page was machine-translated from German as a first draft and is currently under review. The authoritative source remains the German original (see the language switch above).
Notes on the background of the necessary adjustments
The following changes and extensions must be observed on an update:
- In version 2.0.0 the general reference attribute is replaced by the dedicated attributes "Creditor Reference" (for credit transfers) and "Debitor Reference" (for direct debits) (as described under prerequisites). The original attribute "Reference" is retained for now, but is obsolete and will be dropped in one of the future versions of the SEPA Nuclet; expected with version 2.2.0.
- In addition, the export files are stored in an additional business object ("SEPA Export File"). Up to now these files were held directly in the "SEPA Export".
Data migrations must be carried out for both changes if SEPA exports have already been performed in your system.
If you have been using an older version of the SEPA Nuclet in your application and an update to version 2.0.0 is pending, please observe the notes listed here.
5.3.1 Securing the adjustments in data sources (before Nuclet import)
- Please back up your data source for the dynamic business object "References2SEPAExport".
- After the Nuclet transfer, please replace the new dynamic business object "DebitorReferences2SEPAExport" with your previously backed-up data source.
5.3.2 Securing the adjustments in Java rules (before Nuclet import)
Please carry out the steps described in section 5.1.2.
5.3.3 Running the additional object import
Please carry out the steps described in section 4.2 for the newly created object import "SEPA Order Type".
5.3.4 Data migration (after Nuclet import)
After the Nuclet transfer, please run the following SQL statements on your database schema. The reason for this are the changes described above under "Notes on the background of the necessary adjustments".
Data migration for BO table "SEPA Export"
-- Anmerkung: "abcd_" steht für das tatsächliche Tabellenpräfix der Tabelle. -- Es entspricht dem Wert "Lokaler Identifizierer" im Nuclet-Managment des SEPA-Nuclets. -- -- Bitte führen Sie diese Anweisungen erst nach dem Import des SEPA-Nuclets v2.0.0 und den durchgeführten Objektimporten durch. UPDATE abcd_sepaexport SET intid_strordertype = (SELECT intid FROM abcd_sepaordertype WHERE strkey = 'DIRECT_DEBIT_INITIATION'); UPDATE abcd_sepaexport SET struid_nuclosprocess = (SELECT struid_strprocess FROM abcd_sepaordertype WHERE strkey = 'DIRECT_DEBIT_INITIATION');
Data migration for BO table "SEPA Transaction"
-- Anmerkung: "abcd_" steht für das tatsächliche Tabellenpräfix der Tabelle. -- Es entspricht dem Wert "Lokaler Identifizierer" im Nuclet-Managment des SEPA-Nuclets. -- -- Bitte führen Sie diese Anweisung erst nach dem Import des SEPA-Nuclets v2.0.0 durch. UPDATE abcd_sepatransaction SET intid_strdebitorreference = intid_strreference;
Data migration for BO table "SEPA Export File"
-- Anmerkung: "abcd_" steht für das tatsächliche Tabellenpräfix der Tabelle.
-- Es entspricht dem Wert "Lokaler Identifizierer" im Nuclet-Managment des SEPA-Nuclets.
--
-- Bitte führen Sie diese Anweisung direkt nach dem Import des SEPA-Nuclets v2.0.0 durch.
INSERT INTO abcd_sepaexportfile (intid, strfilepath, strfile, intid_strordertype, intid_strsequencetype, strpaymentinformationid,
strmessageid, intid_strsepaexport, strnote, strmessageidnumber, datchanged, strchanged, datcreated, strcreated, intversion)
SELECT
nextval('idfactory'), strfilepath, strfile, intid_strordertype, null as "intid_strsequencetype", strpaymentinformationid,
strmessageid, intid, '' as "strnote", strmessageidnumber,
datchanged, strchanged, datcreated, strcreated, 0 as "intversion"
FROM
abcd_sepaexport;
5.3.5 Adjustments in Java rules (after Nuclet import)
- The class SEPALogic (or the concrete implementation of AbstractSEPALogic used in your case) has to be adapted to some changes and additions:
- class imports: PaymentType and SequenceType are independent classes from version 2.0.0.
- The method fetchPaymentReferences(SEPAExport) was renamed to fetchDirectDebitReferences(SEPAExport) and returns a list of objects of type AbstractDirectDebitReferenceWrapper
- Please refer to the description of the integration steps in section 4.8.3 for further changes.
- The ReferenceWrapper is to be replaced by a DebitorReferenceWrapper (see section 4.8.1)
- The PaymentReferenceWrapper is to be replaced by DirectDebitReferenceWrapper (see section 4.8.1)
- The PaymentReferenceFacade is to be replaced by DirectDebitReferenceFacade (see section 4.8.2)
Related pages
Überblick
Inhalte