Sales Order Not Processing To GTM from EBS With Error: java.sql.BatchUpdateException: ORA-02291: integrity constraint (GLOGOWNER.FK_GTLQ_GTM_QUANTITY_TYPE_GID) violated - parent key not found
(Doc ID 1354087.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Global Trade Management - Version 6.2.2 to 6.2.4 [Release 6.2]Information in this document applies to any platform.
Symptoms
On OTM version 6.2.2 when attempting to interface orders from EBS to GTM the following error occurs.
ERROR
-----------------------
java.sql.BatchUpdateException: ORA-02291: integrity constraint (GLOGOWNER.FK_GTLQ_GTM_QUANTITY_TYPE_GID) violated - parent key not found
at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:629)
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9447)
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:211)
at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:210)
at glog.util.jdbc.SqlUpdate.processBatch(SqlUpdate.java:142)
at glog.util.jdbc.SqlUpdate.resetArguments(SqlUpdate.java:238)
at glog.util.jdbc.SqlUpdate.resetArguments(SqlUpdate.java:161)
at glog.util.jdbc.SqlUpdate.execute(SqlUpdate.java:90)
at glog.util.beandata.BeanDataInserter.insertDBBatch(BeanDataInserter.java:358)
at glog.util.beandata.BeanDataInserter.insertDB(BeanDataInserter.java:302)
at glog.util.beandata.BeanDataInserter.insert(BeanDataInserter.java:197)
at glog.util.beandata.BeanDataInserter.insert(BeanDataInserter.java:232)
at glog.util.beandata.BeanDataInserter.insert(BeanDataInserter.java:171)
at glog.util.persistence.BeanDataPersistenceExecutor.insertPerformed(BeanDataPersistenceExecutor.java:97)
at glog.util.persistence.BeanDataPersistenceExecutor.insertUpdatePerformed(BeanDataPersistenceExecutor.java:116)
at glog.util.persistence.PersistenceExecutor.persistencePerformed(PersistenceExecutor.java:93)
at glog.util.persistence.InsertUpdate.doPersist(InsertUpdate.java:100)
at glog.util.persistence.InsertUpdate.persist(InsertUpdate.java:54)
at glog.util.persistence.PersistenceManager.execute(PersistenceManager.java:122)
at glog.server.compareengine.TopicPublisher.persist(TopicPublisher.java:161)
at glog.server.compareengine.TopicPublisher.publish(TopicPublisher.java:64)
at glog.server.compareengine.CompareEngine.compare(CompareEngine.java:116)
at glog.server.compareengine.CompareEngine.compare(CompareEngine.java:77)
at glog.util.genericcontainer.GenericContainerUtilSessionBean.compare(GenericContainerUtilSessionBean.java:139)
at glog.util.genericcontainer.GenericContainerUtilSessionBean.compareAndStore(GenericContainerUtilSessionBean.java:76)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSideEJBWrapper.compareAndStore(GenericContainerUtilSessionServerSideEJBWrapper.java:169)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSid
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Move Orders from EBS to GTM.
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 |