Rollup as Part of NewItemLoc (NIL) Batch Processing Is Populating RPM_FUTURE_RETAIL With Incorrect Clearance Data (Doc ID 2141266.1)

Last updated on OCTOBER 28, 2022

Applies to:

Symptoms

Rollup of data in RPM_FUTURE_RETAIL (RFR) table is not happening correctly.  The batch is populating an incorrect clearance ID and price for DL records when new items are ranged after price changes and clearances are created at zone level.

Steps to Reproduce :

1. Create a Item Parent with at least 4 Item Children having different DIFF_1 values.
2. Range 3 item children (with different DIFF_1) to a warehouse and to 2 stores which are part of the price change zone.
   Note : Ensure the 2 stores are part of clearance zone also and this zone has only stores.
3. Run the NEWITEMLOCBATCH.
4. Create a regular price change at Item Style level for price change zone for VDATE+1 as effective date.
5. Approve the price change.
6. Run the Price Event Execution (PEE) and PEERMS batches.  Verify the PRICE_HIST, ITEM_LOC and RFR table data.
7. Increase the VDATE to VDATE +1.
8. Create a different percentage off for the 4 items and parent/item diff level for clearance zone for VDATE+1 as effective date.
9. Approve the clearance .
10. Run the PEE and PEERMS batches and again verify the PRICE_HIST, ITEM_LOC and RFR table data.
11. Increase the vdate to VDATE +1.
12. Range a new location for 3 transactional item of the item parent that is part of price change zone and clearance zone.
13. Range a new warehouse to 1 transactional item where there was no ranging earlier and is part of price change zone.
14. Run the NEWITEMLOCBATCH.
15. verify the PRICE_HIST, ITEM_LOC and RFR table data.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.