Regular Price Change Modifications Are Not Processed Correctly in SIM
Last updated on JANUARY 11, 2016
Applies to:Oracle Retail Store Inventory Management - Version 13.1.6 to 13.1.9 [Release 13.1]
Information in this document applies to any platform.
This article will be updated as official patch becomes available.
When a Regular Price Change is modified in THE Retail Price Management (RPM) system, the new changes are not effective in Retail Store Inventory Management (SIM). The new price change is deleted and the Item's price is reset to the original price.
Steps to Recreate:
- Create a regular price change for an item at a store in RPM (for example, original price of the item is $5 and the new regular price change is created with a price of $10), effective tomorrow (i.e. vdate + 1).
- Approve the price change. The price change flows to SIM.
- Run ActivatePriceChanges.sh batch (optional).
- Query SIM database table and note the status of the price change (it should be 3 - completed).
- Look up the item using SIM and note that the price change is effective (steps 4, 5 and 6 are optional).
- In RPM, edit the price change and set the status to "Worksheet".
- Modify the price (for example, set it to $15 (previous price change was from $5 to $10)) and approve.
- Note that RPM publishes two messages to SIM: first message: "REGPRCCHGDEL" followed by another: "REGPRCCHGCRE".
- Query SIM database table and note the status of the price change (it should be 9 - Deleted).
- Query SIM database table INTEGRATION_STAGING and note that all three messages (the original REGPRCCHGCRE from step 3, the REGPRCCHGDEL from step 9, and REGPRCCHGCRE from step 9) are marked as processed.
- Look up the item using SIM and note that the price change is reverted back to its original price change from step 1 (i.e. $5).
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