NewItemLoc Performance Is Poor When There Is a Large Number of Future Price Events to be Inherited

(Doc ID 1949138.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Price Management - Version 13.2.4 to 13.2.7 [Release 13.2]
Information in this document applies to any platform.


Performance issues are encountered when running the NewItemLocBatch process, especially when the number of item/locations in the staging table is huge and there are a lot of future price events that need to be inherited. Currently, NewItemLocBatch process can only be run in one thread to avoid locking issues.

Steps to Reproduce:

  1. Create and approve a large number of future price events.
  2. Create a large number of new item/location combinations by ranging many new items to existing locations, ranging many existing items to new locations, and/or ranging many new items to new locations.  Make sure that these new item/location combinations will inherit price events from the previous step.
  3. Run the NewItemLocBatch process.
  4. Notice that the batch process takes a long time to run.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms