When Manually Adding the 11th Ship Unit to an Order Release, a Duplicate Already Exists Error is Displayed. (Doc ID 604875.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5.03 to 5.5.04
This problem can occur on any platform.

Symptoms

-- Problem Statement:

When trying to save an Order Release that has been manually created using Ship Units and Ship Unit Line the following error is displayed:

The SHIP_UNIT_LINE TEST.PO-1350-001-002 10 cannot be created because a duplicate already exists'.

Cannot add the SHIP_UNIT_LINE record. [SHIP_UNIT_GID, SHIP_UNIT_LINE_NO] must be unique.


Stack Trace

glog.util.remote.CreateDuplicateRecord
Cannot add the SHIP_UNIT_LINE record. [SHIP_UNIT_GID, SHIP_UNIT_LINE_NO] must be unique.
java.sql.SQLException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIP_UNIT_LINE) violated


java.sql.SQLException: ORA-00001: unique constraint (GLOGOWNER.PK_SHIP_UNIT_LINE) violated

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:589)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1957)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1114)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2181)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:2063)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2905)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:644)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:147)
at glog.util.jdbc.SqlUpdate.executeUpdate(SqlUpdate.java:133)
at glog.util.jdbc.SqlUpdate.resetArguments(SqlUpdate.java:111)
at glog.util.jdbc.SqlUpdate.execute(SqlUpdate.java:60)
at glog.util.remote.BeanManagedEntityBean.executeUpdate(BeanManagedEntityBean.java:793)
at glog.util.remote.BeanManagedEntityBean$1.execute(BeanManagedEntityBean.java:195)
at glog.util.remote.BeanManagedEntityBean.dbModify(BeanManagedEntityBean.java:1066)
at glog.util.remote.BeanManagedEntityBean.doCreate(BeanManagedEntityBean.java:191)
at glog.util.remote.BaseEntityBean$1.doIt(BaseEntityBean.java:460)
at glog.util.remote.BaseEntityBean.ejb(BaseEntityBean.java:803)
at glog.util.remote.BaseEntityBean.ejbCreator(BaseEntityBean.java:458)
at glog.ejb.order.db.ShipUnitLineBeanDB.ejbCreate(ShipUnitLineBeanDB.java:68)
at glog.ejb.order.ejb_ShipUnitLine_kbg892_Impl.ejbCreate(ejb_ShipUnitLine_kbg892_Impl.java:295)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.java:750)
at weblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityManager.java:721)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:249)
at glog.ejb.order.ejb_ShipUnitLine_kbg892_HomeImpl.create(ejb_ShipUnitLine_kbg892_HomeImpl.java:141)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms