Search Results reset_flag

Overview

CS_CTR_COUNTER_VALUES_V is a reporting view within the Oracle E-Business Suite Service (CS) module. It presents counter value data captured against service counters, which are used to track cumulative usage, consumption, or measurement readings for customer products, contracts, and service agreements. The view consolidates counter readings, reset information, tolerance and rollover configuration, and supporting descriptive attributes into a single queryable structure, making it suitable for operational reporting, meter-based billing validation, and integration with downstream usage-rating processes.

In both Oracle EBS 12.1.1 and 12.2.2, the view is defined primarily for read-only reference. Notably, the ETRM metadata indicates the object is "Not implemented in this database" and documents no base object dependencies, meaning the view may be absent in some environments or is created through a separate patch or customization. When present, it functions as an abstraction layer over the underlying counter tables, shielding report authors and integrators from the underlying join logic.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects, the view text clearly establishes its dependencies. The principal driving table is CS_COUNTER_VALUES (aliased A), which stores individual reading records. It is joined to:

• CS_COUNTER_GRP_LOG (B) — the counter group log capturing source transaction information.
• CS_COUNTERS (C) — the counter setup/definition table holding name, description, unit of measure, tolerances, rollover thresholds, and validity dates.
• CS_COUNTER_VALUES again (A1) — a self-join retrieving the previous reading for comparison.
• CS_LOOKUPS — an inline subquery resolving the miscellaneous reading type code to its meaning.

The joins are keyed on COUNTER_GRP_LOG_ID and COUNTER_ID, correlating each reading to its parent group log and counter definition.

Key Columns

• COUNTER_READING — the raw reading value captured at VALUE_TIMESTAMP.
• NET_READING — a computed value applying reset logic, miscellaneous readings, and prior net differences to derive the effective consumption.
• RESET_FLAG / RESET_REASON — indicate whether the counter was reset and why.
• PREV_COUNTER_READING / PREV_NET_READING — the prior reading and its net equivalent, supporting delta calculations.
• NAME / DESCRIPTION / UOM_CODE — counter identity and measurement unit.
• TOLERANCE_PLUS / TOLERANCE_MINUS / ROLLOVER_LAST_READING / ROLLOVER_FIRST_READING — threshold and rollover configuration from CS_COUNTERS.
• MISC_READING_TYPE_DESC / MISC_READING — classification and value of adjustment readings, decoded via CS_LOOKUPS.
• VALID_FLAG / OVERRIDE_VALID_FLAG — validation state of the reading.
• ATTRIBUTE1–15, CONTEXT — DFF extensibility columns.

Common Use Cases and Queries

Typical scenarios include reconciling net consumption against billed quantities, auditing reset events, and exporting counter trends for analytics. A representative query retrieves valid readings for a specific counter:

SELECT counter_id, value_timestamp, counter_reading, net_reading, reset_flag FROM cs_ctr_counter_values_v WHERE counter_id = :p_counter_id AND valid_flag = 'Y' ORDER BY value_timestamp;

Another common pattern derives period consumption by comparing NET_READING to PREV_NET_READING:

SELECT counter_id, value_timestamp, net_reading - prev_net_reading period_usage FROM cs_ctr_counter_values_v WHERE counter_id = :p_counter_id AND counter_reading > 0;

Reports may also join the view to CS_COUNTERS or service agreement tables to attribute usage to a contract line, supporting usage-based billing and SLA monitoring.