Results for “cs_counter_groups”

50+ results




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

Overview

CS_COUNTER_GROUPS is a Service (CS) module table that stores counter group templates and counter group instances used within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Counter groups serve as the logical container for one or more counters that track usage, consumption, or threshold metrics on customer assets. A template counter group defines the reusable structure and counter definitions, while an instance counter group is created from that template and bound to a specific source object, most commonly an item instance in CSI_ITEM_INSTANCES. The table therefore acts as the central registry reconciling template definitions with their materialized instances.

The ETRM relationship metadata classifies the table as hub-leaning under a heuristic Data Vault model. This suggests CS_COUNTER_GROUPS behaves primarily as a business entity hub, keyed by a stable identity, with its descriptive attributes and lifecycle events distributed into satellite or log structures. Note that the object is documented as "Not implemented in this database," indicating the DDL may not be deployed in every environment, so its presence should be confirmed before building dependencies.

Key Information Stored

The table is anchored by a surrogate primary key and a composite unique key that together govern row identity and business uniqueness.

The presence of SOURCE_OBJECT_CODE and SOURCE_OBJECT_ID in the unique index establishes them as the principal business-key candidates, while COUNTER_GROUP_ID remains the technical surrogate. Descriptive and audit columns follow the standard EBS column conventions, but only the identifiers above are explicitly documented in the ETRM metadata.

Common Use Cases and Queries

Typical usage centers on resolving the counters attached to an asset, tracing instance groups back to their templates, and reporting counter history. A representative query joins instances to their source item instance:

  • Identify all counter groups for a given asset: select cg.COUNTER_GROUP_ID from CS_COUNTER_GROUPS cg where cg.SOURCE_OBJECT_ID = :item_instance_id and cg.SOURCE_OBJECT_CODE = :code.
  • Trace an instance to its template: join CREATED_FROM_CTR_GRP_TMPL_ID back to COUNTER_GROUP_ID on the same table.
  • Report active counters in a group: join CS_COUNTERS on COUNTER_GROUP_ID.
  • Audit lifecycle changes via CS_COUNTER_GRP_LOG, keyed by COUNTER_GROUP_ID.

These patterns support meter-based billing, preventive maintenance thresholds, and service contract usage verification.

Related Objects

  • CS_COUNTERS — Child counters belonging to the group (COUNTER_GROUP_ID).
  • CS_COUNTER_GRP_LOG — Log of counter group changes (COUNTER_GROUP_ID).
  • CS_CTR_ASSOCIATIONS — Counter associations (COUNTER_GROUP_ID).
  • CSI_ITEM_INSTANCES — Source item instances referenced by SOURCE_OBJECT_ID.
  • AHL_RELATIONSHIPS_B — Asset relationship records referencing the group.
  • CS_CTR_ESTIMATION_METHODS — Estimation methods tied to counter groups.
  • OKC_CONDITION_HEADERS_B / _BH — Contract condition headers referencing counter groups.
  • OKL_LINES_INTERFACE — Lease line interface referencing counter groups.