The Removal of Clearance Resets in RPM Does Not Integrate Correctly With SIM When Using the Bulk Batch ClearancePriceChange.sh
Last updated on NOVEMBER 04, 2016
Applies to:Oracle Retail Store Inventory Management - Version 13.2.8 and later
Information in this document applies to any platform.
When a clearance reset is removed from Retail Price Management (RPM), it is not being removed from Store Inventory Management (SIM) by batch ClearancePriceChange.sh. The clearance reset still occurs on the day for which it was originally created, and it is returned to its regular retail price. This leaves the prices in SIM inconsistent with those in RPM, RMS, and other Retail applications.
Steps to Reproduce:
- In RPM, find (or create) an existing clearance which is active and with Reset Date as null.
- Create a clearance reset by populating reset date and approve it.
- Run the the following batch processes to integrate to SIM:
RPM: ClearancePriceChangePublishBatch.sh, ClearancePriceChangePublishExport.sh
- Look at RK_PRICE_CHANGE for the record. Note that an end date on the clearance is populated as expected.
- In RPM, delete the clearance reset (the reset date will be null).
- Repeat step 3.
- Look at RK_PRICE_CHANGE for the record. The end date of the clearance is incorrectly populated.
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