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.
Safety Stock at Node Level
Enhancements to support Safety Stock at Node Level.Would require an IV API which accepts input at Ship Node and Safety Stock quantity.Node Level Safety Stock applies to all items present in the ship node if there is no safety stock configured at I...
IV to publish Inventory record for inventory audit
The OMS published Inventory Audit in OMS DB but after Inventory is moved to IV this capability is missing . The Inventor audit is crucial for an organization to understand the flow and how it affects OMS order life cycle.
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.
Ability to set dirty node
We need an ability to set Dirty Node at Item Node combination that resolves automatically based on Inventory Movement or Time. Currently IV does not seem to suppor this feature.
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...
Kits functionality in OMS Inventory Visibility
We attended the demo session for OMS Inventory Visibility and felt the product is looking great. However the product is missing support for kits and components (bundles). This is one of the must needed feature for some of the retail clients...
Safety stock enhancements
Enhancement request to support safety stock solution at the following levels,Date range support - Ability to configure safety stock based on applicate date range. This allows the users to configure these ahead of time and does not rely on just in ...
Do not place IBM confidential, company confidential, or personal information into any field.