IBM Sterling Ideas
formerly Watson Supply Chain
Submit ideas for other Watson Customer Engagement Products:
• Watson Marketing
• Watson Campaign Automation
• Watson Commerce
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.
How will this idea be used?
To better troubleshoot any allocation failures.
|What is your industry?||Retail|
|What is the idea priority?||Medium|
|Link to original RFE|