Old Records is Table RPM_PROMO_ITEM_LOC_EXPL Did Not Purged by Conflict Checking Process
(Doc ID 2081625.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Retail Price Management - Version 13.2.6 and later
Information in this document applies to any platform.
In Oracle Retail Price Management (RPM), conflict checking is not purging old item/location records from RPM_FUTURE_RETAIL and RPM_PROMO_ITEM_LOC_EXPL tables as expected. When conflict checking runs for the Item/Location, it is expected that the process should trigger a purge of the RPM_FUTURE_RETAIL and RPM_PROMO_ITEM_LOC_EXPL tables.
Steps to Reproduce:
- Check in RPM_PROMO_ITEM_LOC_EXPL and identify an item/location combination that has old records (e.g., end date of promo is before vdate-PROMOTION_HIST_MONTHS).
- Create a promo for the item/location combination.
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