My Oracle Support Banner

"Shipment is already tendered, loaded, and/or enroute." Error Received When Attempting To Delete a Shipment Template (Doc ID 1336453.1)

Last updated on JULY 20, 2024

Applies to:

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

Symptoms


When attempting to delete a shipment template, the following error is received:


ERROR
-----------------------
Shipment is already tendered, loaded, and/or enroute.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log into OTM.
2. Search for a Shipment Template.
3. Select and click Delete.
4. Note the Error:

Shipment is already tendered, loaded, and/or enroute.

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at glog.util.exception.GLException.factory(GLException.java:434)
at glog.util.exception.GLException.factory(GLException.java:410)
at glog.util.exception.GLException.factory(GLException.java:406)
at glog.util.exception.GLException.factory(GLException.java:402)
at glog.ejb.shipment.ShipmentBean.preRemove(ShipmentBean.java:327)
at glog.util.remote.BaseEntityBean$4.pre(BaseEntityBean.java:540)
at glog.util.remote.BaseEntityBean.ejb(BaseEntityBean.java:797)
at glog.util.remote.BaseEntityBean.ejbRemove(BaseEntityBean.java:538)
at glog.util.remote.BeanManagedEntityBean.ejbRemove(BeanManagedEntityBean.java:577)
at glog.ejb.shipment.ejb_Shipment_2ujudi_Impl.ejbRemove(ejb_Shipment_2ujudi_Impl.java:146)
at weblogic.ejb.container.manager.ExclusiveEntityManager.remove(ExclusiveEntityManager.java:988)
at weblogic.ejb.container.internal.EntityEJBObject.remove(EntityEJBObject.java:134)
at glog.ejb.shipment.ejb_Shipment_2ujudi_EOImpl.remove(ejb_Shipment_2ujudi_EOImpl.java:27991)
at glog.business.shipment.ShipmentUpdateSessionBean.commitShipmentNode(ShipmentUpdateSessionBean.java:850)
at glog.business.shipment.ShipmentUpdateSessionBean.commitShipmentGraph(ShipmentUpdateSessionBean.java:1448)
at glog.business.shipment.ShipmentUpdateSessionServerSideEJBWrapper.commitShipmentGraph(ShipmentUpdateSessionServerSideEJBWrapper.java:320)
at glog.business.shipment.ShipmentUpdateSessionBean.commitShipmentGraph(ShipmentUpdateSessionBean.java:1733)
at glog.business.shipment.ShipmentUpdateSessionServerSideEJBWrapper.commitShipmentGraph(ShipmentUpdateSessionServerSideEJBWrapper.java:283)
at glog.business.shipment.ShipmentUpdateSessionHome_qj7mtr_EOImpl.commitShipmentGraph(ShipmentUpdateSessionHome_qj7mtr_EOImpl.java:1165)
at glog.business.action.ShipmentPlanningActionExecutor.deleteShipmentGraph(ShipmentPlanningActionExecutor.java:2530)
at glog.business.action.ShipmentPlanningActionExecutor.deleteShipments(ShipmentPlanningActionExecutor.java:1802)
at glog.business.session.ShipmentPlanningActionSessionBean.deleteShipments(ShipmentPlanningActionSessionBean.java:960)
at glog.business.session.ShipmentPlanningActionSessionServerSideEJBWrapper.deleteShipments(ShipmentPlanningActionSessionServerSideEJBWrapper.java:776)
at glog.business.session.ShipmentPlanningActionSessionServerSideEJBWrapper_7zfvrj_EOImpl.deleteShipments(ShipmentPlanningActionSessionServerSideEJBWrapper_7zfvrj_EOImpl.java:3094)
at glog.util.persistence.CascadeDelete.persist(CascadeDelete.java:206)
at glog.util.persistence.CascadeDelete.persist(CascadeDelete.java:43)
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:110)
at glog.server.compareengine.CompareEngine.compare(CompareEngine.java:71)
at glog.util.genericcontainer.GenericContainerUtilSessionBean.compare(GenericContainerUtilSessionBean.java:139)
at glog.util.genericcontainer.GenericContainerUtilSessionBean.compareAndStore(GenericContainerUtilSessionBean.java:126)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSideEJBWrapper.compareAndStore(GenericContainerUtilSessionServerSideEJBWrapper.java:268)
at glog.util.genericcontainer.GenericContainerUtilSessionServerSideEJBWrapper_6hrtm7_EOImpl.compareAndStore(GenericContainerUtilSessionServerSideEJBWrapper_6hrtm7_EOImpl.java:718)
at glog.webserver.update.AbstractUpdate.callGenericContainer(AbstractUpdate.java:359)
at glog.webserver.update.GenericContainerXMLUpdate.delete(GenericContainerXMLUpdate.java:356)
at glog.webserver.update.GenericContainerXMLUpdate.process(GenericContainerXMLUpdate.java:118)
at glog.server.xmlupdate.XMLUpdateSessionBean.updateAndTrack(XMLUpdateSessionBean.java:244)
at glog.server.xmlupdate.XMLUpdateSessionServerSideEJBWrapper.updateAndTrack(XMLUpdateSessionServerSideEJBWrapper.java:344)
at glog.server.xmlupdate.XMLUpdateSessionHome_x72wrp_EOImpl.updateAndTrack(XMLUpdateSessionHome_x72wrp_EOImpl.java:285)
at glog.server.xmlupdate.XMLUpdateSessionHome_x72wrp_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

BUSINESS IMPACT
-----------------------
The issue has the following business impact:

Due to this issue, there is no way to delete a shipment marked as a template.

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.