My Oracle Support Banner

Usage Requests: Bill Segment Reads (missing) Issue (Doc ID 2727888.1)

Last updated on NOVEMBER 22, 2020

Applies to:

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

Symptoms

**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:

MDM - Oracle Utilities Meter Data Management

SA - Service Agreement

SQ - Service Quantity

On : 2.4.0.3.0 version, BI - Billing

ACTUAL BEHAVIOR
---------------
When clients are billed with usage requests, the bill segment reads contains only the reads of MDM/external system but other reads/SQ’s populated as part of subsequent rate components are missing
Issue reported in client’s production environment, critical process and financial impact as this involves computation of rates in bills of customers

EXPECTED BEHAVIOR
-----------------------
The bill segment reads should be handled properly.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create new plugin script + algorithm has been developed to insert some dummy SQ’s in bseg read as calculation/audit reads.
2. Create new simple rates are configured for 2 different type of SA’s.
A. Normal SA’s rate schedule
Rate component at sequence 5 is added. This is a calculation RC which populates bseg reads using the above algorithm (SQ == Algo parameter value == CAB).
A Rate component at the end of all sequences of rates schedule is added This is a calculation RC which populates bseg reads using the above algorithm (SQ == Algo parameter value == A-TMTD).
B. Usage SA’s rate schedule
RC @ 24 - call an external system for the consumption/SQ’s/etc.
RC @ 150 - Summary RC
RC @ 160 - RC to populate bseg reads using above algorithm.
3. TESTING
Generate a bill using the above 2 rates.
Bill Successfully generated.
Let’s verify if the bill segment reads are properly populated or not by above plugged algorithm in rate schedule.
A. Normal SA’s Bill Segment.
-Reads Properly populated.
B. Usage SA’s Bill Segment.
-Reads added by our algo are not populated. The above SQ’s are of usages.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


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