Errors With Multi-leg Transfers Via External Finisher With Packing
(Doc ID 3077897.1)
Last updated on MARCH 25, 2025
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 24.1 and laterInformation in this document applies to any platform.
Symptoms
On : 24.1.301 version
When using multi-leg transfers via an External Finisher and Packing Instructions for the work order are added, base functionality allows for the 1) breakdown of a pack to its component items or 2) building of a pack from component items.
The following issues are noticed for each scenario:
1) breakdown of a pack to its component items: error when shipped the 2nd transfer via ReST API
2) building of a pack from component items: Tsf_reserved_Qty becomes negative for Finisher when shipping 2nd leg
ERROR
-----------------------
1. Exception when creating a shipment for 1st leg transfer from Rest API
2. Transfer reserved qty updated as negative on shipping 2nd leg transfer and stays same after receiving.
STEPS TO REPRODUCE:
-------------------------------------
1. Ensure that a pack item exists in the system and has inventory for the Pack item in the WH.
2. Pack item has Store pack Inventory checked, i.e. Notional pack Ind ='Y'
3. Also, make sure that the External finisher is setup as partner to auto receive: PARTNER.AUTO_RCV_STOCK_IND = "Y"
4. Create an Administrative transfer with from_loc as VWH, to_loc as same VWH with an external finisher. Add pack item to the transfer.
5. Add Packing information with explode pack option checked.
6. Add a workorder and approve the transfer.
7. Try to ship the transfer from the REST service outbound asn/create (Swagger/Postman) and note the exception : Cannot update (\"RMS01\".\"ITEM_LOC_SOH\".\"TSF_EXPECTED_QTY\") to NULL returned by program unit BOL_SQL.UPDATE_PACK_LOCS
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |