Split Shipment Action results in the Following Error: Can not consolidate shipment without consolidate equipments, because can not assign best cost equipment for new shipment. (Doc ID 1511171.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

On OTM version 6.2.3

When attempting to split some Ship Units from one shipment to another where the modes are different on each Shipment as are the Equipment, the following error arises.
Note: Looking on the Order Release, Rates and Itineraries there is no reason why the split should not be allowed.

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

Can not consolidate shipment without consolidate equipments, because can not assign best cost equipment for new shipment. (shipmentPK=XXX.002164782)

at sun.reflect.GeneratedConstructorAccessor691.newInstance(Unknown Source)
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:435)
at glog.util.exception.GLException.factory(GLException.java:411)
at glog.util.exception.GLException.factory(GLException.java:407)
at glog.util.exception.GLException.factory(GLException.java:403)
at glog.business.action.ordermovement.MoveOrderMovementsToShipmentActionHelper.moveOrderMovementBundleToShipment(MoveOrderMovementsToShipmentActionHelper.java:218)
at glog.business.action.shipment.ShipmentSpliter.splitSShipUnitsParallel(ShipmentSpliter.java:688)
at glog.business.action.shipment.ShipmentSpliter.splitSShipUnitsParallel(ShipmentSpliter.java:163)
at glog.business.action.shipment.SplitShipmentActions.splitShipmentBySShipUnits(SplitShipmentActions.java:720)
at glog.business.session.ShipmentPlanningActionSessionBean.splitShipmentBySShipUnits(ShipmentPlanningActionSessionBean.java:1338)
at glog.business.session.ShipmentPlanningActionSessionServerSideEJBWrapper.splitShipmentBySShipUnits(ShipmentPlanningActionSessionServerSideEJBWrapper.java:1176)
at glog.business.session.ShipmentPlanningActionSessionServerSideEJBWrapper_7zfvrj_EOImpl.splitShipmentBySShipUnits(ShipmentPlanningActionSessionServerSideEJBWrapper_7zfvrj_EOImpl.java:4099)
at glog.business.session.gen.ShipmentPlanningActionSessionSkel.splitShipmentBySShipUnits(ShipmentPlanningActionSessionSkel.java:1057)
at glog.business.session.gen.ShipmentPlanningActionSessionSkel.exec(ShipmentPlanningActionSessionSkel.java:209)
at glog.webserver.wrapper.SkelImpl.execDispatch(SkelImpl.java:15)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:62)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:58)
at glog.server.wrapper.WrapperSessionHome_a06097_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)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Have two Shipments bot from A to B, where one it TL and the other is Rail.
2. Split some Ship Units from one Shipment to the other.
3. The error is seen and the split fails.
Note: Looking on the Order Release, Rates and Itineraries there is no reason why the split should not be allowed.

Cause

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