Interface Trip Stop Fails with Error: Invalid Location Due To Inactive Ship From Location
(Doc ID 2254176.1)
Last updated on MARCH 22, 2023
Applies to:
Oracle Shipping Execution - Version 12.2.3 and laterInformation in this document applies to any platform.
Symptoms
When attempting to run the Interface trip stop it completes with the following error:
ERROR
______________
Entering WSH_UTIL_VALIDATE.VALIDATE_LOCATION (WSHUTVLB.pls 120.16) (03/29/2017 05:12:55 PM)
P_LOCATION_ID ==> 179
P_LOCATION_CODE ==>
p_isWshLocation ==> FALSE
p_caller ==>
Calling Transfer_Location ==>
Entering WSH_MAP_LOCATION_REGION_PKG.TRANSFER_LOCATION (WSHMLORB.pls 120.19) (03/29/2017 05:12:55 PM)
p_caller ==>
Exiting WSH_MAP_LOCATION_REGION_PKG.TRANSFER_LOCATION (03/29/2017 05:12:55 PM, 0 seconds)
l_return_status ==> S
Entering WSH_UTIL_CORE.ADD_MESSAGE (WSHUTCOB.pls 120.27.12020000.3) (03/29/2017 05:12:55 PM)
P_MESSAGE_TYPE ==> E
P_MODULE_NAME ==> wsh.plsql.WSH_UTIL_VALIDATE.VALIDATE_LOCATION
msg_buffer ==> Invalid location.
E:Invalid location.
Exiting WSH_UTIL_CORE.ADD_MESSAGE (03/29/2017 05:12:55 PM, 0 seconds)
Exiting WSH_UTIL_VALIDATE.VALIDATE_LOCATION - EXCEPTION G_EXC_ERROR (03/29/2017 05:12:55 PM, 0 seconds)
Entering WSH_UTIL_CORE.ADD_MESSAGE (WSHUTCOB.pls 120.27.12020000.3) (03/29/2017 05:12:55 PM)
P_MESSAGE_TYPE ==> E
P_MODULE_NAME ==>
msg_buffer ==> Invalid location
Exiting WSH_UTIL_CORE.ADD_MESSAGE (03/29/2017 05:12:55 PM, 0 seconds)
Entering WSH_UTIL_CORE.GET_MESSAGES (WSHUTCOB.pls 120.27.12020000.3) (03/29/2017 05:12:55 PM)
P_INIT_MSG_LIST ==> N
Exiting WSH_UTIL_CORE.GET_MESSAGES (03/29/2017 05:12:55 PM, 0 seconds)
Error: Invalid location
WSH_XC_INVALID_LOCATION exception has occured.
P_LOCATION_ID ==> 179
P_LOCATION_CODE ==>
p_isWshLocation ==> FALSE
p_caller ==>
Calling Transfer_Location ==>
Entering WSH_MAP_LOCATION_REGION_PKG.TRANSFER_LOCATION (WSHMLORB.pls 120.19) (03/29/2017 05:12:55 PM)
p_caller ==>
Exiting WSH_MAP_LOCATION_REGION_PKG.TRANSFER_LOCATION (03/29/2017 05:12:55 PM, 0 seconds)
l_return_status ==> S
Entering WSH_UTIL_CORE.ADD_MESSAGE (WSHUTCOB.pls 120.27.12020000.3) (03/29/2017 05:12:55 PM)
P_MESSAGE_TYPE ==> E
P_MODULE_NAME ==> wsh.plsql.WSH_UTIL_VALIDATE.VALIDATE_LOCATION
msg_buffer ==> Invalid location.
E:Invalid location.
Exiting WSH_UTIL_CORE.ADD_MESSAGE (03/29/2017 05:12:55 PM, 0 seconds)
Exiting WSH_UTIL_VALIDATE.VALIDATE_LOCATION - EXCEPTION G_EXC_ERROR (03/29/2017 05:12:55 PM, 0 seconds)
Entering WSH_UTIL_CORE.ADD_MESSAGE (WSHUTCOB.pls 120.27.12020000.3) (03/29/2017 05:12:55 PM)
P_MESSAGE_TYPE ==> E
P_MODULE_NAME ==>
msg_buffer ==> Invalid location
Exiting WSH_UTIL_CORE.ADD_MESSAGE (03/29/2017 05:12:55 PM, 0 seconds)
Entering WSH_UTIL_CORE.GET_MESSAGES (WSHUTCOB.pls 120.27.12020000.3) (03/29/2017 05:12:55 PM)
P_INIT_MSG_LIST ==> N
Exiting WSH_UTIL_CORE.GET_MESSAGES (03/29/2017 05:12:55 PM, 0 seconds)
Error: Invalid location
WSH_XC_INVALID_LOCATION exception has occured.
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 |