My Oracle Support Banner

Unable To Relay Shipment At Stop. Error: Not valid relay location. (Doc ID 1321477.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Fleet Management - Version: 6.1.4 and later   [Release: 6.1 and later ]
Information in this document applies to any platform.

Symptoms

On OTM version 6.1.4 When attempting to force a relay the following error occurs.

ERROR
-----------------------
Not valid relay location LEE.LJS_ORACLE_READING or stop number 3 for shipment LEE.01409. It would create 2 consecutive stops at the same location LEE.LJS_ORACLE_READING

At 2011-04-20 12:41:36.717

Not valid relay location LEE.LJS_ORACLE_READING or stop number 3 for shipment LEE.01409. It would create 2 consecutive stops at the same location LEE.LJS_ORACLE_READING.

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:394)
at glog.business.shipment.splitmerge.SplitMergeHelper.validateStopNumberToSplit(SplitMergeHelper.java:122)
at glog.business.fleetassignment.relay.InTransitForceLogic.validate(InTransitForceLogic.java:50)
at glog.business.shipment.AbstractShipmentLogic.perform(AbstractShipmentLogic.java:68)
at glog.business.service.fleetassignment.RelayShipmentService.relayShipmentInTransit(RelayShipmentService.java:140)
at glog.business.action.fleetassignment.relay.InTransitForceAction.process(InTransitForceAction.java:82)
at glog.business.action.shipment.AbstractShipmentPlanningAction.perform(AbstractShipmentPlanningAction.java:138)
at glog.business.action.fleetassignment.AbstractFleetShipmentPlanningAction.perform(AbstractFleetShipmentPlanningAction.java:95)
at glog.business.session.FleetAssignmentActionSessionBean.relayShipmentInTransit(FleetAssignmentActionSessionBean.java:1984)
at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper.relayShipmentInTransit(FleetAssignmentActionSessionServerSideEJBWrapper.java:1734)
at glog.business.session.FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.relayShipmentInTransit(FleetAssignmentActionSessionServerSideEJBWrapper_c0gjd_EOImpl.java:1430)
at glog.business.session.gen.FleetAssignmentActionSessionSkel.relayShipmentInTransit(FleetAssignmentActionSessionSkel.java:1433)
at glog.business.session.gen.FleetAssignmentActionSessionSkel.exec(FleetAssignmentActionSessionSkel.java:276)
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 - Created Order Release ID 3-3441347357 and planned it onto Shipment ID 01409

2 - Allocated a driver to the shipment.

3 - The shipment now has 3 stops
NFR
Pickup
Delivery

4 - Clicked on Actions > Fleet Management > Manage Relays > Relay Shipment in Transit - Force > OK

5 - Set the following:
Relay Location ID: LJS_ORACLE_READING (this is stop 2 location ID)
Shipment Stop Number: 3.LJS_ORACLE_LONDON
Insert Relay location before existing stop: ticked.

6 - Clicked OK

7 - The following error message and stack trace were shown:

Not valid relay location LEE.LJS_ORACLE_READING or stop number 3 for shipment LEE.01409. It would create 2 consecutive stops at the same location LEE.LJS_ORACLE_READING

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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