Got Warning Message Estimation Type Is Invalid In Meter Read Page (Doc ID 2266929.1)

Last updated on MAY 19, 2017

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.5.0.2.0 and later
Information in this document applies to any platform.

Symptoms

 The Meter Read High/Low Limits algorithm is customized in Java, implementing
com.splwg.ccb.domain.common.installation.algorithm.meterReadHigh.MeterReadHigh
LowLimitsAlgorithmSpot. After the customized algorithm is plugged in, the
'Estimate type is invalid (8/16505)¿ warning is shown when a meter read is
added or updated. (Please see the following screenshots for details.)

The Estimate Type is passed into the customized algorithm via the following
set method:
@Override
public void setEstimateType(EstimateTypeLookup estType) {
this.estimateType = estType;
}

After some debugging codes are added, the log shows the value passed in is
'HILO¿, which may be the result of truncating 'HILOW¿ to 4 bytes:
SYSUSER - 957786-157-1 2017-01-25 20:58:43,109 [[ACTIVE] ExecuteThread: '5'
for queue: 'weblogic.kernel.Default (self-tuning)'] INFO
(algorithm.meterReadHigh.CmRegisterReadHighLowLimitsAlgComp_Impl) estType set
by MR page service==>HILO

In the converted component
'com.splwg.ccb.domain.meterread.data.FieldCICMEST8.java', the valid values
are 'HILOW' and 'EST&HILOW'. However, the valid values of the
ESTIMATE_TYPE_FLG lookup (com.splwg.ccb.api.lookup.EstimateTypeLookup) are
'C1ES' and 'C1HL'. 

Note: The converted base algorithm ProgramCIPMFHLX works since it does not
implement MeterReadHighLowLimitsAlgorithmSpot.

 

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