How to Synchronize Physical Purge Between RMS and SIM at Transaction Item (SKU)/Location Level
(Doc ID 2723255.1)
Last updated on APRIL 19, 2021
Applies to:Oracle Retail Merchandising Foundation Cloud Service - Version 16.0 and later
Information in this document applies to any platform.
When a transaction level Item (SKU)/Location is marked for Deletion (Status D) on RMS Cloud same information is passed to Store Inventory Management (SIM) where, it also marked for Deletion.
Now when you run the batch process to physically delete, SKUs may not be purged on both RMS and SIM on the same day.
RMS batch process may find pending some transactions pertaining to that SKU which will prevent the SKU from being purged from RMS.
Whereas on the SIM side it could get deleted if there are no pending transaction items.
In a typical scenario an item/location which is marked for Deletion in RMS may stay in that state for couple of months, whereas on the SIM side, it could get deleted sooner.
This is the current status of the way purging works, and this could lead out of Sync between RMS and SIM with respect to SKUs.
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