Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Oct 9, 2020

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.

What is your industry? Retail
How will this idea be used?

Accurate reporting of rejections by nodes in the BUC