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.
Event to publish any demand changes to external systems
Since there were no description in this idea, the offering assumption is for IV to publish demand.change data similar to supply.change event.
Need a DGAVAILABILITY SNAPSHOT event Publish similar to Product Availability Snapshot event publish
We need a DGAVAILABILITY SNAPSHOT event which has the ability of external trigger based on a Specific DG and have EOF file to intimate end of process.This functionality already exists in Product Availability Snapshot which is at Node level.
IV event to publish availability only when item threshold is reached.
Currently IV publish event : ProductAvailabilityToSell.ShipNodeChange when the availability for an item at a ship node changes. Similarly IV event DgAvailabilityChange is published when the availability for an item in a DG changes.This results in...
Lock Ship nodes at Delivery method level (Enhancement for IBM Sterling OMS v9.5)
This is very much needed for the retailers to maintain a granular Inventory visibility within store network and also to increase the business revenue by showing availability for a specific delivery mode instead of blocking the availability for the...
Need to monitor the progress of IV APIs
The current IV has no way of monitoring the progress of APIs and we need better visibility and access to logs. Also, we need an API to query all the items sync'd up per store / all stores.
Need Threshold based ATP publish for DG Availability changes.
DG Availability was triggered every time when a store reaches capacity and IBM COS buckets are filled with more objects, causing backlog in consumption. Many stores were hitting capacity during the day and, every time this happened, IV triggered u...
Configurable framework in IV to determine distribution group(s) to be used for inventory lookup functions
Currently, the IV API's expect the requesting application to pass the DG to be used for inventory lookup. In our setup, the determination of DG is configured based on OMS sourcing rules and we have numerous parameters (SKU attributes, shipping sta...
APIs should publish events that can be consumed and actions can be taken upon
IV APIs should publish events e.g. On successful creation of reservation or on partial reservation so that an action can be taken upon that event.
APIs should be idempotent
In distributed application architecture, if the APIs are not idempotent duplicate data issues can occur. e.g. duplicate requests for Reservation blocks inventory for other customers.
Breakup of future quantity by date in Available Inventory
The Availability API gives onhand and future in addition to the total quantity. The future should be broken by date e.g. x units on date1, y units on date 2.
Do not place IBM confidential, company confidential, or personal information into any field.