NewItemLoc Performance Is Poor When There Is a Large Number of Future Price Events to be Inherited
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:
- 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms