Unable to add NFR stop to Shipment when DRIVER is populated but 0 records in DRIVER ASSIGNMENT Table

Summary:

As per the configurations, Users are not using the native driver assignment functionality. So there are no records in the Driver Assignment table.

Users are updating the DRIVER_GID column in the shipment table to assign (association) a driver.

Post the association of the DRIVER, when user is trying to adding the NFR stop ( ADD FORCE NFR or ADD NFR action)on the shipment, OTM is looking into DRIVER_ASSIGNMENT table for a record to perform it's internal calculations like re-rating and re-driving.

As there is no record in the DRIVER_ASSIGNMENT table, the addition of the NFR stop is unsuccessful.