My Oracle Support Banner

"SHIPMENT_GID, SHIPMENT_SPECIAL_SERVICE_SEQ must be unique" Error When Attempting to Update a Special Service on a Shipment Using an Agent (Doc ID 1087776.1)

Last updated on MARCH 05, 2019

Applies to:

Oracle Transportation Management - Version 6.1.0 to 6.1.2 [Release 6.1]
Information in this document applies to any platform.

Symptoms

When attempting to use an agent which updates the Special Service after entering a tracking event, the following error is seen in the logs and the special service shipment does not get updated.

ERROR
-----------------------
Cannot add the SHIPMENT_SPECIAL_SERVICE record. SHIPMENT_GID, SHIPMENT_SPECIAL_SERVICE_SEQ must be unique.
java.sql.BatchUpdateException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIPMENT_SPECIAL_SERVICE) violated

java.sql.BatchUpdateException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIPMENT_SPECIAL_SERVICE) violated



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an Agent which listens for a Tracking Event to be created
2. Enter a new tracking event updating the Special Service Tab with the Special Service and change the status to completed
3. View the logs and note the following error:

Cannot add the SHIPMENT_SPECIAL_SERVICE record. SHIPMENT_GID, SHIPMENT_SPECIAL_SERVICE_SEQ must be unique.
java.sql.BatchUpdateException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIPMENT_SPECIAL_SERVICE) violated

java.sql.BatchUpdateException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIPMENT_SPECIAL_SERVICE) violated



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
Cause
Solution
References


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