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 Not under consideration
Created by Guest
Created on Jul 9, 2019

Report availability at the Segment level.

Currently the monitorItemAvailability API and all RTAM capabilities report inventory at the node and item level, to some degree including tag information. The RTAM information doesn't have any references to segment. An example usage of segmentation is separating a purple size large shirt that has a Delta monogram logo on it from those that don't. When requesting availability for the purple size large shirt having the availability not be segmented doesn't show the complete picture and will lead to over selling.

Once the order is created for the purple size large shirt, it will only be able to allocate against the non-segmented product. An example is 120 purple large shirts and another 23 of them with the Delta logo. As it stands, RTAM would provide availability as 143 though it is really only 120.

The only alternative is heavier APIs such as findInventory but since that API is a more involved process, it isn't well placed for getting availability for a high number of items at one time as RTAM is.

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

It will be used to correctly report availability separating out the inventory by segment as applicable.