Troubleshooting during SWIFT 2018 go live

Problem encountered	Possible solution
After start of the installation, an infodump is generated, saying that SWIFT characterset Z is not properly defined	Check tdpara.ini, Settings should be: CharSetSwiftZ=SWIZ and TDUChrSet=1
With SWIFT activated, the fields are unexpectedly shown under unmapped fields	Check that the mapping files (*.swm) were correctly imported using transaction DBxSWH (DBxSWM in versions < DOKA 5.06.00
MGRTSK shows “workflow not properly defined” i.e. because the new service CHD is not configured	Start DBISRO and add entries for CHD. Best place in workflow is before release (PDS)
Bank claims that SWIFT messages are not sent out.	Check if messages are stuck in workflow, waiting for service CHD. Check if the Service CHD is set to “execute” in the task manager. If not, bring down the taskmanager and activate the service. Afterwards restart the manager and check if transaction is processed correctly (i.e the SWIFT message sent out).
Old tasks have not been released and errors / dumps might occur, when picking them up.	If already released items hadn’t been finished completely, they could cause problems, as the outgoing messages had already been created when being saved, not when being released. Items on correction: They should be picked up and saved again before release.
Old messages (DTA, DTA, SWT Interbank, SCO Score, BOLero, TCO) are not displayed any more. Typical error message: “Unformatierte Anzeigen wegen eines Formatfehlers für Typ '…' 302 SFTCNV …. ”	Changes to be made in DOCIMM and CORMOD. For details, see DO5BHF.000554

Information for banks, NOT Going Live with SR2018

In case a customer is NOT able to go in production with his SWIFT 2018 version a HOTFIX solution is:

Reset production environment to the old status.
Stop all background processes. [SYSMGR]
Copy the attached configuration files into the INI folder.
Restart DOKA
Restart the background processes. [SYSMGR]

This enables the customer at least to import the new incoming messages using the incoming message manager [SWITSK]. Zipped SR2018 HotFix-Files

BUT …

New message types will be routed to “SPTROU” and have to be processed manually
New fields in existing messages (like MT707) will not be mapped into the transaction fields and thus be found under the popup window of “unmapped” fields in the processing transaction.
NO outgoing SWIFT/Score/DTA/BOLERO messages in the new format can be sent out. Thus the user have either to send letter/fax/mail. Using “SWIFT/Score/DTA/BOLERO” as a medium for sending outgoing correspondence will result in the messages being NAKed.

When using the inbuilt auto convert functionality, it is possible to create a MT999 that will not be NAKed. But still these messages will be auto converted based on the old SWIFT format and will not include any new fields. Therefore the content is not reliable correct.