My Oracle Support Banner

No_contact_found_forwithdraw_work_assignment Error Received Attempting To Unassign A Driver On A Shipment Which Has Been Dispatched (Doc ID 1334519.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 unassign a Driver on a shipment the following error is received if the Shipment has been Dispatched (a status of DISPATCH_SENT).

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

cause.No_contact_found_forwithdraw_work_assignment 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.server.workflow.tender.WithdrawWorkAssignment$NotifyDriver.perform(WithdrawWorkAssignment.java:163) at glog.server.workflow.Workflow.executeBody(Workflow.java:79) at glog.server.workflow.Workflow.execute(Workflow.java:51) at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:64) at glog.server.workflow.WorkflowSessionServerSideEJBWrapper.execute(WorkflowSessionServerSideEJBWrapper.java:38) at glog.server.workflow.WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.execute(WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.java:353) at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:353) at glog.server.workflow.Trigger.trigger(Trigger.java:122) at glog.util.event.EventHandler.triggerEvent(EventHandler.java:247) at glog.server.workflow.TopicManager.execute(TopicManager.java:205) at glog.server.workflow.ServerPublisher.execute(ServerPublisher.java:161) at glog.server.workflow.ServerPublisher.execute(ServerPublisher.java:164) at glog.server.workflow.Topic.execute(Topic.java:178) at glog.business.action.ShipmentExecutionActionExecutor.withdrawWorkAssignment(ShipmentExecutionActionExecutor.java:4439) at glog.business.fleetassignment.DriverAssigner$WithdrawWorkAssignmentTask.run(DriverAssigner.java:1860) at glog.business.shipment.ShipmentUpdateSessionBean.commitShipmentGraph(ShipmentUpdateSessionBean.java:1656) 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.shipment.AbstractShipmentPlanningAction.persistShipmentGraph(AbstractShipmentPlanningAction.java:463) at glog.business.action.shipment.AbstractShipmentPlanningAction.persist(AbstractShipmentPlanningAction.java:437) at glog.business.action.shipment.AbstractShipmentPlanningAction.perform(AbstractShipmentPlanningAction.java:151) at glog.business.action.fleetassignment.AbstractFleetShipmentPlanningAction.perform(AbstractFleetShipmentPlanningAction.java:95) at glog.business.session.FleetAssignmentActionSessionBean.unassignDriverFromShipment(FleetAssignmentActionSessionBean.java:703) at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper.unassignDriverFromShipment(FleetAssignmentActionSessionServerSideEJBWrapper.java:698) at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.unassignDriverFromShipment(FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.java:854) at glog.business.session.gen.FleetAssignmentActionSessionSkel.unassignDriverFromShipment(FleetAssignmentActionSessionSkel.java:789) at glog.business.session.gen.FleetAssignmentActionSessionSkel.exec(FleetAssignmentActionSessionSkel.java:162) at glog.webserver.wrapper.SkelImpl.execDispatch(SkelImpl.java:15) at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:61) 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 into OTM.
2. Search for a Shipment where the Dispatch has been sent.
3. Go to Actions --> Fleet Management --> Unassign --> Driver.
4. Note the Message Received:
Shipment xxxxx has been committed or dispatched. If you choose to unassign
the driver from this shipment, it will be uncommitted. Any previous dispatch
of the shipment will be withdrawn. Shipment xxxxx is not the last assignment
of driver SH.DRIVER1. Do you want to continue?

5. Click Ok.
6. Note the Error:

cause.No_contact_found_forwithdraw_work_assignment at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at

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.