Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 product management 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.

Additional Information

To view our roadmaps:

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

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Components Usability
Created by Guest
Created on Apr 9, 2019

Regarding 40873 311 758 - Length check in MER

As discussed with Gabi von Carlowitz, I opened this RFE. It is regarding the length checking functionality which is missing in the MER application to avoid that customer entered too long message and thinking that the message is valid.
  • Guest
    Apr 17, 2019

    AS business impact: a msg 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. as the end user think the message is validate and do not expect to have it rejected, the same check done at DNF_ILC_FIN level should be introduced in MER to avoid such a situation.

  • Guest
    Apr 17, 2019

    very userfull ideal as it is a non-sense to validate the message that later on will be refused and that has to be resend