Search Results prev_net_reading

Overview

CS_CTR_COUNTER_READINGS_V is a Service (CS) module view that consolidates counter reading information captured against customer service counters. In Oracle E-Business Suite 12.1.1 and 12.2.2, counters are used to track cumulative usage measures such as meter readings, copy volumes, mileage, or runtime hours on serviceable assets. The view joins the counter definition (from CS_COUNTERS) with the transaction-level reading records (from CS_COUNTER_GRP_LOGS and associated reading tables) to present a denormalized, reporting-ready result set.

Its principal value lies in the derived columns it computes rather than the raw data it exposes. The view returns a calculated NET_READING that adjusts the raw counter reading for miscellaneous usage and prior period differences, and it handles the special case of a counter reset by adding back the pre-reset last reading and subtracting the post-reset first reading. It also exposes OVERRIDE_VALID_FLAG, calculated as NVL(A.OVERRIDE_VALID_FLAG, A.VALID_FLAG), which is the column most relevant to the search term override_valid_flag. This flag allows a user-entered override of the system-determined validity of a reading to take precedence over the base validity flag, so that readings flagged as suspect or out-of-tolerance by automated validation may still be marked valid by explicit operator action.

Underlying Base Objects

The view is defined over the CS_COUNTERS table (aliased C), the counter group log table CS_COUNTER_GRP_LOGS (aliased A), a self-join back to the same log source (aliased A1) to retrieve the immediately preceding reading, and a lookup table aliased CSL that resolves MISC_READING_TYPE to its display meaning. The self-join on A1 provides PREV_COUNTER_READING, PREV_NET_READING, and PREV_READING_DATE, enabling period-over-period consumption analysis within a single row.

The ETRM metadata records the view as "Not implemented in this database" and lists no documented base objects for 12.2.2; the object should therefore be treated as a functional specification artifact rather than a guaranteed deliverable in every installation. Where present, it is a read-only query view with no DML surface, and it depends on the row-level integrity of the underlying counter tables.

Key Columns

• COUNTER_ID, COUNTER_GROUP_ID, NAME, DESCRIPTION — counter definition attributes from CS_COUNTERS.
• COUNTER_VALUE_ID, COUNTER_GRP_LOG_ID, VALUE_TIMESTAMP — identifiers and effective date of the reading.
• COUNTER_READING / NET_READING — raw and adjusted reading values; NET_READING accounts for resets and miscellaneous usage.
• PREV_COUNTER_READING, PREV_NET_READING, PREV_READING_DATE — prior-period comparison values.
• RESET_FLAG, RESET_REASON, PRE_RESET_LAST_RDG, POST_RESET_FIRST_RDG — reset handling controls.
• MISC_READING, MISC_READING_TYPE, MISC_READING_TYPE_DESC, PREV_NET_CURR_DIFF — adjustments deducted from the net calculation.
• VALID_FLAG and OVERRIDE_VALID_FLAG — system validity and operator-overridden validity respectively.
• UOM_CODE, STEP_VALUE, TOLERANCE_PLUS, TOLERANCE_MINUS, ROLLOVER_LAST_READING, ROLLOVER_FIRST_READING — counter mechanics and validation thresholds.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — descriptive flexfield segments on the reading record.

Common Use Cases and Queries

Typical scenarios include billing and contract usage verification, tolerance-exception review, and audit reporting of counter resets or manual overrides of reading validity.

To list readings where the operator has overridden the automatic validity determination:

• SELECT counter_id, counter_value_id, value_timestamp, counter_reading, net_reading, valid_flag, override_valid_flag FROM cs_ctr_counter_readings_v WHERE override_valid_flag = 'Y' AND NVL(valid_flag,'N') = 'N';

To examine net consumption between consecutive readings for a given counter:

• SELECT value_timestamp, net_reading, prev_net_reading, net_reading - prev_net_reading period_usage FROM cs_ctr_counter_readings_v WHERE counter_id = :counter_id ORDER BY value_timestamp;

To review readings that required a reset and their adjustment components:

• SELECT reset_reason, pre_reset_last_rdg, post_reset_first_rdg, misc_reading, prev_net_curr_diff, net_reading FROM cs_ctr_counter_readings_v WHERE reset_flag = 'Y' ORDER BY value_timestamp DESC;