Not Able To Assign / Force Assign Equipment Type To Ground Schedule Shipment, Error "Not a valid action for STATIC TRIP shipments." (Doc ID 1395630.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 6.1.5 to 6.2.0 - Release: 6.1 to 6.2
Information in this document applies to any platform.

Symptoms


On OTM version 6.1.5 when working with a Shipment created from a Ground Schedule (even when released) and using the Fleet action to assign Equipment Type the following error is seen:

ERROR
-----------------------
Not a valid action for STATIC TRIP shipments.

at sun.reflect.GeneratedConstructorAccessor359.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: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.business.action.comm.DefaultShipmentValidator.validateScheduleType(DefaultShipmentValidator.java:164)
at glog.business.action.comm.DefaultShipmentValidator.validateShipment(DefaultShipmentValidator.java:114)
at glog.business.action.fleetassignment.AbstractFleetShipmentPlanningAction.preValidate(AbstractFleetShipmentPlanningAction.java:84)
at glog.business.action.shipment.AbstractShipmentPlanningAction.perform(AbstractShipmentPlanningAction.java:118)
at glog.business.action.fleetassignment.AbstractFleetShipmentPlanningAction.perform(AbstractFleetShipmentPlanningAction.java:95)
at glog.business.session.FleetAssignmentActionSessionBean.getEquipmentTypeAssignmentInputForShipment(FleetAssignmentActionSessionBean.java:809)
at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper.getEquipmentTypeAssignmentInputForShipment(FleetAssignmentActionSessionServerSideEJBWrapper.java:809)
at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.getEquipmentTypeAssignmentInputForShipment(FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.java:3662)
at glog.business.session.gen.FleetAssignmentActionSessionSkel.getEquipmentTypeAssignmentInputForShipment(FleetAssignmentActionSessionSkel.java:858)
at glog.business.session.gen.FleetAssignmentActionSessionSkel.exec(FleetAssignmentActionSessionSkel.java:175)
at glog.webserver.wrapper.SkelImpl.execDispatch(SkelImpl.java:15)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:83)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:61)
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 - Log onto an OTM 6.1 system.

2 - Navigate to Operational Planning > Schedule Management > Ground Schedule

3 - Click NEW and create a new Ground Schedule ID.

4 - From the Shipment click Actions > Generate Shipments, set the date to tomorrow and created for one day.

5 - A shipment is created.

6 - Create an Order Release and move it to the existing shipment.

7 - Click on Actions > Utilities > Release Schedule Instance.

8 - Navigate away from the shipment and search for it again to force a screen refresh.

9 - Click on Actions > Fleet Management > Assign > Equipment Type and the error is shown.


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