IBM Sterling Ideas

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:

Post your ideas

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.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.

  • Guest
  • Apr 9 2019
  • Future consideration
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 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. 

  • Guest 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.

  • 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.  

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.