"Scheduling This drivable object has more than two nodes. Cannot drive!" Exception When Itinerary Has Depot Profile However Rate is Not Using Depot
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Operational Planning - Version 6.0 and later
Information in this document applies to any platform.
When attempting to plan an Order Release onto a Rate that uses a Rate Service of DistanceDuration, DayDuration or ExternalTransitDays, it fails to plan when the desired Itinerary includes a Depot Profile. The logs show the following:
Scheduling This drivable object has more than two nodes. Cannot drive!
Planning rate engine result 1 was filtered out due to rate service constraint. Contine to the next one
Since the rate is not marked as "Depot Applicable", the Depot Profile is not expected to be used. If the Depot Profile is removed from the itinerary.
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