Rate Inquiry (RIQ) via XML no Longer Working in 5.5 CU3 RU2 (Doc ID 472939.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version 5.5.03.02 to 5.5.03.04 [Release 5.5]
Information in this document applies to any platform.
Checked for relevance on 25-May-2010


Symptoms

-- Problem Statement:
On 5.5.03.02:
RIQ in OTM whether invoked remotely or through OTM is failing when the source or location gid passed in the RIQ XML is not defined in OTM. It was working fine earlier in CU1.

Also, if the RIQ XML is uploaded with both the address and the location ID,  If the location GID was not found it would use the MileageAddress for evaluating and returning the results in CU1. It is now erroring out in CU3

ERROR

<StackTrace>java.lang.NullPointerException java.lang.NullPointerException at
glog.business.location.TLocation.getLocationGid(TLocation.java:293) at
glog.business.location.TLocation.load(TLocation.java:568) at
glog.business.location.TLocation.getInstance(TLocation.java:544) at
glog.business.rate.rateinquiry.RateInquirySession.reconstructAddress(RateInquirySession.java:1220)
at
glog.business.rate.rateinquiry.RateInquirySession.getRateInquiryData(RateInquirySession.java:268)
at glog.business.rate.rateinquiry.RateInquirySession.getRatesInternal(RateInquirySession.java:555)
at glog.business.rate.rateinquiry.RateInquirySession.getRates(RateInquirySession.java:168) at
glog.business.action.RateActionExecutor.getRates(RateActionExecutor.java:83) at
glog.business.session.RateActionSessionBean.getRates(RateActionSessionBean.java:71) at
glog.business.session.RateActionSessionServerSideEJBWrapper.getRates(RateActionSessionServerSideEJBW
rapper.java:60) at
glog.business.session.RateActionSessionHome_a6s4b5_EOImpl.getRates(RateActionSessionHome_a6s4b5_EOIm
pl.java:208) at glog.integration.application.query.RIQ2.buildRIQQueryResult(RIQ2.java:1025) at
glog.integration.application.query.QueryInterface.validateRemoteQuery(QueryInterface.java:103) at
glog.integration.application.query.QueryInterface.validateXML(QueryInterface.java:65) at
glog.integration.application.TransmissionProcessor.processQuery(TransmissionProcessor.java:234) at
glog.integration.application.CommandLineSessionBean.processQuery(CommandLineSessionBean.java:657)
at
glog.integration.application.CommandLineSessionServerSideEJBWrapper.processQuery(CommandLineSessionS
erverSideEJBWrapper.java:134) at
glog.integration.application.CommandLineSessionHome_12qkd9_EOImpl.processQuery(CommandLineSessionHom
e_12qkd9_EOImpl.java:964) at
glog.integration.application.CommandLineSessionHome_12qkd9_EOImpl_WLSkel.invoke(Unknown Source) at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477) at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108) at
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420) 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:415) at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)</StackTrace>

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:

1- Create a RIQ XML which has a source or destination location ID that is not defined in OTM.
2- Use Integration Manager to upload the XML
3- View the Remote Query Results.

-- Business Impact:
The issue has the following business impact:
Due to this issue, users are not able to use this functionality.

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