Results for “cs_counter_properties”

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

Overview

CS_COUNTER_PROPERTIES is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the individual property definitions belonging to a service counter. A counter in Oracle Service represents a measurement construct—such as mileage, hours of operation, or cycle count—used to track usage and drive preventive maintenance, warranty, and service entitlement logic. Each row in CS_COUNTER_PROPERTIES defines one attribute (property) of a parent counter, such as its value type, units, or derivation behavior. The table therefore sits at the intersection of counter configuration and the runtime property values recorded against installed base items.

From a Data Vault modeling perspective, the heuristic classification is hub-leaning. The unique key CS_COUNTER_PROPERTIES_UK1 (COUNTER_ID, NAME) establishes a durable, uniquely identified business concept—a named property within a counter—while the self-referencing foreign keys support versioning and lineage. This suggests the table functions primarily as a hub of counter property identities, with dependent satellite and link structures implied by the surrounding relationships.

Key Information Stored

The following columns are the most significant, based on the documented metadata:

• COUNTER_PROPERTY_ID — the surrogate primary key (CS_COUNTER_PROPERTY_PK), uniquely identifying each property row regardless of its business context.
• COUNTER_ID — foreign key to CS_COUNTERS, establishing the parent counter to which the property belongs; combined with NAME it forms the business unique key CS_COUNTER_PROPERTIES_UK1.
• NAME — the business name of the property; the second component of the unique business key.
• CREATED_FROM_CTR_PROP_TMPL_ID — self-referencing foreign key identifying the counter property template from which this property was instantiated, supporting template-driven configuration.
• SOURCE_COUNTER_PROP_ID — self-referencing foreign key indicating the originating property when the row was copied or derived from another counter property.

The presence of both a surrogate key and a composite business key is important for integration and de-duplication. The self-references for template origin and source property provide traceability, while the parent COUNTER_ID anchors the property to its owning counter. Note that the metadata marks this table as "Not implemented in this database," indicating it may not exist in every schema or may be deployed only in specific configurations.

Common Use Cases and Queries

Typical usage involves enumerating the properties defined for a given counter, tracing property provenance, and joining to recorded values. For example, to list all properties of a specific counter:

• SELECT counter_property_id, counter_id, name FROM cs_counter_properties WHERE counter_id = :counter_id;

To compare properties instantiated from templates versus those defined directly, query CREATED_FROM_CTR_PROP_TMPL_ID. To trace a property back to its source, join the row to its SOURCE_COUNTER_PROP_ID. Reporting scenarios include counter configuration audits, template compliance checks, and analysis of which properties have captured readings, achieved by joining CS_COUNTER_PROP_VALUES on COUNTER_PROPERTY_ID.

Related Objects

The most significant related objects, derived from the documented foreign keys, are:

• CS_COUNTERS — parent counter; joined via CS_COUNTER_PROPERTIES.COUNTER_ID = CS_COUNTERS.COUNTER_ID. Also references this table through CS_COUNTERS.DERIVE_PROPERTY_ID.
• CS_COUNTER_PROP_VALUES — stores recorded values; joined via COUNTER_PROPERTY_ID.
• CS_COUNTER_DER_FILTERS — derivation filters; joined via COUNTER_PROPERTY_ID.
• CS_COUNTER_PROPERTIES (self) — referenced through CREATED_FROM_CTR_PROP_TMPL_ID and SOURCE_COUNTER_PROP_ID for template and source lineage.

Together these relationships define the counter property ecosystem within Oracle Service, linking configuration definitions to the derived filters and captured values that drive service execution.