Transfers Created in SIM Are Reflected in RMS With Doubled Quantity

(Doc ID 1613685.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Merchandising System - Version 13.0.2 to 13.0.7 [Release 13.0]
Oracle Retail Store Inventory Management - Version 13.0 to 13.0.7 [Release 13.0]
Oracle Retail Merchandising System - Version 13.2 to 13.2.5 [Release 13.2]
Information in this document applies to any platform.

Symptoms

In some cases when Store to Store transfer is created in Oracle Store Inventory Management (SIM) and published to Oracle Retail Merchandising System (RMS), the transfer is created in RMS with double the transfer quantity requested in SIM and thus additional units are reserved in ITEM_LOC_SOH table.

When a transfer is dispatched in SIM two messages, SOStatus and ASNout are published.  The problem occurs only when RMS consumes the ASNOut message first. When the SOStatus is consumed first, the transfer gets created in RMS with the correct quantity.


Steps to Reproduce:

1. Log in to RMS. Check ITEM_LOC_SOH quantities: STOCK_ON_HAND = 7, TSF_RESERVED_QTY = 0
2. Log in to SIM and create a store to store transfer for 2 units and dispatch it without leaving transfer detail screen.
3. Log in to RMS and check the transfer quantity created there.

Note that the transfer is created with double the quantity requested in SIM, TSF_QTY=4 (should be 2). Check also ITEM_LOC_SOH table that there is TSF_RESERVED_QTY = 2 (should be 0)

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