E2E: Allocation ReST API Is Swapping Physical And Virtual WH Locations On Allocation Publication (Doc ID 3077892.1)

Last updated on MARCH 27, 2025

Applies to:

Symptoms

On : 24.1.301.3.1 version

ACTUAL BEHAVIOR
---------------
For both Pre-allocations and WH allocations, the MERCHAPI_EXT_ALLOC has the incorrect values in PhysicalToLocation and ToLocation. This API is publishing the PhysicalToLocation with a virtual WH ID and publishing the ToLocation with a physical WH ID


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use the /services/inventory/allocations/create to create either a WH allocation or a Pre-allocation
2. Ensure that the to_location on the allocation is another VWH in a different Physical WH
3. Validate that ALLOC_HEAD and ALLOC_DETAIL are populated correctly once the API has processed the payload
4. Now use the /services/inventory/allocation OR /services/inventory/allocation/{allocNo} ReST API to retrieve the Allocation from step 1
5. Notice that the PhysicalToLocation has a VWH ID and the toLocation has a Physical WH ID
6. Also, check the MERCHAPI_EXT_ALLOC table for the same allocation. This table also shows that the WH location ID's have been swapped incorrectly.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.