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

Provide an audit of demand in a similar way to how inventory audit works today to see an audit of supply.

Whenever demand is created, cancelled, or closed by a reservation or schedule change the audit of that change should be written to a table. Could even use the existing YFS_INVENTORY_AUDIT table with the addition of a column to define whether a demand or supply change.


Then for any APIs that affect demand including confirmShipment, reserveItemInventory, reserveAvailableInventory, scheduleOrder, createOrder, and others; really anything that raises the INVENTORY_CHANGE.DEMAND_CHANGE event. Write to a new table such as YFS_INVENTORY_DEMAND_AUDIT or YFS_INVENTORY_AUDIT table and record that demand change. The advantage of using the existing table is the existing getInventoryAudit... APIs would only need to be changed to support inventory type input rather than having brand new APIs.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 23 2019
  • Needs review
How will this idea be used?

To better troubleshoot any allocation failures.

What is your industry? Retail
What is the idea priority? Medium
DeveloperWorks ID
Link to original RFE
  • Attach files