UseUnavailableInventory Field Is Not Working As Expected In Create Transfer Rest API
(Doc ID 3077233.1)
Last updated on MARCH 17, 2025
Applies to:
Oracle Retail Enterprise Inventory Cloud Service - Version 24.1 to 25.0 [Release 24.1 to 25.0]Information in this document applies to any platform.
Symptoms
On : 24.1 version, Integration
ACTUAL BEHAVIOR
---------------
useUnavailableInventory field is not working as expected in create transfer rest API
REST WS ///siocs-int-services/api/transfers
If this field is populated as true, ideally USE_AVAILABLE in tsf table should be 'N'. However this behaving in opposite way.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send the request with "useUnavailableInventory" = true
Request
{
"sourceStoreId": 102,
"destinationLocationType": 1,
"destinationLocationId": 103,
"notAfterDate": "",
"authorizationCode": "1111",
"useUnavailableInventory": true,
"allowPartialDelivery": true,
"contextTypeId": 101,
"contextValue": "C",
"contextTypeId": 1,
"contextValue": "124",
"lineItems": [
{
"itemId": "100020001",
"quantity": 1
}
],
"notes": [
"Transfer needs to be rushed.",
"Items are in the back room."
]
}
2. Check the TSF table for the USE_AVAILABLE field
Due to this issue, users will be confused as the field appears to do the opposite of what it says.
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 |