Unassign Driver Action give the following error: Could not unassign driver from shipment xxx because there are too many driver assignments after this shipment.
(Doc ID 1197944.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.1.1 and laterInformation in this document applies to any platform.
Symptoms
On OTM version 6.1.1 version, when attempting to unassign a drive from a Shipment gain the following error:
ERROR
-----------------------
Error Exception Could not unassign driver from shipment xxx because there are too many driver assignments after this shipment.
at sun.reflect.GeneratedConstructorAccessor282.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Go to a Shipment where a Driver has been allocated.
2. Attempt to unassign the Driver from the Shipment
3. The error arises.
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 |