Price Change Consumer Price History Delete Logic Is Wrong and Should Include Store and Item (Performance Issue)

(Doc ID 1991474.1)

Last updated on OCTOBER 12, 2017

Applies to:

Oracle Retail Store Inventory Management - Version 13.2.4 to 13.2.9 [Release 13.2]
Information in this document applies to any platform.


In the Store Inventory Management (SIM) application, we find that price change consumer deletes from price history using column ID_EV instead of column PRICE_CHANGE_ID. The query should also be including store ID and item ID to greatly improve performance.  Note that there are no indexes existing on LE_HST_ITM_SLS_PRC.ID_EV column, adding to performance issues.

Steps to Reproduce:

1. Send ClrPrcChgDel, MultiBuyPromoDel, or RegPrcChgDel from RPM to SIM
2. Observe sessions in database taking a long time to execute DELETE FROM LE_HST_ITM_SLS_PRC WHERE ID_EV = ? while the parameter being passed in the code is from PRICE_CHANGE_ID
3. Observe stuck threads in WebLogic server due to query execution taking longer than stuck_thread_max


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