RPM Location Move Schedule Batch Generates Duplicate RPM_FUTURE_RETAIL And RPM_PROMO_ITEM_LOC_EXPL Records
(Doc ID 2129299.1)
Last updated on OCTOBER 28, 2022
Applies to:
Oracle Retail Price Management - Version 14.1.1 to 14.1.2 [Release 14.1]Oracle Retail Price Management - Version 14.0 to 14.0.4 [Release 14.0]
Oracle Retail Price Management - Version 13.2 to 13.2.9 [Release 13.2]
Information in this document applies to any platform.
Symptoms
The locationMoveScheduleBatch.sh batch generates duplicate records in the RPM_FUTURE_RETAIL (RFR) and RPM_PROMO_ITEM_LOC_EXPL(RPILE) table when both the DZ (or DL) and IL timelines exist in RFR for the location that is being moved.
Steps to Reproduce:
- Create a new style and create a child item.
- Range it to a location.
- Run newitemlocbatch and verify the RFR table and make sure there is an entry for PZ for the style.
- Create a price change for the newly created Parent item Diff/Zone.
- Approve the same.
- Verify the RFR and make sure there is entry for Curr_hier DZ for the price changed item.
- Create a Promotion for the Parent Item Diff/Location.
- Approve the same.
- Verify the RFR and make sure there is entry for DL for the newly created parent item.
- Create a Clearance for the child item/location.
- Approve the item.
- Verify the RFR and make sure there is entry for IL for the newly created child item.
- Create locationmove for the location to a new location.
- Approve the same.
- Run the locationMoveSchedule batch.
- Verify that duplicates are created for the location in the RFR.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |