Last updated on JULY 09, 2014
Applies to:Oracle Fleet Management - Version: 6.0 to 6.0.3
This problem can occur on any platform.
A Driver has been configured with an Activity Calendar that defines the Drivers' Work Period. This Work Period is defined with an Effective and Expiration Date. A shipment is created from an Order Release. This Order Release has Pickup Date that is NOT within the Effective/Expiration for the Work Profile.
When the Driver is assigned to the Shipment via "Fleet and Asset Management->Assign Driver" actions, the Shipment is adjusted to the defined Start Time of the Work Period.
It is not expected that that this Work Period is in use as the Shipment Start Time is not within the effective times of the Work Period, therefore the shipment should not be adjusted.
Note: If the Effective Date is updated to be outside of the Shipment's times (i.e. after delivery), then the Start Time remains unaffected by the Activity Calendar.
-- Steps To Reproduce:
1. Create a Driver with Work Period, with a defined Effective/Expiration date
2. Create a Shipment that has a Start Time that is NOT within this Effective range
3. Assign this Driver to this shipment using Actions: Fleet and Asset Management->Assign Driver
4. Notice that the results show that the Shipment Start Time is adjusted to the Start Time of the Calendar defined in the Work Period
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