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 Mar 23, 2024

Restarting a flow where we want a subset that originally tracked red to re-process while ignoring others that originally tracked green.

SCBN Customers send batch outbound files for multiple Partners and some times due to Tranlsation, Configuration or System Outages some of the transactions impacted and failed in the batch and once the issue resolved and we or Customer want to restart them then in current scenario it will restart the complete batch and that cause duplicates to some of Partners where they have already received the data.

In order to avoid that, if we have the flexibility of restarting the failed docs and ignoring the already processed one's would be much helpful.

Also, it would be good to have independence from one doc to other for restarting the data which only effect the specific Partner.

For Example:

Ceva is the Customer who sends batch IDOC which contain 100 docs for 100 Partners to SCBN to split and deliver the tranlsated EDI doc to multiple Partners and due to some reason 50 docs posted to one few Partners failed due to System issues/bugs then we can't restart them from Inflight as it will restart the complete batch.

To restart the only few specific docs then again we have to reach the Customers and they have submit it again from starting.

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

Restarting a flow where we want a subset that originally tracked red to re-process while ignoring others that originally tracked green will be helpful for avoiding the duplication data delivery with restart from Inflight