IBM RegTech Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

 

note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

Block 3 field 121 (FIN MT199 and FIN MT103) in lower case despite DABADKKK DnqEROUOptions EditorAllFieldsUppercase FIN

Referring PMR 19041,010,678
Also see item #36 in the attached doc.

In order to comply with the SWIFT specifications and recommendations for the unique transaction reference (UETR - field 121 in GPI messages MT 103 and MT 199) we urgently need a possibility to ensure, that this field is not translated to upper case, independent of the configuration within MER how to handle the remaining fields within a message. Configuring MER in a way that no upper case translation is done at all is not an option, as this runs the risk to not comply with SWIFT specifications for other fields.

This RFE repeats the same request which we already been raised for WBIFN some years ago, to have a configuration possibility for upper case translation per field. As a compromise, we by that time accepted to get a global configuration possibility to configure upper case translation in general (for all fields and all MTs). This compromise now causes our issue and necessitates this RFE.

Our ultimate request is a configuration possibility within FTM MER to allow specify whether upper case translation is done per field, however, considering the urgency to comply with the SWIFT recommendations for GPII now, for WBI-FN MER, we would accept an implementation which just excludes field 121 in MT 103 and MT 199 from being translated to upper case.

We don't consider this minimum solution as a requirement at all - it's necessary to comply with SWIFT's specifications and recommendation, and we expected to get this implemented with an APAR within the next 2-3 months.

We need a solution for WBIFN.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Shipped
Component Mapping & Translation
Priority Urgent - Blocker
  • Attach files