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 Future consideration
Categories Inflight
Created by Guest
Created on Oct 31, 2022

Add EDI FA 997 correlation values to inbound document PIDs (similar to how FA 997 correlation is handled for outbound documents)

When an inbound EDI X12 document is received from a partner an outbound 997 is apparently automatically triggered based on the SCBN setup. This outbound 997 FA shares the same SCBN PID as the originating inbound document, but this action does not updated Acknowledgement "Status" or the add the Acknowledgement detail "link" like you see on the outbound documents. There is therefore no obvious "reconciliation" to the outbound associated EDI 997 FA in any received EDI document details. To see this level of detail you currently have to use the inbound document reference ID to determine the PID and then conduct the search again by PID to see BOTH the originating inbound document and its associated PID.

I suggest that when an inbound document is received that an OB 997 is triggered based on the setup which shares the same PID but also updates the Acknowledgement "Status" and detail link like you see in outbound document 997 FA reconciliation.

What is your industry? Other
How will this idea be used?

To facilitate operational efficiency correlation and review of inbound documents.