DRIVER.DRIVER_ASSIGNMENT_SEQ_NUM Field Not Updated After Driver Assignment Purge
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.0 to 6.3.2 [Release 6.2 to 6.3]
Information in this document applies to any platform.
After we ran a Data Purge, we found cases where a DRIVER_ASSIGNMENT record with the Assignment Seq Number matching that in the Driver record did not exist. The Driver Assignment record was purged when the matching Shipment was purged but the DRIVER.DRIVER_ASSIGNMENT_SEQ_NUM was not updated.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms