PriceEventExecutionRMSbatch Writes Incorrect Data to PRICE_HIST
Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Price Management - Version 12.0.6 to 22.214.171.124 [Release 12.0]
Information in this document applies to any platform.
Checked for relevance on 07-Dec-2011
Checked for relevance July 2013
When a regular price change and a clearance price change are created for an item/multiple zones with the same effective dates, the priceEventExecutionRMSBatch populates an incorrect reason code in PRICE_HIST table.
Steps to Reproduce:
1. Create and approve a clearance for an item/multiple zones effective vdate +1
2. Create and approve a price change for an item/multiple zones effective vdate +1
3. Run "priceEventExecutionBatch.sh" and then "priceEventExecutionRMSBatch.sh". Notice how PRICE_HIST table gets updated.
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