NewItemLocBatch Cannot Be Executed in Multi-Threaded Mode
(Doc ID 1662299.1)
Last updated on OCTOBER 15, 2017
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.
We experience performance issues when running the NewItemLocBatch process, especially when the number of items/locations in the staging table is large and there are many future price events that need to be inherited. Currently, the NewItemLocBatch process can only be run in one thread to avoid some locking issues.
Steps to Reproduce:
- Create and approve a large number of future price events.
- 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.
- Run the NewItemLocBatch process.
- Notice that the batch process takes a long time to run.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document