FTM-MER should be able to handle this double slash (//) checking

FTM-MER should be able to handle this double slash (//) checking

In existing Merva users are required to key in a double slash '//' at the beginning of

each account number. In FTM this is not required anymore but since the users are

used to keying in the double slash '//' for the account numbers, they will sometimes do the same thing in FTM also (refer to Attachment No. 1 for instance).

When users verify the message, the FTM will prompt the message stating that the message is valid and hence the user will proceed to submit the message without noticing the mistake. At the backend, what happens is that the FTM is formatting the message from the GUI into an unformatted format (refer to Attachment No. 2) to be routed through the queues respectively. The double slash is being combined with the predefined single slash in the unformatted format to form a triple slash '///'. FTM will read this triple-slash value as a code with a single slash value in which this code field should be filled only with a 'C' or 'D' value and is also not compulsory.

When this message is sent to SWIFT, the message will fail and lands in the TCCERROR queue instead because of this issue. The error is displayed in the Context field. Refer to Attachment No. 3 and No. 4 for a sample message for this particular issue reported by our Head Office users.

FTM-MER should be able to handle this double slash checking during the data entry validation screen.

Ref. CASE #: TS005043751