When using the 'Rapid Order Base' with a Template, upon saving all changes made in the 'Rapid Order Base' screen are ignored. (Doc ID 1586380.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

On OTM version 6.3.1 when using the 'Rapid Order Base' with a Template, upon saving all changes made in the 'Rapid Order Base' screen are ignored.
If the 'Shippable' flag is ticked the following error is also seen:

ERROR
-----------------------
 Error in TObReleaseInstruction::getReleasingQuantity for ObLine: {ObLineGid=null} and ObReleaseInstruction:xxx.123_2-001-1, Zero Packaged Item Count on ObLine and quantityQualifierGid on ObReleaseInstruction is Count (obLineGid=xxx.111_2-001)
 
Stack Trace
Error in TObReleaseInstruction::getReleasingQuantity for ObLine: {ObLineGid=null} and ObReleaseInstruction:xxx.123_2-001-1, Zero Packaged Item Count on ObLine and quantityQualifierGid on ObReleaseInstruction is Count (obLineGid=xxx.111_2-001)

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:450)
at glog.util.exception.GLException.factory(GLException.java:426)
at glog.util.exception.GLException.factory(GLException.java:422)
at glog.util.exception.GLException.factory(GLException.java:418)
at glog.business.orderbase.TObReleaseInstruction.getReleasingQuantity(TObReleaseInstruction.java:459)
at glog.business.orderbase.TObReleaseInstruction.getReleasingQuantity(TObReleaseInstruction.java:489)
at glog.business.orderbase.TObLine.isOverReleasing(TObLine.java:602)
at glog.business.order.OrderReleaseBuilder.buildOrderReleases(OrderReleaseBuilder.java:469)
at glog.business.order.OrderReleaseBuilder.buildOrderReleases(OrderReleaseBuilder.java:111)
at glog.business.session.OrderBaseActionSessionBean.buildOrderReleases(OrderBaseActionSessionBean.java:75)
at glog.business.session.OrderBaseActionSessionServerSideEJBWrapper.buildOrderReleases(OrderBaseActionSessionServerSideEJBWrapper.java:97)
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.business.session.gen.OrderBaseActionSessionSkel.buildOrderReleases(OrderBaseActionSessionSkel.java:179)
at glog.business.session.gen.OrderBaseActionSessionSkel.exec(OrderBaseActionSessionSkel.java:52)
at glog.webserver.wrapper.SkelImpl.execDispatch(SkelImpl.java:16)
at glog.server.wrapper.WrapperSessionBean.execDispatch(WrapperSessionBean.java:83)
at glog.server.wrapper.WrapperSessionServerSideEJBWrapper.execDispatch(WrapperSessionServerSideEJBWrapper.java:48)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl.execDispatch(Unknown Source)
at glog.server.wrapper.WrapperSessionHome_a06097_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1 - Logged onto an internal OTM 6.3.1 system.

2 - Using the properties servlet set the following:

glog.order_release.show_template=true
glog.order_base.show_template=true

3 - Navigated to: Order Management > Purchase Order > Rapid Order Base.

4 - The screen displayed was the entry screen for details to created a new Order but there was not ability to select a Template.

5 - Added the two properties into the glog.properties file and restarted OTM.

6 - Navigated to: Order Management > Purchase Order > Rapid Order Base.

7 - The Template select screen was displayed.

8 - Entered the Template ID of: TEMPLATE
(This is an Order Base from *_ORACLE_READING to *_ORACLE_LONDON)

9 - Clicked Submit.

a - Entered Order Base ID: 111-2

b - Changed the Pick up Location to be: *_ORACLE_BIRMINGHAM.

c - Changed the Delivery Location to be: *_ORACLE_BRISTOL

d - Changed the Packaged Iterm ID to be: *_DEFAULT_PACKAGING_ITEM

e - Changed the Total Packaging Count to be: 2

10 - Saved all changed and clicked Submit.

11 - Edited the newly Created Order Base.

12 - In the Line Item tab the locations are *_ORACLE_READING and *_ORACLE_LONDON, not those as entered when populating the 'Rapid Order Base'.

13 - Total Package Count is null.

14 - Repeat the above with Shippable ticked and gain the error.

 
 

Changes

Cause

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