My Oracle Support Banner

Merge Shipments Is Failing Wth Error 'ORA-00001: unique constraint (GLOGOWNER.PK_S_SHIP_UNIT_PIECE) violated' (Doc ID 2638553.1)

Last updated on FEBRUARY 13, 2020

Applies to:

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

Symptoms

Merge Shipments is failing when two shipments are build with CONOPT logic configuration. 

ERROR
-----------------------


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1.Create two order releases , Update Transport Mode to LTL on constraints tab

2. Create CONOPT logic configuration and Parameter Set with following

  USE 3D BASED LOAD CONFIGURATION - TRUE
  CONSIDER SPACES ABOVE PLACED ITEMS SEPARATELY - TRUE 
  DRIVE WHILE RATING SHIPMENT IN CONOPT - TRUE
  

  New parameter set created using default values for below parameters
  ORDER RELEASE BUNDLING RULE SET
  MULTISTOP CONFIG ID

3. Plan the both order releases onto shipments using planning parameter created above
4. Tender the shipment and their status changed to SECURE RESOURCES_PICKUP NOTIFICATION
4. Merge shipments by selecting above two using manual option 'force merge onto shipment'
5. getting below error
  "Error while removing TenderCollaborations for shipment: xxxx
  You must withdraw the active tender on shipment xxxx before it can be deleted"
6. when withdrawn tenders and try to merge .. run in below exception
  "Cannot add the S_SHIP_UNIT_PIECE_T record. [S_SHIP_UNIT_GID, PIECE_NUMBER] must be unique.
  java.sql.BatchUpdateException: ORA-00001: unique constraint (GLOGOWNER.PK_S_SHIP_UNIT_PIECE) 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.