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
Currently the monitorItemAvailability API and all RTAM capabilities report inventory at the node and item level, to some degree including tag information. The RTAM information doesn't have any references to segment. An example usage of segmentation is separating a purple size large shirt that has a Delta monogram logo on it from those that don't. When requesting availability for the purple size large shirt having the availability not be segmented doesn't show the complete picture and will lead to over selling.
Once the order is created for the purple size large shirt, it will only be able to allocate against the non-segmented product. An example is 120 purple large shirts and another 23 of them with the Delta logo. As it stands, RTAM would provide availability as 143 though it is really only 120.
The only alternative is heavier APIs such as findInventory but since that API is a more involved process, it isn't well placed for getting availability for a high number of items at one time as RTAM is.
How will this idea be used?
It will be used to correctly report availability separating out the inventory by segment as applicable.
|What is your industry?||Retail|
|What is the idea priority?||Urgent|
|Link to original RFE|