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
Workspace Store Engagement
Created by Guest
Created on May 11, 2022

AdjustmentType for Manual is missing in SIM

getAjustmentReasonList API is unusable since there is no WMS screen to create Adjustment Reason at store level.

Alternate solutions:

- Use Common Code List to maintain adjustment reason. Maintained from Application manager

- Use Custom table to maintain adjustment reason in OMOC UI. Build maintenance screen for table

- Use hard-coded list of reason in OMOC. Requires code changes to add/remove reasons

The current SIM API to add/remove inventory does not capture Adjustment Reason Code and Reason Text.

Comparing the existing adjustLocationInventory API, we have a Audit tag in which we pass the above attributes.

The audit records the AdjustmentType as ADJUSTMENT along with ReasonCode and ReasonText.

There is a provision to pass adjustmentType in SIM API but is limited to the following adjustment types:


Because of this limitation we are not able to save the ReasonCode and ReasonText as references.

Expectation from IBM:

Add an additional AdjustmentType as ADJUSTMENT or MANUAL

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

This is used in the manual adjustment process. Not having a manual adjustment type is a defect. We use it in 9.1.