Results for “cs_counter_prop_values”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_COUNTER_PROP_VALUES is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the historical values captured against counter properties for installed base counters. Counters are the metering mechanism used to track usage, consumption, or operational readings recorded against an asset, item instance, or service contract line; counter properties describe the individual attributes of those counters (for example, a reading value, a unit of measure reference, or a specific measurement dimension associated with the counter definition). Because Oracle EBS preserves the value history of these properties rather than overwriting them, CS_COUNTER_PROP_VALUES functions as a transactional history store, allowing reports and business processes to reconstruct how a counter's measured values changed over time.

From a Data Vault modeling perspective, the ETRM metadata classifies this table heuristically as a link. This classification is a suggestion derived from the foreign-key structure: the table resolves a relationship between an instance-level counter value and a counter property definition. In practice, however, the table also carries an effective-date-like character typical of a satellite, since it retains historical snapshots of property values. Designers populating a dimensional or Data Vault layer should treat it as a bridge linking counter values to their property definitions while retaining the historical context. The table is documented in ETRM as not implemented in the current database, so deployments should verify actual instantiation before assuming runtime data availability.

Key Information Stored

The documented structure centers on a single surrogate primary key and two foreign-key columns:

• COUNTER_PROP_VALUE_ID — surrogate primary key, enforced by CS_COUNTER_PROP_VALUES_PK. Uniquely identifies each historical property value row.
• COUNTER_VALUE_ID — foreign key to CS_COUNTER_VALUES. Identifies the parent counter reading (the counter value instance) to which this property value belongs.
• COUNTER_PROPERTY_ID — foreign key to CS_COUNTER_PROPERTIES. Identifies the counter property definition being recorded.

The metadata does not expose documented unique business indexes beyond the primary key, so COUNTER_VALUE_ID and COUNTER_PROPERTY_ID should be treated as the principal business-key candidates for joins; a combination of these two columns, possibly together with an effective or reading date attribute, would typically distinguish a specific historical value. Additional descriptive and numeric value columns, plus date-stamped creation and update audit columns, are expected in the physical table but are not enumerated in the documented metadata and should be confirmed by querying ALL_TAB_COLUMNS.

Common Use Cases and Queries

The most frequent scenario is reconstructing the reading history of a counter to support usage-based billing, warranty validation, or asset health reporting. A representative join pattern follows:

• Join CS_COUNTER_PROP_VALUES to CS_COUNTER_VALUES on COUNTER_PROP_VALUES.COUNTER_VALUE_ID = COUNTER_VALUES.COUNTER_VALUE_ID to bring property-level detail up to the counter reading level.
• Join CS_COUNTER_PROP_VALUES to CS_COUNTER_PROPERTIES on COUNTER_PROP_VALUES.COUNTER_PROPERTY_ID = COUNTER_PROPERTIES.COUNTER_PROPERTY_ID to resolve the property name and definition.
• Filter by COUNTER_VALUE_ID to retrieve every historical property value recorded for one counter reading, or group by COUNTER_PROPERTY_ID to trend a specific property across all readings.
• Aggregate property values over a date range for period-over-period consumption reporting, validating that metered usage matches contracted entitlement.

Reporting use cases include meter reconciliation, planned-maintenance triggers based on accumulated usage, and dispute investigation where the sequence of recorded property values must be audited.

Related Objects

The following objects are most significant relative to CS_COUNTER_PROP_VALUES, based on the documented foreign-key relationships:

• CS_COUNTER_VALUES — parent counter reading table; linked via COUNTER_PROP_VALUES.COUNTER_VALUE_ID = COUNTER_VALUES.COUNTER_VALUE_ID. The primary dependency for any value-level query.
• CS_COUNTER_PROPERTIES — counter property definition table; linked via COUNTER_PROP_VALUES.COUNTER_PROPERTY_ID = COUNTER_PROPERTIES.COUNTER_PROPERTY_ID. Supplies property metadata and validation rules.
• CS_COUNTER_PROP_VALUES_PK — primary key constraint over COUNTER_PROP_VALUE_ID, enforcing row uniqueness.

Beyond these documented relationships, reporting queries commonly traverse upward through the counter and installed-base hierarchy to reach item instances, service contracts, and customer accounts, which provides the business context needed to interpret the property values historically retained in this table.