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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Based on the requirement discussion on this RFE, renaming the title to
"Ability to consider unassigned demands (no assigned node) in availability calculation"
Thank you for the update. To instate the requirement, client is facing issue with unassigned demand which is slightly different than the OPEN ORDER demand which was discussed in earlier thread.
The issue here is when multiple vendors whose does not have access to order scheduling or inventory allocation against a shipnode, they will create a demand without shipnode. By default IV does not support unassigned demands as there is no context of shipnode. To address this problem clients wants a way to include unassigned demand when computing the availability for a given item-node, therefore mitigating the risk of overselling.
Currently the vendors does not use the concept of reservation, and the unassigned demand is created directly on the system.
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.
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.
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.
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.
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.
From a client perspective, it is critical that the inventory be accurate with what is truly available when displaying inventory pictures to the customers.