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.
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...
Want to drill down to order data (PO , MFG Order) from inventory screen
From the inventory screen , user should be able to see the orders( Purchase orders , sales orders ) that is causing the supply and demand. This is currently possible in Inventory console screens
Short pick/reject from a store results in a inventory oversell
When a shortage is reported from a store (through out of the box IBM Store module) that results in the order being backordered, the backorder demand is not being considered in the overall shipping aggregate ATP in OMS. As a result, this will resul...
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 performanc...
Get Availability by tag (inventory identifier)
IV does not currently provide availability by tag. It does support taking supplies/demands by tag. OMoC will generate the TagNumber and pass it to IV for supply/demand updates. IV will store them as OMoC had provided. However, you will not be able...
Ability to schedule on hand inventory publish for a set of DG’s or nodes
Currently, the IV events for inventory publish only include available units (supply - demands - safety stock). We have a need to schedule (intra day changes and nightly sync) the publish of ON HAND units for SKU/location level to certain external ...
Ability to schedule the publish of network level availability for a set of DG's
The trigger DgAvailabilityChange Event allow you to publish availability changes for all DG's within a tenant ID. This does not allow us to schedule the publish from within IV and also restrict the data publish to a subset of DG's. Within IV, we n...
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
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.