Search Results cs_counter_values_uk

Overview

CS_COUNTER_VALUES is a Service (CS) module table that stores the historical readings of a counter in Oracle E-Business Suite. In the Service and field service context, counters represent meters or usage measurement points attached to serviceable assets, and each row in CS_COUNTER_VALUES captures a discrete reading taken against one of those counters at a point in time. The table therefore serves as the transactional history layer beneath the counter definition itself.

Under the heuristic Data Vault classification derived from its foreign key structure, CS_COUNTER_VALUES leans toward a satellite. It is an insert-oriented, event-style table: each counter reading is recorded as a separate, immutable row linked back to its parent counter. The unique constraint on SEQ_NO and COUNTER_ID reinforces the satellite pattern by enforcing a stable business sequence per parent, allowing multiple ordered readings to coexist against the same counter.

Key Information Stored

The documented metadata identifies the following structural columns:

• COUNTER_VALUE_ID — surrogate primary key (CS_COUNTER_VALUES_PK) uniquely identifying each historical reading.
• SEQ_NO — sequence number within a counter; part of the unique key CS_COUNTER_VALUES_UK alongside COUNTER_ID.
• COUNTER_ID — foreign key to CS_COUNTERS, identifying which counter the reading belongs to. Also part of the unique key.
• COUNTER_GRP_LOG_ID — foreign key to CS_COUNTER_GRP_LOG, linking the reading to the counter group logging context.

Here COUNTER_VALUE_ID is the surrogate key, while the combination (SEQ_NO, COUNTER_ID) is the business-key candidate enforced by the unique index. Additional attribute columns holding the actual reading value, unit of measure, and timestamp are implied by the table's purpose as a historical reading store, though only the columns documented above are enumerated here.

Common Use Cases and Queries

Typical usage includes counter history reporting for warranty and usage-based billing, meter-to-contract reconciliation, and asset utilization analysis. A representative pattern retrieves the ordered reading history for a specific counter:

• SELECT counter_value_id, seq_no, counter_id FROM cs_counter_values WHERE counter_id = :p_counter_id ORDER BY seq_no;
• Joining to the counter definition: SELECT cv.*, c.* FROM cs_counter_values cv, cs_counters c WHERE cv.counter_id = c.counter_id;
• Filtering by group log context: SELECT * FROM cs_counter_values WHERE counter_grp_log_id = :p_grp_log_id;

These queries support dashboards tracking counter progression, audits of reading sequences via SEQ_NO, and reconciliation against property values stored downstream in CS_COUNTER_PROP_VALUES.

Related Objects

• CS_COUNTERS — parent table; joined via CS_COUNTER_VALUES.COUNTER_ID = CS_COUNTERS.COUNTER_ID.
• CS_COUNTER_GRP_LOG — group logging context; joined via CS_COUNTER_VALUES.COUNTER_GRP_LOG_ID = CS_COUNTER_GRP_LOG.COUNTER_GRP_LOG_ID.
• CS_COUNTER_PROP_VALUES — dependent child table referencing this table through CS_COUNTER_PROP_VALUES.COUNTER_VALUE_ID = CS_COUNTER_VALUES.COUNTER_VALUE_ID, storing captured property attributes associated with a reading.

The metadata notes "Not implemented in this database," indicating that in the examined environment the table was not deployed. The relationships above remain authoritative for the object's logical schema, and any Service analytics or billing integration touching counter history should be built around these documented keys.