Planned Shipment Interface Errors with No timezone was found for ID 539.HZ_API_RETURN_ERROR
(Doc ID 1917500.1)
Last updated on AUGUST 14, 2018
Applies to:Oracle Shipping Execution - Version 188.8.131.52 and later
Information in this document applies to any platform.
When running Planned Shipment Interface to interface date from OTM to EBS , records are erroring and getting stuck in the Shipment Interface Messages Corrections form:
OTM sent Planned Arrival Date ==> 07/18/2014 12:01:00 AM
OTM sent Planned Departure Date ==> 07/18/2014 12:01:00 AM
Entering WSH_TMS_RELEASE.GET_SERVER_TIME (WSHTMRLB.pls 115.2.11510.19) (07/17/2014 01:34:55 PM)
p_source_timezone_code : US/Mountain
p_source_time : 18-JUL-2014 00:01:00
Server tz id :1
Returning time :
Get Server Time for Planned Arrival Date, l_return_status: ==> E
No timezone was found for ID 539.HZ_API_RETURN_ERROR
There was an error processing the interface data from Oracle Transportation Management.
The issue can be reproduced at will with the following steps:
1. Order Management Super User Responsibility
4. Messages Corrections
5. Highlight errored transactions
6. select process
Time zone was changed on customer record.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|