Last updated on AUGUST 01, 2017
Applies to:Oracle Retail Price Management - Version 188.8.131.52 and later
Oracle Retail Merchandising System - Version 184.108.40.206 and later
Oracle Retail Store Inventory Management - Version 12.0.5 and later
Information in this document applies to any platform.
Checked for relevance on 15-Feb-2010
Checked for relevance on 24-Oct-2011
Checked for relevance on 28-Mar-2013
Checked for relevance on 08-Sep-2014
Checked for relevance on 12-Feb-2016
Checked for relevance on 01-Aug-2017
Assuming Retail Merchandising System(RMS)/Retail Price Management(RPM) is configured to make use of the Retail Integration Bus(RIB) for communcation
(SYSTEM_OPTIONS.rpm_rib_ind = 'Y'). When a new item/location is added to RMS, it does not
flow to RPM (i.e. intial seed record never gets populated into RPM_FUTURE_RETAIL).
1) New item/location is added and approved in RMS.
2) Record gets inserted into ITEMLOC_MFQUEUE.
3) RIB picks up item from ITEMLOC_MFQUEUE, sends it to the RIB and removes from ITEMLOC_MFQUEUE.
4) Record gets picked up by RPM/RIB code and gets inserted into RPM_STAGE_ITEM_LOC.
5) Record remains in RPM_STAGE_ITEM_LOC and never gets inserted into RPM_FUTURE_RETAIL.
If one is configured to use the RIB for RMS-to-RPM communcation is there a need to run the NewItemLocBatch batch process and customer have the triggers on ITEM_LOC that insert into RPM_STAGE_ITEM_LOC disabled. Thus, the RPM code picks the new item/locations up from the RIB and puts into RPM_STAGE_ITEM_LOC, but never puts the records into RPM_FUTURE RETAIL.
Currently , one has to manually push the items into RPM_FUTURE_RETAIL, which is not the preferred
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms