Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 6.2.0 to 6.2.2 - Release: 6.2 to 6.2
Information in this document applies to any platform.
A shipment is created that also has a Secondary Charge Shipment. When an action is executed that affects this shipment such as "Change Service Provider" or an "Unassign" from the Release the following error is encountered:
Cannot add the SHIPMENT record. SHIPMENT_GID must be unique.
java.sql.BatchUpdateException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIPMENT) violated
The shipment ID attempted to be used is the shipment ID of the Secondary Charge shipment.
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