Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Needs more information
Created by Guest
Created on Apr 9, 2019

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.

What is your industry? Computer Services
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.  

  • Guest
    Sep 23, 2022

    Hi Sampson, The use case is very specific where order is captured from partner channel (Marketplace). when this order is created in sterling then a OPEN_ORDER demand is created without association of any node. Then this demand picture flows to IV this is not recognized as a demand and also not associated to any of the node or DG for availability calculation. Only when we pass the OPEN_ORDER demand against a specific node, IV takes this demand for AVL calculation. Please let know if you see a different behavior.

  • Admin
    Sampson Wong
    Sep 13, 2022

    Hi All. the network availability API by default considers OPEN_ORDER demand for the distribution group. If the client wish to consider across the full network, a DG must be created to include all node that should be considered.

    Can you please provide more details what is needed here provided the API already does what is asked in the RFE.

  • Guest
    Jun 29, 2022

    We are doing this for our ecosystem, but third parties and external systems are exported to sterling without any reservation. We can use a workaround where we create a reservation for external open orders, but need to be sure that IBM has the feature "Consider Open Order Demands" on your roadmap.

  • Guest
    Apr 12, 2019

    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. 

  • Guest
    Apr 12, 2019

    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.

  • Guest
    Apr 10, 2019

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