Driver Assignment With Driver Special Service Is Failing in OTM With Error 'Failed advanced rule compatibility checking'
(Doc ID 2952965.1)
Last updated on JUNE 01, 2023
Applies to:
Oracle Fleet Management Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
In OTM Fleet Management, an issue has been observed that- while trying to assign a Driver to a Shipment, where both- the Driver and the Shipment have a Special Service assigned, the Driver Assignment process is failed with error Failed advanced rule compatibility checking.
This occurs under the following conditions:
1) When the Special Service assigned to the Driver has Effective Date and Expiration Date set, the Driver Assignment to the Shipment fails with the mentioned error. This happens even if the Shipment's Start and End dates fall within the Driver's Special Service Effective and Expiration dates.
2) However, when the Special Service assigned to the Driver does not have Effective Date and Expiration Date set, the Driver is successfully assigned to the Shipment.
1) When the Special Service assigned to the Driver has Effective Date and Expiration Date set, the Driver Assignment to the Shipment fails with the mentioned error. This happens even if the Shipment's Start and End dates fall within the Driver's Special Service Effective and Expiration dates.
2) However, when the Special Service assigned to the Driver does not have Effective Date and Expiration Date set, the Driver is successfully assigned to the Shipment.
User Log can show error similar to below-
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 |