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 Mar 15, 2019

Order Management on Cloud dataload to use DB Index and runstats for table YFS_ITEM

During an OMoC initial dataload there can be a need to upload 1M+ item records to the YFS_ITEM DB table. This table is initially empty and non indexed. This can make the dataload INSERT take a very long time when using the ManageItem API. There is a need for the YFS_ITEM table to first be Indexed and possibly primed with records, and then a runstats needs to be run, as we have seen INSERTs running that do not initially use the Index, and the accompanying SEARCH to an INSERT is a huge overhead for the dataload. We need the YFS_TABLE and the ManageItem API to use Indexing by default OOB, and the YFS_ITEM table to be indexed OOB in an OMoC env.  Please look at this request from a client dataload perspective. We need the recommended OOB dataload (from an MQ GET queue / ManageItem API ) to use most efficient way to run the underlying YFS_ITEM sql INSERT.

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

This idea will be used across all OMoC clients for initial dataload, and subsequent updates using the ManageItem API and YFS_ITEM table.

  • Guest
    Apr 13, 2020

    All the indexes are created in OMoC right after the tables are populated. Run stats are regularly run in all environments to keep indexes up-to-date.

    Indexes needs to be created based on customer data profile.

    If additional information on the problem and missing indexes can be provided, this can be reviewed for further actions.