No MD node named sum(postVEE) Error Encountered when IMD is VEEd with VEE Rule Eligibility Criteria (Doc ID 2238240.1)

Last updated on MARCH 03, 2017

Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.3 and later
Information in this document applies to any platform.

Symptoms


Eligibility Criteria “XPath to the element to be evaluated” failed using sum() function.

PREREQUISITE:
1. Create MC Type, MC type should have VEE Group with Hi-Low VEE rule added.
2. This VEE Rule should have VEE Eligibility criteria defined.
3. The eligibility criteria should have below settings in Criteria Section:
a. Criteria Field - Create new algorithm and select that here.
b. New algorithm - Newly created algorithm - NewAlgoName, Algorithm type used - D1-IMD-CRTFD , Xpath value - sum(postVEE/msrs/mL/q)

STEPS
1. Navigate to 360 degree view of Measuring Component ID 096998680265.
2. Create IMD through "Create/Override" function. Initial Measurement Data ID -- 09646406797016
3. Initial Measurement page will be launched.
4. Click on perform VEE.
5. Obtain logs and verify

Error from Logs:

SYSUSER - 348883-4975-1 2017-02-03 12:21:39,267 [[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (web.dataservlet.XMLBasedServlet) Unexpected exception.
com.splwg.shared.common.LoggedException:
The following stacked messages were reported as the LoggedException was rethrown:
com.splwg.base.support.service.ServiceReplayExecuter.executeInAppropriateSession(ServiceReplayExecuter.java:114): Exception occurred calling serviceName: D1-ManualIMDInterval-BO-ServiceBean
com.splwg.ejb.service.impl.ServiceBeanSessionHelper$1$1.execute(ServiceBeanSessionHelper.java:34): Caught exception from SessionExecutable.execute()
com.splwg.base.support.schema.rules.AbstractModifyingBusinessObjectRuleProcessor.postProcess(AbstractModifyingBusinessObjectRuleProcessor.java:91): Encountered exception, session marked for rollback

The root LoggedException was: No MD node named sum(postVEE
at com.splwg.shared.common.LoggedException.raised(LoggedException.java:67)
at com.splwg.base.api.businessObject.COTSInstanceNode.validateIsContainerSchemaMD(COTSInstanceNode.java:447)
at com.splwg.base.api.businessObject.COTSInstanceNode.privateGetContainerFromPath(COTSInstanceNode.java:396)
at com.splwg.base.api.businessObject.COTSInstanceNode.getFieldAndMDForPath(COTSInstanceNode.java:493)
at com.splwg.d1.domain.admin.veeEligibilityCriteria.veeCriteriaField.VeeCriteriaFieldIMDElementEvaluationAlgComp_Impl.invoke(VeeCriteriaFieldIMDElementEvaluationAlgComp_Impl.java:46)
at com.splwg.d1.domain.admin.veeEligibilityCriteria.veeCriteriaField.VeeCriteriaFieldIMDElementEvaluationAlgComp_Impl__.CGLIB$invoke$2(<generated>)
at com.splwg.d1.domain.admin.veeEligibilityCriteria.veeCriteriaField.VeeCriteriaFieldIMDElementEvaluationAlgComp_Impl__$$FastClassByCGLIB$$d1c15e86.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:215)

Changes

 

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