IBM Sterling Ideas

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.

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Ability/ API to provide inventory availability considering the OPEN_ORDER/ BACKORDER in the response of IV service

The Get Network Availability API exposed in Inventory Visibility mandate Distribution Group to be passed in the input. The API does not consider OPEN_ORDER/ BACKORDER demand types while computing the availability in IV. This leads to inconsistencies in the availability picture provided to consumers of IV service and could lead to situations like over-promising. There must be the capability in IV to get the right availability picture considering these uncommitted demand types during the computation of inventory availability.  This API must behave similar to getATP from OMoC.

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

Customers implementing IV can use this picture to ensure the correct inventory picture is provided for use by the order capture channels and not land in over-promising situations.  

What is your industry? Computer Services
What is the idea priority? High
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    12 Apr, 2019 07:50pm

    Workaround 1 will create a demand against the node which might not be the node from where the fulfillment would happen. The other question which node to tie this OPEN_ORDER demand against. Workaround 2 will require customization in OMoC just to ensure it work with IV's APIs in their current state. 

    Can a getATP like API be exposed in IV, which does not mandate DG/ ShipNode and considers all nodes and demands in ATP calculation? That way, both OMoC and IV responses will be in sync and there won't be any discrepancies. 

  • Admin
    Chloe Chang commented
    12 Apr, 2019 07:10pm

    We do take open-order and back-order demands into account for availability. In OMS there are 3 kinds of availability levels (node, DG and across all node). The catch is that sometimes demands do not belong to a node or DG. 
    Therefore, you must use the GetATP API.

    Workaround 1 : On the orderline, create an order and select a tentative node (which can be changed with sourcing rules). A config in OMS can allow backorders to flow to the highest priority node in the hierarchy.

    Workaround 2: When you take the order, make a DG level reservation on IV. And when the order gets scheduled, remove the reservation.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    10 Apr, 2019 03:23pm

    From a client perspective, it is critical that the inventory be accurate with what is truly available when displaying inventory pictures to the customers.