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 Delivered
Created by Guest
Created on Sep 3, 2019

Consolidate duplicate records in YFS_INVETNORY_SUPPLY table

After enabling hot fix for inventory adjustments system started created duplicate supply records but they are not consolidated. This is causing reporting issue. 

 

Please refer to PMR TS001600046 and TS002660522

 

Either inventory purge or consolidate agent should consolidate the records is ideal solution if that is not possible we were able to a workaround suggested by support team in TS001600046. Problem is we wanted to use ON_INV_MISMATCH_LIST instead of ON_INV_MISMATCH as later one will cause performance issues. The attribute which are available in ON_INV_MISMATCH are not available on ON_INV_MISMATCH_LIST We want ActualQuantity, ExpectedQuantity and Quantity part of LIST event so that we can implement work around. 

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

Data will look clean, table size will be reduced.