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.

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 .

  • Guest
  • Sep 28 2018
  • Not under consideration
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 .

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.