When Multiple Price Changes Overlap, Price Mismatch Occurs Between RMS and SIM

(Doc ID 2092829.1)

Last updated on MARCH 22, 2017

Applies to:

Oracle Retail Store Inventory 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 is already scheduled for future release.  This article will be updated as official patch becomes available.


In the Store Inventory Management (SIM) application, we find the following:

Scenario 1:
=========
  1. In Retail Price Management (RPM) application, if a regular price change is created for an item, for which a clearance/promotion is already in effect:
  2. Retail Merchandising System (RMS) and RPM show the current price as clearance price
  3. SIM shows the price as the new regular price change - SIM should show the ongoing clearance price same as RMS and RPM
  4. RMS and RPM reset the price to the regular price ONLY after the ongoing Clearance/Promotion is reset
  5. All applications (RMS, RPM, SIM) should reset the price to the newly created regular price, ONLY after the ongoing clearance/promotion is reset


Scenario 2:
=========
  1. In RPM, an ongoing clearance/.promotion was reset
  2. Both RMS and RPM change the item price back to it's original unit price or last regular price
  3. The SIM database table ITEM_PRICE and database view ITEM_PRICE_V both show the current price of the item as the item's original price or the last regular price
  4. However, SIM Item lookup (and other functional areas in the UI such as item ticket etc.) still show the clearance/promotion price that was reset


Steps to Recreate:

Scenario 1:
=========
  1. Ensure that RPM to SIM communication is set to RIB (NOT batch)
  2. In RPM, find an item at a store that does not have an on going clearance/promotion
  3. In RPM create a clearance/promotion for the item at that store for the same day (without an end date)
  4. Query RPM database table RPM_FUTURE_RETAIL and RMS database table ITEM_LOC to ensure that the price change is effective
  5. Approve and let the price change information flow to SIM
  6. Check in SIM (Item lookup or Item ticket) and ensure that the price shows as clearance/promotion for the item at the store
  7. In RPM, for the same item and store combination, create a same day regular price change
  8. Query RPM database table RPM_FUTURE_RETAIL and RMS database table ITEM_LOC and find that the retail price (ongoing price) of the item is shown as clearance/promotion price
  9. Approve and let the price change information flow to SIM
  6. Check in SIM (Item lookup or Item ticket) and find that the item price is shown as the new regular price - not as the clearance/promotion that both RPM and RMS show


Scenario 2:
========
  1. Ensure that RPM to SIM communication is set to RIB (NOT batch)
  2. In RPM, find an item at a store that is on an ongoing clearance/promotion
  3. Ensure that the price is shown as clearance/promotion in SIM also (item lookup or item ticket)
  4. In RPM, edit the ongoing clearance/promotion and modify it with an end date of today - i.e. reset the ongoing clearance/promotion using the same day price change
  5. Approve and let the price change information flow to SIM
  6. Query RPM database table RPM_FUTURE_RETAIL and RMS database table ITEM_LOC and find that the item retail price is set to it's original unit price or last known regular price
  7. Lookup the item in SIM using item look up or item ticket and find that the item price still shows as on clearance/promotion
  8. Query SIM database table ITEM_PRICE and find that the clearance/promotion is reset - i.e. database updates are successful, but UI does not show the price changes.


Changes

 

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