My Oracle Support Banner

OTM Agent Action "ASSIGN BEST DRIVER" Is NOT Checking the Availability of the Driver and Assigning that to Multiple Shipments Wrongly (Doc ID 2956203.1)

Last updated on JUNE 22, 2023

Applies to:

Oracle Fleet Management Cloud Service - Version 19.3 and later
Information in this document applies to any platform.


User is trying to assign Drivers to multiple Shipments through an Agent using the Agent Action ASSIGN BEST DRIVER based on required Agent Event.

If the Agent/Agent Action is executed on multiple Shipments at a time, system is assigning the same Driver to all/most of those Shipments.

This is happening even if the-
1. OD Pair is different for those Shipments
2. Combinations of Start Time & End Time are different for those Shipments i.e. Time Infeasible amongst themselves

However, if the same Agent/Agent Action is executed on multiple Shipments one at a time, then the functionality is working as expected; i.e. system is checking the availability of all Drivers and assigning them on Shipments accordingly as needed.

Here, the expectation is- System should check the availability of Drivers and then tag them on different Shipments. If one Driver is already blocked/occupied, then that driver should not be picked by system for another assignment if the above conditions are not satisfied for the assignment.

Example/Test Case for better understanding

Took, two Releases :
1. OR_001 (Loc-001 > Loc-003)
2. OR_002 (Loc-012 > Loc-013)

Planned both the ORs and it created two shipments- SH_001 & SH_002

  1. For both of these Shipments DRIVER-001 has been assigned
  2. Pickup Time at the Source Location for both the Shipments are exactly same





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

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