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 Not under consideration
Created by Guest
Created on Apr 5, 2019

Display USER_CODE separately on the transmission hierarchy screen.

Sorry for the delay on this. I discussed this with the developer and
also the architect.

We have been calling the DOCUMENT TYPE field the "record id" for awhile.
This is not something that we would want to change. The
USER_CODE being displayed as the "record id" does not make sense.
However, if the USER_CODE does have value to you, we can display it
separately on the transmission hierarchy screen. We would do this as a
feature request (RFE) if you request it.
  • Admin
    Craig Rector
    May 31, 2022

    Because other higher priority features need to be addressed in the product, this Idea will not be implemented in the next 12 months

  • Guest
    Jan 10, 2020

    Duplicate of FTMCHECK-I-50.  Keeping FTMCHECK-I-47.  Details from FTMCHECK-I-50:

    Record ID value shown as zero in FTM Inbound Transmission Hierarchy page

    The Record Id field in Inbound transmission Hierarchy -> Debit Details -> Check Data is shown as zero. If this field in the UI is the CPCS record id, then it should be corrected. If not, we need the CPCS Record Id (decimal value 0 - 255) field to be displayed as part of the transaction details in the FTM screens. More details are thee in the IBM PMR 85708-442-000.

     Had "1" Vote.