Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified 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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jan 14, 2019

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"

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.  

  • Guest
    Sep 16, 2021

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

  • Guest
    Jan 7, 2021

    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
    Jan 7, 2021

    JIRA ITXP-8787

  • Guest
    Apr 2, 2019

    Will review internally

    Will review internally

  • Guest
    Feb 28, 2019


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

    Thanks in adavance..