My Oracle Support Banner

PRICE_HIST Only Saving Latest Emergency Price Change On Same Day Though Reason Codes Are Different (Doc ID 2461532.1)

Last updated on DECEMBER 03, 2019

Applies to:

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


On : 16.0.1 version, RPM Interfaces/Integration

  When having multiple emergency price changes for the same item/loc/date but different reason codes, only the latest price change is sent and maintained in the PRICE_HIST table
  As different reason codes are used, you expect both records to be entered into PRICE_HIST

The issue can be reproduced at will with the following steps:
   1. Create emergency price change for particular item/loc/effective date/reason code.
   2. Do another emergency price change with same item/loc/effective date but different reason code
   3. notice the price hist table only saves the latest one.
   4. Expecting two records on price_hist for both scenarios.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.