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.
API to GET all items having supplies for a node
IBM Inventory Visibility Service does not provide an API to GET all supplies available for a node. In our implementaion, there are hundreds of shipnodes. Also, many old items are discontinued often. If we want to do a comparison with IV for any...
IV Supply Sync Visibility
Need an acknowledgement process for Supply Sync in IV that will summarize saying they received “x” number of updates, processed “x” number, and the supply for “x” number of items did not change. IBM informed this requirement is on the product road...
Add Fields to Order Hub (reference, referenceType, lineReference, segment, segmentType)
We would like to have the option to view the following fields in Order Hub: reference, referenceType, lineReference, segment, segmentType.
GTIN based Inventory Availability and Scheduling in OMS CoC and Inventory Visibility
For our current client, inventory items are uniquely identified using UPCs(not to be confused with UPC in generic sense) and not SKUs, while the selling catalog identifies items using SKUs. These UPCs can change every year for the same item. For e...
Trigger SupplyChange Event based on change in timestamp in addition to quantity change
Currently, IV triggers supply change event for an item only when there is an update to supply bucket quantity. To make the event updates robust, we need capability to generate the events on the change of timestamps.
Make sourceTs and updatedTs fields visible in Get Supply and Get Demand API Responses
As an integration consultant, I need to be able to see when the supply and demand for an item was last updated so I can confirm whether or not information is flowing from external systems to IV. The sourceTs and updatedTs will help when performan...
Multiple User Credentials
Our product team has grown exponentially; we now have around 9 teams with 2-4 developers in each team, and potentially all will have PROD access to IV at some point. Currently, we only have one generic user credentials to make changes in PROD. Thi...
IV doesn't allow syncing negative inventory postion like GIV does.
When an Absolute sync is done for Item-Node combination with -ve value IV ignores it. Where as we have this functionality in GIV
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 doesn't provide ability to differentiate various shipnodes by ship node type. As a result events published from IV cannot be filtered and/or distributed over separate channels within the external consumer by ship node type.
Currently in Ship Node configuration only Delivery method configuration is there need additional ability to differentiate DC vs Store so we can define various rules based on Ship Node type
Do not place IBM confidential, company confidential, or personal information into any field.