Results for “cs_counters”

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

Overview

The CS_COUNTERS table is a core data object within the Oracle E-Business Suite Service (CS) module. As documented in the ETRM metadata, it stores counter templates and instances, meaning it holds both the blueprint definitions used to create counters and the active counter records themselves. Counters in the Service module are used to track cumulative consumption or usage metrics — such as meter readings, cycle counts, or units consumed — against serviceable items, contracts, and installed base assets. The table therefore plays a central role in metering, billing, preventive maintenance scheduling, and usage-based service entitlement.

The heuristic Data Vault classification mined from the foreign key structure is hub-leaning. In Data Vault modeling terms, this suggests CS_COUNTERS behaves primarily as a hub, holding the durable business keys and identity of each counter, with satellites (such as CS_COUNTER_VALUES and CS_COUNTER_PROPERTIES) carrying descriptive and transactional attributes around it. This classification is a modeling suggestion only, derived from the connectivity of the documented key relationships, and should be validated against actual usage.

The ETRM metadata records the table as "Not implemented in this database," indicating the object may be conditionally deployed depending on the modules and features licensed and configured in a given environment.

Key Information Stored

The following columns are the most significant based on the documented primary, unique, and foreign key metadata:

• COUNTER_ID — The surrogate primary key defined by CS_COUNTERS_PK. It uniquely identifies each counter template or instance and is the column referenced by all dependent child tables.
• COUNTER_GROUP_ID — Groups related counters together. It participates in two unique keys (CS_COUNTERS_UK1 and CS_COUNTERS_UK2) and is a foreign key to CS_COUNTER_GROUPS.
• NAME — The counter name, combined with COUNTER_GROUP_ID in unique key CS_COUNTERS_UK1, making it a business-key candidate for uniqueness within a group.
• USAGE_ITEM_ID — Combined with COUNTER_GROUP_ID in unique key CS_COUNTERS_UK2, linking the counter to the specific usage item it measures.
• CREATED_FROM_COUNTER_TMPL_ID — Self-referencing foreign key indicating the template counter from which this instance was created.
• SOURCE_COUNTER_ID — Self-referencing foreign key identifying a source counter, supporting counter lineage and derivation.
• DERIVE_COUNTER_ID — Self-referencing foreign key identifying a counter from which this value is derived.
• DERIVE_PROPERTY_ID — Foreign key to CS_COUNTER_PROPERTIES, defining the property used in derivation logic.
• ESTIMATION_ID — Foreign key to CS_CTR_ESTIMATION_METHODS, associating an estimation method used to project counter readings.

The distinction between COUNTER_ID (surrogate) and the NAME/COUNTER_GROUP_ID and USAGE_ITEM_ID/COUNTER_GROUP_ID pairs (business keys) is essential for integration and data-migration work.

Common Use Cases and Queries

Typical scenarios include retrieving all counters for a given group, locating the template behind a counter instance, or reporting counter values for metering and billing. The following patterns reflect the documented relationships.

List counters and their groups:

SELECT c.counter_id, c.name, g.counter_group_id
FROM   cs_counters c, cs_counter_groups g
WHERE  c.counter_group_id = g.counter_group_id;

Find instances derived from a template:

SELECT counter_id, name, created_from_counter_tmpl_id
FROM   cs_counters
WHERE  created_from_counter_tmpl_id IS NOT NULL;

Retrieve current values for a counter:

SELECT v.counter_id, v.value
FROM   cs_counter_values v
WHERE  v.counter_id = :counter_id;

These queries support usage reporting, threshold monitoring, and reconciliation against preventive maintenance intervals.

Related Objects

The following tables are the most significant dependents and references, with the join columns documented in the key metadata:

• CS_COUNTER_GROUPS — joined via CS_COUNTERS.COUNTER_GROUP_ID.
• CS_COUNTER_PROPERTIES — joined via COUNTER_ID and referenced through DERIVE_PROPERTY_ID.
• CS_COUNTER_VALUES — joined via CS_COUNTER_VALUES.COUNTER_ID.
• CS_COUNTER_DER_FILTERS — joined via CS_COUNTER_DER_FILTERS.COUNTER_ID.
• CS_CTR_ESTIMATION_METHODS — joined via ESTIMATION_ID.
• CS_CTR_FORMULA_BVARS — joined via COUNTER_ID and MAPPED_COUNTER_ID.
• AHL_MR_INTERVALS — joined via AHL_MR_INTERVALS.COUNTER_ID, linking counters to maintenance intervals in the asset module.

Self-referencing relationships (CREATED_FROM_COUNTER_TMPL_ID, SOURCE_COUNTER_ID, DERIVE_COUNTER_ID) further establish CS_COUNTERS as a composite hub anchoring counter definitions and their derived lineage.