Order Release Ship Unit Count, Weight And Volume Are Not Updating In OTM 6.3.3
(Doc ID 1915472.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.3 to 6.3.3 [Release 6.3]Information in this document applies to any platform.
Symptoms
When attempting to over release an Order Base
the following error occurs.
Exception Unable to release order base ship unit because the ship unit would be over released.
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:460)
at glog.util.exception.GLException.factory(GLException.java:436)
at glog.util.exception.GLException.factory(GLException.java:432)
at glog.util.exception.GLException.factory(GLException.java:420)
at glog.business.order.OrderReleaseBuilder.buildOrderReleases(OrderReleaseBuilder.java:365)
at glog.business.order.OrderReleaseBuilder.buildOrderReleases(OrderReleaseBuilder.java:276)
at glog.business.order.OrderReleaseBuilder.buildOrderReleases(OrderReleaseBuilder.java:109)
at glog.business.order.OrderReleaseBuilder.buildOrderReleases(OrderReleaseBuilder.java:80)
at glog.business.session.OrderBaseActionSessionBean.buildOrderReleases(OrderBaseActionSessionBean.java:75)
at glog.business.session.OrderBaseActionSessionServerSideEJBWrapper.buildOrderReleases(OrderBaseActionSessionServerSideEJBWrapper.java:101)
at glog.business.session.OrderBaseActionSessionHome_lsyxxr_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at glog.business.session.OrderBaseActionSessionHome_lsyxxr_EOImpl.buildOrderReleases(Unknown Source)
at glog.server.workflow.adhoc.OrderReleaseWorkflow$ProcessOrder.perform(OrderReleaseWorkflow.java:77)
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:40)
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at glog.server.workflow.WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl.execute(Unknown Source)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:356)
at glog.server.workflow.Trigger.trigger(Trigger.java:122)
at glog.util.event.MemoryEventQueueRunnable.processEvent(MemoryEventQueueRunnable.java:145)
at glog.util.event.MemoryEventQueueRunnable.run(MemoryEventQueueRunnable.java:100)
at glog.util.event.EventThread.run(EventThread.java:86)
at java.lang.Thread.run(Thread.java:680)
The issue can be reproduced at will with the following steps:
1. Create an Order Base via Xml,
2. The Order release gets automatically created
3. Modify the Order Base via Xml
4. The Order Release is not getting updated.
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 |