Calculation / Audit Usage Details

We use the term "calculation / audit usage" to describe service quantities retrieved from the bill segment's usage request. An example of when calculation / audit usage may be required:

• You may have situations where meter reads are not maintained in Oracle Utilities Customer Care and Billing and bill determinants are requested from a meter data management system via a usage request. MDM might return both bill determinants and meter reads to print on the bill.

Usage service quantities are also stored in a bill segment's read details (the name of the table is CI_​BSEG_​READ ). The following points describe the differences between these types of rows on this table:

• Calculation / audit usage may or may not reference a service point.
• Calculation / audit usage does not reference the prime key of a real read.
• Calculation / audit usage has a usage flag with a value of Service Quantity.
• Calculation / audit usage does not require a UOM code. If a UOM is not supplied, an SQI must be supplied.

If you encounter other scenarios during your implementation that necessitate calculation / audit usage, you can develop bill segment type and calculation rule algorithms to add additional calculation / audit usage to a bill segment's read details.

In order to avoid confusing end-users, we do not show calculation / audit reads on Bill Segment - Read Details (this page only shows "real" reads). Rather, calculation / audit usage is shown in a separate section on Bill Segment - SQ Details.