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
Categories Onboarding
Created by Guest
Created on Sep 28, 2018

Request For Enhancement : Scenario Release Number Value issue in SPE02/Config Center

While on-boarding partners to the SCBN platform whenever we are trying to clone an existing outbound EDIFACT envelope we are getting the Scenario Release Number value : D96A getting populated by default . This should not be the case as the existing envelope we are cloning did not have this value/parameter in the first place . The cloned new envelope should have the same parameters as the existing envelope . The value is conditional as per UNH/EDIFACT standard and should not be populated by default. This value results in a bad UNH segment for the EDI file and partners reject it on their side harming business .

Salesforce Case :TS001240649 where customer had complained of bad UNH segment as D96A value populating twice .

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

As part of Watson Customer Engagement we work on on-boarding partners to our Hosted Sterling Integrator under SCBN offerings . Our customers engage in EDI transactions with their on-boarded partners and this value coming twice in the EDI UNH segment is unacceptable for many of the partners and causes data to fail on their side affecting business. This would restrict failures to happen for business transactions resulting to faster realizations .