Deletion of a Return Creates a Mismatch in RMS Non-Sellable Inventory
Last updated on JULY 03, 2017
Applies to:Oracle Retail Store Inventory Management - Version 13.1.4 to 13.1.9 [Release 13.1]
Information in this document applies to any platform.
In Store Inventory Management (SIM) 13.1.x, we find that when a Return To Warehouse (RTW) is created with an item that has unavailable inventory, and if the RTW is created to return the unavailable inventory back to the warehouse, SIM creates an unnecessary inventory adjustment with reason code as "Returns" and publishes it to Retail Merchandising System (RMS). When RMS consumes the incoming inventory adjustment message, the unavailable stock increases in RMS and the Stock On Hand (SOH) between SIM and RMS go out of synch.
Steps to Reproduce:
- Find an item+store combination, and ensure that the item has some unavailable inventory.
- Create a RTW for this item, so that the return is created for the entire unavailable inventory. Ensure that you select "Yes" at the prompt that asks if the unavailable inventory should be used. Also ensure that the reason code selected is "Unavailable inventory".
- Click on 'Done' (do not click on 'Dispatch') and note that SIM publishes an InvAdjCre message as well as a SoStatusCre message to RMS.
- Delete the RTW from Step 2 that is in 'Pending' status.
- Observe that SIM only publishes the 'SoStatusMod' message to RMS.
- Check the ITEM_LOC_SOH database table in RMS and note that the NON_AVAILABLE_QTY has increased by the RTW quantity, whereas the RK_STORE_ITEM_SOH.ADJUST_UNAVAIL_QTY value in SIM is reset back to the original unavailable quantity.
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