My Oracle Support Banner

What If The Automation Agent Shipment Appointment Tracker Doesn't Work? (Doc ID 740395.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Transportation Management - Version 5.5.04 and later
Information in this document applies to any platform.


When scheduling an Appointment Action for an existing shipment, it is expected that the estimated arrival time is recalculated because of the Public Automation Agent SHIPMENT APPOINTMENT TRACKER. But the Agent doesn't run.

For example:

A shipment is created by bulk planning. It has 2 stops. The estimated arrival time for the second stop is 19.00. The dock door resource calendar has a receive activity from 10:00 until 18:00.
Click 'actions' -> Dock Scheduling -> Schedule Appointment for the second stop.
In the Manage Appointments window, the shipment is now scheduled for 10.00 the next day
The public Automation Agent SHIPMENT APPOINTMENT TRACKER is active and supposed to listen to SHIPMENT - APPOINTMENT SCHEDULED and perform RECALC STOP APPOINTMENT TIMES. The parameters of this Action are:
Late Threshold - 30 min
Redrive - selected
Number of Downstream Shipments -1

But no recalculation takes place. The estimated arrival time for the second stop remains at 18.39. 


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.