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.
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...
Maintain item search details and context over the different selections in BUC
It would help productivity in BUC if the item search feature remembered the selections previously made. There is the breadcrumb offering some persistence, but if the user jumps to Orders or anywhere else, all the item search selections are cleared...
Reset dirty Node - Optimized approach for IV
We are looking at an option where we have one invocation to reset the dirty flag instead of doing for each item ship node. In full sync there will be 150K items and 3000 stores hence this approach of resetting dirty node for each item and ship nod...
In BUC Prepopulate the enterprise entry field when there is just the one value available
Selecting the enterprise over and over again seems like an irrelevent user task. Usually there is just one enterprise configured in the system. Even with multiple enterprises defined, perhaps one could be preselected as the default.It would be gr...
OMoC platform cap of 1MB for the YFS_EXPORT.MESSAGE needs to be increased
To troubleshoot/debug issues we need to log outgoing/incoming messages to yfs_export table and few messages are more than 1 MB. Service fails if YFS_EXPORT.MESSAGE is more than 1 MB.This imitation needs to be increased as DB2 supports 2GB of CLOB...
Add user, role management to the BUC tool for users who are administrators
Allow a BUC authorized user with admin privelages to manage OMS users directly in BUC. BUC users should be able to see users by enterprise, team, group or role. Actions allowed should be to delete a user, create a user, or update a user's info...
DB tool usability enhancements
The DB query tool that comes with OMoC 2.0 has multiple usability issues.1) on running a query, do not scroll the query entry window to the top, but leave the cursor where it is in the window2) I should not need to add a space at the end of each l...
Provide capability for a BUC user to get from Node exception alert or a Node Details page to Node’s order list
OMNI Fulfillment managers oversee several hundred nodes and need the ability to see a Node's open order, or orders flagged as an exception, while reviewing the node's alerts or from the Node Detail page. Use Case. How to get from Node exception to...
Node Fill Rate Metrics in the BUC module needs to consider Pick Declines in calculating rate, and should not ignore them
Per feedback regarding Fill Rate calculationNode metrics not considering cancelled/rejected orders - Per the current product design, BUC was not considering cancelled/rejected orders while calculating the node metrics. Our engineering team is rev...
The design of the Pick Declined metric in the BUC should be looking at line status = 1400 even when the line moves to the next status and 1400 is no longer active
Current design of BUC reporting Declined by Node metrics has gap that will under-report and under represent the declines/reject/short-picks by node.-Design as explained in Case #TS004179727 "Pick Decline is a status of BUC and we do not have a sta...