In SIM, the Same Transfer Can Be Received Twice (Even After Applying the Fix for Bug 19496344) (Doc ID 2088678.1)

Last updated on DECEMBER 15, 2015

Applies to:

Oracle Retail Store Inventory Management - Version 13.0.2 and later
Information in this document applies to any platform.

Symptoms

The same transfer in the Store Inventory Management (SIM) application can be received twice.  Even though the fix for <Bug 19496344> has been applied, duplicate receiving can be done for the same transfer with a slightly different scenario.


Steps to Reproduce:

  1. Log in to SIM as user A.
  2. Go to Shipping/Receiving -> Transfers.
  3. Create and dispatch transfer from store (1) to store (2) with one item and one quantity.
  4. Go to the store (2).  Find transfer from step 3 and show details.  Leave this instance of SIM on the details screen.
  5. Log in to SIM from a different machine.
  6. Find the transfer from step 3 and try to show details (a prompt related to breaking the record lock should appear).
  7. Leave SIM instance with prompt window on the screen.
  8. Go back to the session in step 4 and try to receive the transfer. Transfer has been correctly received (related transfer in has been generated).
  9. Go back to the session in step 7 and press Yes. Transfer details are shown on the screen.
  10. Fill Qty Received field and try receive transfer from step 9. Error message appears, stating that only dispatched transfers may be received.
  11. Press Done button. Transfer changes back status to In Progress (ERROR).  Second related transfer in has been generated in tables DO_CTL_INV and TR_LTM_ICD_MR.
  12. Choose transfer from the list, show details, and try to receive again. Transfer is correctly received a second time (ERROR).


Business Impact:

SIM - Transfer out has two related transfers in. SOH (Stock On Hand) in the destination location has been added twice; additionally, in transit quantity in the destination location in the RK_STORE_ITEM_SOH table is now negative.
RMS (Retail Merchandising System) - SOH in the source location has been decreased twice; SOH in the destination location has been added twice. Transfer has duplicated received quantity (TSFDETAIL table).

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