Transfers and Returns Are Created in RMS With Double the Quantity Created in SIM
Last updated on OCTOBER 27, 2016
Applies to:Oracle Retail Merchandising System - Version 13.2.4 to 13.2.7 [Release 13.2]
Oracle Retail Store Inventory Management - Version 13.2.4 and later
Oracle Retail Merchandising System - Version 13.1 to 13.1.9 [Release 13.1]
Information in this document applies to any platform.
Transfers and returns are sometimes created in Retail Merchandising System (RMS) with double the transfer/return quantity requested in Store Inventory Management (SIM).
The Save and Dispatch functions in SIM are necessarily sequential. However, these operations are reflected in RMS using asynchronous RIB messaging (SOStatusDesc and ASNOutDesc). This problem happens only when RMS consumes the ASNOut message first; when the SOStatus is consumed first, the quantities are reflected properly. Specifically, when RMS consumes ASNOut, it checks if related a transfer or return exists. If this message is consumed first, RMS creates a new transfer/return. Later, when the SOStatus message is consumed, RMS checks that a transfer has been already created; the quantity from SOStatus is then added to the transfer quantity and ITEM_LOC_SOH.TSF_RESERVED_QTY.
Steps to Reproduce:
1. Log in to RMS. Check the quantities in RMS ITEM_LOC_SOH table: STOCK_ON_HAND and TSF_RESERVED_QTY.
2. Log in to SIM and create a store to store transfer for 2 quantity and dispatch it without leaving the transfer detail screen.
3. Log in to RMS and check that there is a doubled TSF_QTY = 4 (should be 2). Check also the ITEM_LOC_SOH table and note that the TSF_RESERVED_QTY = 2 (should be 0).
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