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 Delivered
Created by Guest
Created on May 13, 2019

Schedule agent creating duplicate entries in YFS_ORDER_RELEASE_STATUS and YFS_ORDER_LINE_SCHEDULE

Creating this RFE on request of IBM Development for RTC


1. Original Issue details

Customer is finding some orders with large numbers of Order Release Status records when one line is Reserved, and another continues in BackOrdered status, after multiple Schedule attempts.  I have attached a replication steps document describing it.

Customer wants to use FIFO processing during schedule fulfillment, so they have set the Backordered retry schedule to be 0 hours, so we are seeing some orders have up to 30K - 50K ORS records due to one new one being added with each Schedule attempt.  Client is expecting that new records shouldn't be created each time, so that the total number of ORS records won't build to such a volume and affect performance.

2. Simulation steps of problem
Attached are replication steps document describing it.

3. Resolution/workaround earlier provided
A Purge Script was provided in original case TS000799039 / RTC 576128

4. Expected behavior.
Customer is expecting solution that will ensure there are no duplicate records getting added.

What is your industry? Wholesale Distribution & Services
How will this idea be used?

Discussed in RTC 582375

  • Guest
    Mar 16, 2022

    Close this request since I have not heard back and based on my above comment, this should have already been delivered in a Fix Pack.

  • Guest
    Mar 1, 2022

    Hi Alexandar. I am reviewing old enhancement requests and this one appears to have been released in FP49 on version 9.4 and the issue was resolved. Could you please let me know if there is any outstanding aspect to this request?