Fulfillment Orders Retry on Status X - Leaves No Stock Available
(Doc ID 2986813.1)
Last updated on NOVEMBER 14, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 16.0 and laterInformation in this document applies to any platform.
Symptoms
Customer reports when calling FulfillOrderService if the item doesn't have stock they have the following error:
"Unable to create transfer due to out of stock,verify ORDCUST table key values are assignmentRef ----------- fulfilment id ----------"
Following this when the stock is made available and is called a second time the following error appears:
"The customer order number/fulfill order number/source loc ID/fulfill loc ID combination already exists in ordcust. Customer order no ----------------, Fulfill order no -----------------.."
This is not resolved by cancelling the order due to data remaining in the RMS tables. The webservice is called by bespoken OMS, IDs cannot be changed.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1 - confirm there is no stock for the item/loc
2 - publish the webservice message
3 - confirm return is Status X with the locking error: "Unable to create transfer due to out of stock,verify ORDCUST table key values are assignmentRef XXXXXXXXX fulfilment id XXXXXXXXX"
4 - confirm data exists in ORDCUST_% tables
5 - retry the same message to get the error "The customer order number/fulfill order number/source loc ID/fulfill loc ID combination already exists in ordcust. Customer order no XXXXXXXXX, Fulfill order no XXXXXXXXX.."
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 |