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
IV does not currently provide availability by tag. It does support taking supplies/demands by tag.
OMoC will generate the TagNumber and pass it to IV for supply/demand updates. IV will store them as OMoC had provided. However, you will not be able to request availability by tag number.
Note that OMoC generates TagNumber as an aggregation of the tag identifiers. For example, if you have LotNo and BatchNo as the item's tag-identifiers and createOrder is called with LotNo=L1 and BatchNo=B1 in the OrderLineInvAttRequest element, OMS by default will set TagNumber (aka tagNumber) as "L1|B1" when making the demand update to IV.
For supply sync/updates to IV, you'll need to use the same logic as OMS to define the tag number. Or you can use your own logic to determine the tag number and implement the YFSGetTagNoUE in OMS to use the same logic.
But again, IV only supports showing availability across tags. So even if an order is placed asking for L1|B1, the availability will be across all.
How will this idea be used?
Currently DalTile is use invetory identifiers for availability calculations.
|What is your industry?||Construction / Architecture / Engineering|
|What is the idea priority?||Medium|
|Link to original RFE|