Transfer Expected and Transfer Reserved Quantities Not Released After Returning a Partially Shipped Warehouse Based Allocation

(Doc ID 1602314.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Merchandising System - Version and later
Information in this document applies to any platform.


In Retail Merchandising System (RMS) India Localization release, for a warehouse based allocation, after distribution in the warehouse, the Transfer Reserved and Transfer Expected buckets in ITEM_LOC_SOH table are getting updated.

For example, if the Allocated quantity for item # A is 20 units, after approving the allocation, the 'Tsf Reserved' bucket of the ITEM_LOC_SOH table will show 20 units at the sending location, and the 'Tsf Expected' bucket at the receiving location will also show 20 units.   Suppose the distributed/picked quantity is only 8 units.  In this case, the 'Tsf Reserved' and 'Tsf Expected' buckets are getting updated to 8 units respectively.  Hence, when the expiry message is sent from Retail Warehouse Management System (RWMS) after the Pick Not After date is crossed, the 'Tsf Reserved' and 'Tsf Expected' buckets are going negative.  Also, after performing a Return to Stock operation for the units that were not shipped (and after passing the expiry from RWMS and running the docclose batch), the allocation is not getting closed.

Steps to Reproduce:

1. Create a WH Based allocation in Oracle Retail Allocation for an item for two stores.
2. Approve the allocation.
3. Distribute/Pick the quantity using the RWMS application.  For one store, distribute equal to the allocated quantity and for the second store distribute less than the allocated quantity.
4. Check the impact in ITEM_LOC_SOH table after completing the picking.
5. Ship less than the distributed quantity.
6. Receive less than the Shipped qty at stores using Store Inventory Management (SIM).
7. For the short received qty, ‘SL’ is booked as the system option is set accordingly.
8. Pass the return to stock in RWMS for the Picked – Shipped qty.
9. Check the impact in ITEM_LOC_SOH table after completing Step 8.
10. Send the expiry message from RWMS.
11. Check the impact in ITEM_LOC_SOH table after completing Step 10.
12. Run the docclose batch. Observe that the DOC_CLOSE_QUEUE table still contains the corresponding records.

The allocation is not getting closed. (Also note that multiple records are entered in the DOC_CLOSE_QUEUE table).


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