Skip to Main Content
IBM Data and AI RegTech Ideas Portal

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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

Shorter URL for this site is: or

Status Delivered
Component Usability
Created by Guest
Created on Apr 9, 2019

Introduce message length check in MER, analogue to the length check performed in DNF_ILC_FIN.

Introduce message length check in MER, analogue to the length check performed in DNF_ILC_FIN.

The business impact: A message which is successfully validated in MER may nevertheless fail to be send to SWIFT, because it fails the length check in DNF_ILC_FIN due to the fact, that DNF_ILC_FIN considers the mandatory trailers which are to be added in block 5 when calculating the message length.

Response DNFH3752E informs about this, however, the user gets confused because the message still validates ok, when it shows up in MER again for correction.

Therefore, MER should already perform a length check for the message, considering the mandatory trailers in the same way as DNF_ILC_FIN does.