Error When Copying Refnum From Order Base To Order Base Ship Unit, Error: java.lang.NoSuchFieldException: orderBaseShipUnitGid (Doc ID 1288762.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

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

Symptoms


On OTM 6.1.3 when attempting to have an agent to copy reference numbers from a Ship Unit to the Order Base the following error arises:

ERROR
-----------------------
Error Exception java.lang.NoSuchFieldException: orderBaseShipUnitGid

java.lang.NoSuchFieldException: orderBaseShipUnitGid
at java.lang.Class.getField(Class.java:1520)
at glog.business.action.UtilActionExecutor.copyRefnumsToObject(UtilActionExecutor.java:1402)
at glog.server.agent.utility.CopyRefnumsToObject.execute(CopyRefnumsToObject.java:50)
at glog.server.agent.ActionWorkflow.execute(ActionWorkflow.java:49)
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.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable.java:141)
at glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:96)
at glog.util.event.EventThread.run(EventThread.java:82)
at java.lang.Thread.run(Thread.java:619)
[agentUtility - 1]


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an Order Base Ship Unit Agent with the action to copy the Reference Number Qualifiers (refnums) from the Ship Unit to the Order Base
2. Import an Order and expect the Order to be created and the agent to copy the refnums.
3. Not the refnums are not copied and the error is in the logs.

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