Consecutive Price Change Is Updating Selling Retail Incorrectly in RPM_FUTURE_RETAIL Table (Doc ID 2098694.1)

Last updated on DECEMBER 12, 2016

Applies to:

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

Symptoms

The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.

Selling price updated incorrectly in RPM_FUTURE_RETAIL table for a consecutive emergency and future price change for the same item location combination.


Steps to Recreate:


1. Create an item and range the location in RMS.
2. Run Newitemlocbatch to range item-location in RPM.
3. Go to Price changes -> Create Price change in RPM.
4. Create regular price change for current Vdate and give change type as 'Change By Percent'. Give change percent as 10%.
5. Give item, location and apply the price change.
6. Approve the price change and check ITEM_RETAIL in ITEM_LOC and SELLING_RETAIL in RPM_FUTURE_RETAIL table.
7. Create another price change for the same item location combination and increment by 10%, ut give the effective date as vdate+1.
8. Check the SELLING_RETAIL in RPM_FUTURE_RETAIL table.

Expected:

Unit_retail -> 10
price change for Vdate (10%) - > 11
price change for Vdate+1 (10%) - > 12.1

Actual:

Unit_retail -> 10
price change for Vdate (10%) - > 12.1
price change for Vdate+1 (10%) - > 13.2

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