IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 15 2019
  • Needs review
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.

What is your industry? Retail
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files