LIKESTORE Process Causes Non-Transactional Level Items To Be Added In RPM_ITEM_LOC And RPM_FUTURE_RETAIL Tables In Case RPM New Item Loc Batch Is Run In Paralel
(Doc ID 2520825.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Retail Merchandising System - Version 16.0.1 and later
Oracle Retail Price Management - Version 16.0.1 and later
Information in this document applies to any platform.
When LIKESTORE batch is triggered, after a store is created in Retail Merchandising System (RMS) user interface (UI), non-transactional level items are added in RPM_ITEM_LOC and RPM_FUTURE_RETAIL tables if RPM_Newitemloc batch is triggered via job scheduler while LIKESTORE is still running
The issue can be reproduced at will with the following steps:
- User creates store via RMS UI.
- LIKESTORE background processing is triggered (records are inserted into the RPM_STAGE_ITEM_LOC – both style and SKUs).
- RPM_Newitemloc batch is triggered via job scheduler while LIKESTORE is still running and it does the following in the RPM_STAGE_ITEM_LOC table:
- REMOVE_DELETED – removes items deleted from ITEM_MASTER.
- REMOVE_DUPLICATES – removes duplicates records.
- REMOVE_UNWANTED – removes NON-TRANSACTION level items.
- REMOVE_EXISTING – removes records already existing in RPM_ITEM_LOC table.
- STAGE_ITEM_LOCS_TO_PROCESS – inserts into RPM_STAGE_ITEM_LOC_CLEAN.
- UPDATE RPM_STAGE_ITEM_LOC to I – marks records to I in RPM_STAGE_ITEM_LOC.
After REMOVE_UNWANTED ran, LIKESTORE continues to insert data in the RPM_STAGE_ITEM_LOC and causes NON-TRANSACTION level items to be inserted into RPM_ITEM_LOC and RPM_FUTURE_RETAIL.
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