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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Please use the Search supply API for this requirement, Documentation: https://www.ibm.com/docs/en/intelligent-promising?topic=demand-inventory-search
Marking complete.
In our project, it would be good to have that kind of API to be able to compare the stock available in the original system against the stock available in IV, after a synch supply has been done or a set of adjustments for example. We opened the case TS010029153 for this purpose.
There are requirement to maintain multiple supply buckets in IV using productClass (Good, Damaged, Display etc). In such cases, a single API to get all the supplies for 1-N item-Nodes or or node level supply list is a basic and must have requirement for store to be able to pull supply (and demand) and during the counting especially.
With the current GET supplies API, if there are 4 supply buckets (based on productClass), the calling system will need to make 4 calls. If productClass and shipNode can atleast accept array of object, it would reduce the call from 4-1.