Update Appointment Time on Not Using Local Time Zone
Last updated on JULY 03, 2017
Applies to:Oracle Transportation Management - Version 6.4.1 to 6.4.3 [Release 6.4]
Information in this document applies to any platform.
On : 6.4.1 version, Business Process Automation
A Tracking Event Agent is configured to run the action: UPDATE APPOINTMENT TIMES. When this action stores the time in SHIPMENT_STOP.APPOINTMENT_DELIVERY, it is storing the literal value provided on the XML instead of converting it to the local time zone of that stop.
It is expected when viewing the shipment stop details in the UI to see the converted time zone.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms