IBM Sterling Ideas

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

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting 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 notifications 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.

Compliance Check map to include the CTX segments in the 999 Negative Acknowledgement

the usage of the CTX segment in the 999 would utilized in the LOOP ID - 2100 - AK2/IK3 ERROR IDENTIFICATION. where the Business Unit Identifier can correctly show the transaction error. TR3 rules state "Required when the error reported in this IK3 loop is within a business unit and the business unit identifier is known by the submitter of the 999" the TR3 also states how to utilize this within the 999

"Valid values for the business unit identifier are:

TRN02 269 business unit identifier

TRN02 270 business unit identifier

TRN02 271 business unit identifier

NM109 274 business unit identifier

PATIENT NAME NM109 275 business unit identifier

TRN02 276 business unit identifier

TRN02 277 business unit identifier

SUBSCRIBER NAME NM109 278 business unit identifier

ENT01 820 business unit identifier

SUBSCRIBER NUMBER REF02 834 business unit identifier

TRN02 835 business unit identifier

CLM01 837 business unit identifier"

  • Guest
  • Jan 14 2019
  • Not under consideration
What is your industry? Insurance
How will this idea be used?

The purpose of this is to identify the errors with the CTX segment in the 999 transaction.  

  • Admin
    Luke Raiano commented
    16 Sep, 2021 03:51pm

    We will review in the future, but not for the time horizon for thse requests. Please re-open in Q2 if still required.

  • Guest commented
    7 Jan, 2021 06:31pm

    We will re-evaluate. Many years ago I had reviewed this when we first implemented the 999 for version 5010 and the decision at that time was not to implement. The reason (if memory serves) was that due to uncorrolated arrays we would not always be certain that we could report the correct business unit value. I believe this was an issue in the 837s in particular - but it has been a while since I've look at this. Will ask a developer to review.

  • Guest commented
    7 Jan, 2021 06:28pm

    JIRA ITXP-8787

  • Admin
    Luke Raiano commented
    2 Apr, 2019 05:18pm

    Will review internally

    Will review internally

  • Guest commented
    28 Feb, 2019 01:57am

     

    Is there a way to generate CTX Business Identifier Unit segment with IBM ITXA.

    Thanks in adavance..

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.