Planning an Order Gives the following Error: Failed at checking time feasibility of estimate! (Doc ID 1483281.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

On OTM version 6.2.

When attempting to plan an Order, if the number of days is greater than 30 the following error occurs.

ERROR
-----------------------
 Failed at checking time feasibility of estimate!
 


View Log

At 2012-08-01 05:04:28.219
 
Failed at checking time feasibility of estimate!

at sun.reflect.GeneratedConstructorAccessor892.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:435)
at glog.util.exception.GLException.factory(GLException.java:411)
at glog.util.exception.GLException.factory(GLException.java:407)
at glog.util.exception.GLException.factory(GLException.java:403)
at glog.business.shipment.MiniShipmentBuilder.buildShipmentManually(MiniShipmentBuilder.java:492)
at glog.business.action.OrderActionExecutor.buildShipmentManually(OrderActionExecutor.java:670)
at glog.business.session.OrderActionSessionBean.buildShipmentManually(OrderActionSessionBean.java:1504)
at glog.business.session.OrderActionSessionServerSideEJBWrapper.buildShipmentManually(OrderActionSessionServerSideEJBWrapper.java:1456)
at glog.business.session.OrderActionSessionHome_likuwd_EOImpl.buildShipmentManually(OrderActionSessionHome_likuwd_EOImpl.java:4881)
at glog.business.session.gen.OrderActionSessionSkel.buildShipmentManually(OrderActionSessionSkel.java:1196)
at glog.business.session.gen.OrderActionSessionSkel.exec(OrderActionSessionSkel.java:272)
at glog.webserver.wrapper.SkelImpl.execDispatch(SkelImpl.java:16)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:62)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:58)
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.2 system.

2 - Create an Order Release.

3 - From the Order Release click: Actions > Operational Planning > Create Buy Shipment > Manual.  OR Bulk Plan the Order Release.

4 - Enter the following details:

Transport Mode ID: VESSEL-CO or other sea related mode.
Service Provider: Enter as needed.
Estimated Service Time: 50 D
Estimated Cost: 100EUR
Perspective: BUY.

5 - Click OK.

6 - The following error is shown:


Failed at checking time feasibility of estimate!
 

 Failed at checking time feasibility of estimate!
 


View Log

At 2012-08-01 05:04:28.219
 
Failed at checking time feasibility of estimate!

at sun.reflect.GeneratedConstructorAccessor892.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:435)
at glog.util.exception.GLException.factory(GLException.java:411)
at glog.util.exception.GLException.factory(GLException.java:407)
at glog.util.exception.GLException.factory(GLException.java:403)
at glog.business.shipment.MiniShipmentBuilder.buildShipmentManually(MiniShipmentBuilder.java:492)
at glog.business.action.OrderActionExecutor.buildShipmentManually(OrderActionExecutor.java:670)
at glog.business.session.OrderActionSessionBean.buildShipmentManually(OrderActionSessionBean.java:1504)
at glog.business.session.OrderActionSessionServerSideEJBWrapper.buildShipmentManually(OrderActionSessionServerSideEJBWrapper.java:1456)
at glog.business.session.OrderActionSessionHome_likuwd_EOImpl.buildShipmentManually(OrderActionSessionHome_likuwd_EOImpl.java:4881)
at glog.business.session.gen.OrderActionSessionSkel.buildShipmentManually(OrderActionSessionSkel.java:1196)
at glog.business.session.gen.OrderActionSessionSkel.exec(OrderActionSessionSkel.java:272)
at glog.webserver.wrapper.SkelImpl.execDispatch(SkelImpl.java:16)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:62)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(WrapperSessionHome_a06097_EOImpl.java:58)
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)

 

7 - Repeated the above steps, this time used 31 days and the same error was seen.

8 - Repeated the above steps, this time used 29 days, the Shipment was successfully planned.



BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use OTM and go live is planned for next Monday, the 6th August 2012.

Cause

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