IBM Sterling Ideas
formerly Watson Supply Chain
Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
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.
How will this idea be used?
Discussed in RTC 582375
|What is your industry?||Wholesale Distribution & Services|
|What is the idea priority?||Urgent|
|Link to original RFE|