Location Calendar Not Being Considered While Planning. (Doc ID 764175.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Operational Planning - Version: 5.5.04.01
This problem can occur on any platform.

Symptoms

Although the help defines the use of Interim legs (defined on itineraries), if calendars are defined for the interim locations, they are not taken into consideration for planning purposes..

The online help for an itinerary leg reads:

A leg interim point adds one or more stops between the source and destination locations. For example, you can use interim points to identify a border crossing or a stop over during the night. An interim point is a reference point for shipment activity, where nothing is loaded or unloaded from the equipment.

The help also defines the various calendar activity definitions:

Load indicates that the location is open for loading goods onto equipment.
Receive indicates that the location is open for receiving goods.
Other means interim stop or via point stops; no pickup or dropoff at these stops. Interim stops model border crossing points as such. Via points are for arbitraries where on one shipment there could be more than one service provider.

Between the 2 points, it can be inferred that load/received cannot be used for interim stop locations. However, there were several clients thinking that they can assign a calendar for load/receive on an interim location and have service time take the calendar into consideration.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms