PriceEventExecutionRMSbatch Writes Incorrect Data to PRICE_HIST

(Doc ID 729642.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Price Management - Version 12.0.6 to [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 "" and then "".  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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms