The following entries have to be made in the code tables:
| Codetable | Code | Text |
|---|---|---|
| ACTTYP | SPA | SEPA Account |
| SRVTXT | SPA | Sepa |
| APFCLA | SPA | Sepa |
| CORTYP | SPA | Sepa |
An application form for SEPA has to be set up using the 'Maintaining Form Sets' (DBIAPF) transaction.
The SPA service then has to be integrated in a suitable position in the Workflow using 'Maintaining Service Order' (DBISRO).
Besides path and job details, the sender ID, creditor ID and the IBAN for returns have to be set up in the configuration panel for the SPA service in the Workflow Manager (MGRTSK).
SPASUP.INI and SPAOVR.INI files used to prepare messages in PrettyPrint format have to be stored in the INI directory.
On top of this, project-specific adjustments to the structure of messages and/or additional checks, etc. may be necessary.
If there are customer-specific checks of account numbers, these will have to be adapted to SEPA accounts if these account numbers are from external banks (i.e. where the party servicing the account is not the same as the bank's own party).
It is basically possible for a SEPA account number to be the same as an in-house account number. As account numbers have to be unique within an entity in DOKA, it is possible to identify account numbers from external banks by appending 'SPA' either before or after the actual account number. This issue has to be decided internally.
The user manual describes how corresponding customer and bank accounts are to be set up and used.
The SEPA activation is effected by entering the date as of which SEPA is to be capable of being used, in the system parameters via the transaction 'Management of System Parameters' (DBITDP).