Last updated on JULY 03, 2017
Applies to:Oracle Retail Price Management - Version 13.2.4 and later
Information in this document applies to any platform.
Retail Price Management(RPM) in front end limits the effective date for Reset POS Price change to be VDATE.
However, the same validation is not enforced in the price injector batch, where price changes may be injected with a future date and approved, however the price changes published inconsistently carry the VDATE as the effective date.
Steps to reproduce:
1. Stage price injector records for Reset POS price change type with a future date.
2. Run the InjectorPriceEventBatch and observe the records getting approved.
3. Observe the payload records and notice that the effective date in RPM_PRICE_CHANGE is the date populated in step 1 and the effective date in RPM_PRICE_CHG_PAYLOAD is the VDATE.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms