Customizing Electronic Messages

The structure of electronic messages is defined at Level 2. Thus, it is the responsibility of Surecomp DOS to determine which messages are created with which tags.

• If the contents of a tag is unique, the whole tag is displayed in the text function.
• If the tag is mandatory, but the contents is customized, the content is filled via a function at Level 5.
• If the tag is optional and the customer is to decide whether the tag is to be displayed or not, a function is provided at Level 5 that outputs the tag and the content. Example: Tag 39“/PrintAdditionalAmount”

Field formatting is not permitted in electronic messages (“ConvertBlock” in the text function is not allowed). If field contents of a tag are composed of several parts, tag content has to be prepared in the correct format in the transaction field and is then just displayed in the message. “TagxxTXT” fields in TRNDOC are used to prepare the texts. These fields are filled in line with default rules at Level 5. The “CheckBlockSize” function checks the format.

The central rule “SWTPrtReference (tag, channel, role)” is used to control the output of reference numbers in correspondence.

Tag is obligatory, channel and role are optional.

If the channel is empty, the short reference is output
If the channel is entered, the function will know whether the short or long reference it to be used
If the role in empty, use \TRNMOD\TRNDOC\DOCCUR\ROLE - this is the field that will have to be used in 99% of cases.

SWIFT RMA Check

Setting RMACHK=“I” in DOCEOT init order 1200 activates an access to sftrma.ini.

An entry in the form

[<8-digit BIC>]
<MT>=No

in this file means that the MT message types are rejected and a warning issued. The user then has to decide how to proceed. Setting 'C' posts the “GetSwtMtAutCus” rule which contains a customer-specific check logic.