My Oracle Support Banner

Salesprocess Creates TRAN_DATA_HISTORY for Closed Periods Back to Orig Price Hist Date (Doc ID 2352179.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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


RPM/RMS 15.0.1, Batches issue

When a sales return comes for a location on the current date and the item was not ranged to that location, then data is incorrectly inserted into the TRAN_DATA_HIST table.
This should have written a Tran_Date of the first date of the open month and not for a closed period.

The issue can be reproduced with the following steps:
1. Take an item that is already clearanced out and is set to 0 retail at a Style/Color level in RFR table for some past date in previous months or years.
2. Check the item loc ranging of the item.  Item should be ranged to a few locations, but not all.
3. Check the Item's original retail. Say it is 24.99, but the clearance retail at all locations should be 0.
4. Check the Unit_Retail on ITEM_LOC table and you will see it is 0.00 for all locations.
5. Check the Item on Price_Hist.
6. Now pick a location that is not ranged.  (Example: location 7661)
7. Bring a Return transaction for the NON ranged location via POSU/Sales process. Return the item at original retail.
8. Observe that data is written to ITEM_LOC, PRICE_HIST, TRAN_DATA tables with current date (today's date).
9. Run new item Loc batch. Observe that RPM_ITEM_LOC gets populated for loc 7661.
10. Now run the PriceEventExecution batch for RMS and observe the following:
      ...Price_hist gets created for tran_type = 8 for 0 retail.
      ...ITEM_LOC.unit_retail gets updated to 0 from 24.99.
      ...TRAN_DATA (Tran_data_history after batches have completed) will record 26th DEC 2016 entry for tran_code 16 for total retail of 24.99.
      ...At this point TRAN_DATA for the same item will have 2 records. ie One for Tran_date = 26-Jul-2017 and one for Historical period date of 26-DEC-2016.




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.