Wrong Status and SOH Updates of Serialized Items when a Received Transfer is Adjusted (Doc ID 2026136.1)

Last updated on MARCH 30, 2016

Applies to:

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

Symptoms

In Store Inventory Management (SIM) application, find that when a transfer containing serialized and non-serialized items is adjusted:


1. The Stock On Hand (SOH) updates for the sending store is wrong
2. The status of the UIN at the receiving store is incorrect
3. Once a UIN is received during transfer adjust, the UIN is not available at the receiving store, though it's stock on hand is increased.
4. The UIN from Step 3 above is still available at the sending store, and the SOH of the serialized item is not reduced
5. If the system option TSF_FORCE_CLOSE_IND is set to 'SL', then after transfer adjust, the SOH at the sending store is not updated

Steps to recreate:

Testcase 1:


System option: Transfer Force Close Indicator: No Loss

1. Find two stores where serialized and non-serialized items are available
2. Query SIM database table STORE_ITEM_STOCK and note down the SOH of the items at both stores
3. Query SIM database table ITEM_UIN and note down the UINs of the serialized item at the sending store (Store A)
4. Create a store to store transfer from Store A to Store B with quantities shown below as example:
Non-serialized item: Quantity: 3
Serialized item: Quantity 2: UIN1 and UIN2
5. Dispatch the transfer and note the SOH of the items and UINs
6. Log into Store B and receive the transfer as follows:
Non-serialized item: Quantity: 2
Serialized item: Quantity 1: UIN1
7. Confirm and note the SOH using the database tables and note that the short received quantities are added back to the SOH of the sending store (Store A)
8. Now re-open the received transfer and click on 'Adjust'
9. Choose to adjust the received transfer
10. Enter the quantities as below:
Non-serialized item: Original shipped Quantity: 3, previous received quantity: 2....Adjust the quantity to 3
Serialized item: Original shipped Quantity 2: UIN1 and UIN2 - Previous received quantity: 1 with UIN1.
11. Click on UIN qty field and note that both UINs are shown. However, note that the status of both UINs are shown as "In Stock"
12. Since UIN2 is not yet received, it should be in "Shipped to Store" status...not "In Stock" at Store B
13. Add the missing UIN (UIN2) and confirm the receipt
14. Query STORE_ITEM_STOCK and ITEM_UIN tables and note the following:
STORE_ITEM_STOCK: Does not show SOH updates at the sending store for the adjusted transfer receipt.
15. Note that:
a, The readjusted stock is not updated for either item at the sending Store (Store A)
b. The UIN that is received during adjust of transfer does not show at the receiving Store (Store B), but it's SOH is increased

Testcase 2:

Steps to recreate:

1. Pre-Requisite: Transfer Force Close Indicator  =  'Sending Loss' and Parameter `Number of days received transfer can be adjusted value > 0
2. Create a store to store transfer with the following items:
   a. Regular item: with a quantity of 5
   b. UIN item with two UINs: UIN1, UIN2
3. Note the SOH of both items at both stores. For example
   a. At Store A: Regular item SOH: 20, UIN Item: 6.
   b. At Store B: Regular Item SOH: 46, UIN item SOH: 9
4. Dispatch the transfer from Store A
5. Log into Store B and receive the incoming transfer as follows:
   a. Regular item: with a quantity of 3
   b. UIN item with on UINs: UIN1
6. Note the SOH of both items at both stores:
   a. Store A: Regular item: 15, UIN: 4
   b. Store B: Regular: 49, UIN: 10) a. At Store A, the missing UIN marked as "Missing" - This is correct
7. In Store B, re-open the transfer and adjust the delivery
8. Enter the quantity as: - (i.e. receive all the quantity)
   a. Regular item: with a quantity of 5
   b. UIN item with two UINs: UIN1, UIN2
9. Check the SOH of the items at both stores:
   a. At Store A: Regular item SOH: 15, UIN Item: 3.
   b. At Store B: Regular Item SOH: 51, UIN item SOH: 11
10. Note that for the UIN item, the SOH at sending store (Store A) is updated wrongly - the SOH of UIN item should be 4, not 3 as the test case shows).

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