RPM_ORPOS_PRICE_CHANGE_PUBLISH.RESET_INDICATOR Not Updated to 1 When Reset Date Is Added (Doc ID 2214190.1)

Last updated on DECEMBER 19, 2016

Applies to:

Oracle Retail Price Management - Version 13.2.6 and later
Information in this document applies to any platform.

Symptoms

In Retail Price Management (RPM) 13.2.x, the reset_indicator remains '0' after adding a reset date to an executed clearance and running the RPMtoORPOSPublishBatch.  We expect the reset_indicator to be updated to '1' as happens when we add a reset date when creating the clearance.


Steps to Reproduce:

1. Create a clearance at sku/loc level or any level (do not add reset date)
2. Approve the clearance
3. Wait for the clearance to be in executed status
4. Go to Create Clearance screen and add reset date and approve
5. Note that rpm_clearance_payload and rpm_clearance_reset tables get updated with reset date
6. Run RPMtoORPOSPublishBatch.sh
7. Note that for the reset clearance price change record - RESET_INDICATOR comes as 0
    - The same is seen when reset date is added later on for executed clearance


Cause

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