RPM Location Move Schedule Batch Generates Duplicate RPM_FUTURE_RETAIL Records (Doc ID 2129299.1)

Last updated on MARCH 21, 2017

Applies to:

Oracle Retail Price Management - Version 14.1.1 to 14.1.2 [Release 14.1]
Oracle Retail Price Management - Version 14.0 to 14.0.4 [Release 14.0]
Information in this document applies to any platform.

Symptoms

The locationMoveScheduleBatch.sh batch generates duplicate records in the RPM_FUTURE_RETAIL (RFR) table when both the DZ (or DL) and IL timelines exist in RFR for the location that is being moved.

Steps to Reproduce:

  1. Create a new style and create a child item.
  2. Range it to a location.
  3. Run newitemlocbatch and verify the RFR table and make sure there is an entry for PZ for the style.
  4. Create a price change for the newly created Parent item Diff/Zone.
  5. Approve the same.
  6. Verify the RFR and make sure there is entry for Curr_hier DZ for the price changed item.
  7. Create a Promotion for the Parent Item Diff/Location.
  8. Approve the same.
  9. Verify the RFR and make sure there is entry for DL for the newly created parent item.
  10. Create a Clearance for the child item/location.
  11. Approve the item.
  12. Verify the RFR and make sure there is entry for IL for the newly created child item.
  13. Create locationmove for the location to a new location.
  14. Approve the same.
  15. Run the locationMoveSchedule batch.
  16. Verify that duplicates are created for the location in the RFR.

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