Item Deletion Information from RMS Application is Not Sent to ORPOS Through batch_orpos_extract.ksh (Doc ID 2026889.1)

Last updated on DECEMBER 16, 2015

Applies to:

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

Symptoms

Once items are deleted from the Retail Merchandising System (RMS) application, they are not getting deleted from Oracle Retail Point of Service (ORPOS), as batch_orpos_extract.ksh is not picking up the correct change_type. In place of DEL, ADD is getting picked up.
 

Steps to Reproduce:

  1. Create a transaction level item in RMS. TRAN_TYPE 1 and 2 gets populated in POS_MODS table.
  2. Run the batch orpos_extract.ksh and see that CHANGE_TYPE in ORPOS_PRELOAD_ITEM_TEMP is recorded as 'ADD' which is expected.
  3. Also the item gets exported to ORPOS.
  4. Now, mark the same item for deletion in RMS.
  5. While the item status is in 'Delete Pending' in RMS, update item_description and then see that TRAN_TYPE 10 gets populated in POS_MODS table.
  6. Execute dlyprg job to delete the item permanently which was in delete pending status.
  7. After deletion of item from RMS, TRAN_TYPE 21, 22 gets populated in POS_MODS table.
  8. Now run the batch_orpos_extract.ksh once again.
  9. See that the based on previous TRAN_TYPE's as 22,21,10,1,2, still the CHANGE_TYPE recorded in ORPOS_PRELOAD_ITEM_TEMP is 'ADD' instead of 'DEL'. 
    -  Issue is that the item deletion information is not going to ORPOS whereas the item was already deleted in RMS application.

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