IBM Sterling Ideas

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.

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 status with this name in OMS application. As per the current design, pick decline in BUC maps to the OMS status 1400 ("Backordered From Node")"

Reason for design review

When a node declines/rejects a line it moves to Status = 1400 but it will only be in that state temporarily, a few hours at the most. Most retailers will typically have the OMS take action on that line pretty quickly by assigning it to another node (if ATP), cancelling (it no ATP) or having Customer Service take action (put a CSR hold). The issue is that it won't be in 1400 status for long, and once it moves to another status the "Pick Decline" event won't be visible for the node, though they rejected it, so it under-reports declines by the node.

  • Guest
  • Oct 9 2020
  • Planned for future release
How will this idea be used?

Accurate reporting of rejections by nodes in the BUC



What is your industry? Retail
What is the idea priority? Medium
  • Attach files