My Oracle Support Banner

DRIVER ASSIGNMENT Status Error When Attempting to Unassign Driver From Relay Shipment (Doc ID 1307754.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Fleet Management - Version: 6.1.1 and later   [Release: 6.1 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to unassign a driver from a relay shipment, the following error occurs.

-- Error
2011-02-02 12:02:22.745 446259 Error Exception Status error for Shipment V1.06182
DRIVER ASSIGNMENT status must be one of the following: [DRIVER ASSIGNMENT_ASSIGNED, DRIVER ASSIGNMENT_COMMITTED]

at glog.business.action.comm.AbstractShipmentValidator.checkCanPerform(AbstractShipmentValidator.java:77)
at glog.business.action.fleetassignment.driver.ValidateUnassignDriverFromShipmentAction.preValidate(ValidateUnassignDriverFromShipmentAction.java:66)
at glog.business.action.shipment.AbstractShipmentPlanningAction.perform(AbstractShipmentPlanningAction.java:117)
at glog.business.action.fleetassignment.AbstractFleetShipmentPlanningAction.perform(AbstractFleetShipmentPlanningAction.java:95)
at glog.business.session.FleetAssignmentActionSessionBean.validateUnassignDriverFromShipment(FleetAssignmentActionSessionBean.java:677)
at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper.validateUnassignDriverFromShipment(FleetAssignmentActionSessionServerSideEJBWrapper.java:661)
at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.validateUnassignDriverFromShipment(FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.java:4166)
at glog.business.session.gen.FleetAssignmentActionSessionSkel.validateUnassignDriverFromShipment(FleetAssignmentActionSessionSkel.java:766)


-- Steps
The issue can be reproduced at will with the following steps.
DRIVER
DRIVER2

- Created Order Release: Order_1

To clean up the previously corrupted data:

1. Run the following SQL:

update shipment_status set status_value_gid ='TBRYANT.DRIVER ASSIGNMENT_ASSIGNED' where status_type_gid='TBRYANT.DRIVER ASSIGNMENT' and shipment_gid='Shipment01181'

2. Navigate to Shipment Management -> Shipment Management -> Buy Shipments
3. Go to Order Release tab
4. Search for shipments with order release: Order_1
5. Unassign the driver from each of the shipments: 01181, 01182 (Actions -> Fleet Management -> Fleet Unassign -> All)
6. Navigate to Order Management -> Order Release -> Order Release
7. Search for Order Release: Order_1
8. Actions -> Order Mangement -> Unassign Order Release -> Unassign Order - Buy

To replicate:

1. Navigate to Order Management -> Order Release -> Order Release
2. Search for order release: Order_1
3. Actions -> Operational Planning -> Create Buy Shipment -> Direct (click ok on popups)

Take note of the shipment ID (will be referred as shipment#1)

4. Click on shipment#1
5. Actions -> Fleet Management -> Assign -> Equipment Type
6. Check the "Freight" box and click OK (this should assign the equipment type successfully)
7. Actions -> Fleet Management -> Assign -> Driver
8. Using Manual, enter driver: DRIVER and click OK (this should assign the driver successfully)
9. Actions -> Fleet Management -> Assign -> Equipment
10. Check the radio button under "Process" and enter "GENERIC" in the Equipment ID field...click OK (this should assign the equipment successfully)


11. Actions -> Fleet Management -> Manage Relays -> Relay Shipment Breakdown (click ok on ignore criteria)
12. Enter the following:

Breakdown Location ID=EL PASO
Shipment Stop Number=2.LUBBOCK
Insert Breakdown location before existing stop=checked
Driver Breakdown=checked

13. Click ok (this should successfully relay the shipment into two shipments

Take note of the shipment ID for the second shipment (will be referred as shipment#2)

14. Click on shipment#2
15. Actions -> Fleet Management -> Assign -> Driver
16. Use "Manual" with driver: DRIVER2

This will change the status of the shipment to DRIVER ASSIGNMENT_ASSIGNED

17. from shipment#2 again, Actions -> Fleet Management -> Fleet Unassign -> Driver

This will set the status of shipment#2 to DRIVER ASSIGNMENT_UNASSIGNED. However it will ALSO set the status of shipment#1 to DRIVER ASSIGNMENT_NOT STARTED...even though the Driver is Still assigned. To observe this:

18. Navigate to Shipment Management -> Shipment Management -> Buy Shipments
19. Search for Shipment#1
20. Click View

Notice that the driver is displayed as: DRIVER

21. Click on STATUS button

Notice that the status is: DRIVER ASSIGNMENT_NOT STARTED

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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