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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Aug 23, 2019

Provide an audit of demand in a similar way to how inventory audit works today to see an audit of supply.

Whenever demand is created, cancelled, or closed by a reservation or schedule change the audit of that change should be written to a table. Could even use the existing YFS_INVENTORY_AUDIT table with the addition of a column to define whether a demand or supply change.

 

Then for any APIs that affect demand including confirmShipment, reserveItemInventory, reserveAvailableInventory, scheduleOrder, createOrder, and others; really anything that raises the INVENTORY_CHANGE.DEMAND_CHANGE event. Write to a new table such as YFS_INVENTORY_DEMAND_AUDIT or YFS_INVENTORY_AUDIT table and record that demand change. The advantage of using the existing table is the existing getInventoryAudit... APIs would only need to be changed to support inventory type input rather than having brand new APIs.

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

To better troubleshoot any allocation failures.