My Oracle Support Banner

Driver Assignment Fails For Orders With A Fixed Delivery Datetime And Activity Time On The Last Stop (Doc ID 1339374.1)

Last updated on JULY 20, 2024

Applies to:

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

Symptoms


When Building a shipment on an order which has Fixed Pickup and Delivery Dates, a Driver is unable to be unassigned to a shipment, even when it has never been assigned to a shipment before and has a home location the same as the source location on the shipment.

ERROR
-----------------------
The shipment graph has no feasible solution: Time infeasible; Location not checked; Carrier capacity not checked. Shipment: <DOMAIN NAME>.01470 is Time infeasible; Location not checked; Carrier capacity not checked.<ServiceTimeResult for shipment: SH.01470 feasibility: Service time is infeasible. Stop: 2 at location: null No overlap between work period and time window. startTime: 2011-06-27 10:00:00 America/Chicago endTime: 2011-06-30 09:28:00 America/Chicago infeasibleAmount: null # of stops: 2>


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Setup:

Create a shipment on an order with the following dates:

Early Pickup Date 2011-06-27 10:00 America/Chicago
Late Pickup Date 2011-06-27 10:00 America/Chicago
Early Delivery Date 2011-06-30 08:28 America/Chicago
Late Delivery Date 2011-06-30 08:28 America/Chicago


To Replicate:

1. Log into OTM.
2. Search for Shipment created..
3. Select and go to Actions --> Fleet Management --> Assign --> Driver.
4. Select a valid Driver in the Driver ID field.
5. Click Ok.
6. Note the Error:

The shipment graph has no feasible solution: Time infeasible; Location not checked; Carrier capacity not checked. Shipment: <DOMAIN NAME>.01470 is Time infeasible; Location not checked; Carrier capacity not checked.<ServiceTimeResult for shipment: SH.01470 feasibility: Service time is infeasible. Stop: 2 at location: null No overlap between work period and time window. startTime: 2011-06-27 10:00:00 America/Chicago endTime: 2011-06-30 09:28:00 America/Chicago infeasibleAmount: null # of stops: 2>

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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