Backorder Via Ship Confirm Fails With Error: The Update Is Not Allowed Because The Source Line Number Is WMS Controlled
(Doc ID 2863664.1)
Last updated on SEPTEMBER 13, 2023
Applies to:
Oracle Shipping Execution - Version 12.2.10 and laterOracle Warehouse Management - Version 12.2.10 and later
Information in this document applies to any platform.
Symptoms
Attempting to backorder a delivery detail via Ship Confirm > Backorder All option and the following error is raised:
ERROR
-----------------------
Error: Some deliveries selected for Ship Confirm have errors or warnings.
Error: The update is not allowed because the source line number is WMS controlled.
Unexpected Error : Quantity 20 could not be unreserved for delivery detail id xxxxx.
Error: The update is not allowed because the source line number is WMS controlled.
Unexpected Error : Quantity 20 could not be unreserved for delivery detail id xxxxx.
Shipping Debug file shows the following additional error:
AFTER CALLING WSH_INTERFACE.PROCESS_RECORDS E
ERROR IN WSH_INTERFACE.PROCESS_RECORDS / UPDATE_INVENTORY_INFO
Exiting WSH_INTERFACE.UPDATE_SHIPPING_ATTRIBUTES
wf_update_after_inv_unreserv: CTO:Failed in WSH_INTERFACE.update_shipping_attributes:
LEAVING OE_MSG_PUB.ADD
wf_update_after_inv_unreserv: unexp error in CTO_WORKFLOW_API_PK.wf_update_after_inv_unreserv::stmt number 50
LEAVING OE_MSG_PUB.COUNT_AND_GET 1
AFTER CALLING INVS DELETE_RESERVATION: U
FND_API.G_EXC_UNEXPECTED_ERROR exception has occured.
Exiting WSH_DELIVERY_DETAILS_ACTIONS.UNRESERVE_DELIVERY_DETAIL -
EXCEPTION:FND_API.G_EXC_UNEXPECTED_ERROR
l_return_status ==> U
Entering WSH_UTIL_CORE.ADD_MESSAGE (WSHUTCOB.pls 120.27.12020000.18)
P_MESSAGE_TYPE ==> U
P_MODULE_NAME ==> wsh.plsql.WSH_SHIP_CONFIRM_ACTIONS2.BACKORDER
U:Quantity 20 could not be unreserved for delivery detail xxxxxx.
Exiting WSH_UTIL_CORE.ADD_MESSAGE (03/08/2022 03:58:57 PM, 0 seconds)
BACKORDER_ERROR exception has occured.
Exiting WSH_SHIP_CONFIRM_ACTIONS2.BACKORDER - EXCEPTION:BACKORDER_ERROR
AFTER CALLING WSH_INTERFACE.PROCESS_RECORDS E
ERROR IN WSH_INTERFACE.PROCESS_RECORDS / UPDATE_INVENTORY_INFO
Exiting WSH_INTERFACE.UPDATE_SHIPPING_ATTRIBUTES
wf_update_after_inv_unreserv: CTO:Failed in WSH_INTERFACE.update_shipping_attributes:
LEAVING OE_MSG_PUB.ADD
wf_update_after_inv_unreserv: unexp error in CTO_WORKFLOW_API_PK.wf_update_after_inv_unreserv::stmt number 50
LEAVING OE_MSG_PUB.COUNT_AND_GET 1
AFTER CALLING INVS DELETE_RESERVATION: U
FND_API.G_EXC_UNEXPECTED_ERROR exception has occured.
Exiting WSH_DELIVERY_DETAILS_ACTIONS.UNRESERVE_DELIVERY_DETAIL -
EXCEPTION:FND_API.G_EXC_UNEXPECTED_ERROR
l_return_status ==> U
Entering WSH_UTIL_CORE.ADD_MESSAGE (WSHUTCOB.pls 120.27.12020000.18)
P_MESSAGE_TYPE ==> U
P_MODULE_NAME ==> wsh.plsql.WSH_SHIP_CONFIRM_ACTIONS2.BACKORDER
U:Quantity 20 could not be unreserved for delivery detail xxxxxx.
Exiting WSH_UTIL_CORE.ADD_MESSAGE (03/08/2022 03:58:57 PM, 0 seconds)
BACKORDER_ERROR exception has occured.
Exiting WSH_SHIP_CONFIRM_ACTIONS2.BACKORDER - EXCEPTION:BACKORDER_ERROR
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. OM Super User Responsibility
2. Shipping > Transactions
3. Query delivery
4. Select ship confirm
5. Select backorder all option in the ship confirm window
6. Error is raised
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |