Search Results cs_counter_groups_v




Overview
Explore in AI Chat

Overview

CS_COUNTER_GROUPS_V is a reporting and integration view within the Oracle E-Business Suite Service (CS) module. It exposes counter group definitions used by Oracle TeleService and related Service applications to organize counters — the measurable quantities or meter readings tracked against serviceable items, contracts, and installed base assets. A counter group bundles one or more individual counters into a logical set, and the view surfaces the group header attributes: identity, naming, descriptive text, template status, source tracking, and the standard EBS WHO columns. The object is documented in ETRM at the 12.2.2 level and is present in the 12.1.1 and 12.2.2 code lines as part of the CS schema, where it is typically used for read-only reporting and for integrations that must resolve counter group identifiers without touching the base table. Per the ETRM metadata, the view is not implemented as a standalone database object in the reference database, and no dependent base objects are separately documented — the definition is derived entirely from CS_COUNTER_GROUPS.

Underlying Base Objects

The view is defined over a single base table, CS_COUNTER_GROUPS, aliased as A. The SELECT list is a direct projection: every column is drawn from the base table with no joins, unions, or aggregations. The one structural addition is A.ROWID, exposed under the column name ROW_ID, which provides the physical row address of the underlying CS_COUNTER_GROUPS record. Because the view is a straight projection, it inherits the base table's filtering, security, and partitioning behavior; there is no view-level WHERE clause and no Multi-Org policy applied at the view layer. The ETRM excerpt lists no additional referenced objects, and the view text confirms that no lookup, flexfield, or cross-module table is joined. Any foreign keys implied by SOURCE_OBJECT_CODE, SOURCE_OBJECT_ID, SOURCE_COUNTER_GROUP_ID, or CREATED_FROM_CTR_GRP_TMPL_ID are resolved by the calling application rather than by the view itself. The absence of documented base objects in the metadata should be read as "no dependencies beyond the primary table," not as missing definition.

Key Columns

  • ROW_ID — the ROWID of the underlying CS_COUNTER_GROUPS row; useful for high-volume, row-addressable operations.
  • COUNTER_GROUP_ID — primary key of the counter group; the join key to counter group membership and counter definition tables.
  • NAME and DESCRIPTION — user-facing identification and free-text description of the group.
  • TEMPLATE_FLAG — indicates whether the record is a template that can be used to instantiate new counter groups.
  • SOURCE_OBJECT_CODE, SOURCE_OBJECT_ID, SOURCE_COUNTER_GROUP_ID — denormalized provenance fields recording the originating entity when a group was generated or copied.
  • CREATED_FROM_CTR_GRP_TMPL_ID — the template counter group from which this record was created, when applicable.
  • ASSOCIATION_TYPE — classifies how the group is associated with its owning object.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective-dating window controlling when the group is considered active.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns.
  • ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the DFF (descriptive flexfield) segment columns and context for customer-defined attributes.
  • OBJECT_VERSION_NUMBER — optimistic locking version stamped by the framework.

Common Use Cases and Queries

Typical scenarios include reporting on active counter groups, validating template availability before instantiation, and reconciling provenance when groups are copied between source objects. The view is also a convenient target for integration extracts because it avoids direct reads against the base table.

List active, non-template counter groups:

SELECT counter_group_id, name, description, association_type
FROM cs_counter_groups_v
WHERE template_flag = 'N'
AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE))
AND NVL(end_date_active, TRUNC(SYSDATE));

Find groups created from a template, with audit context:

SELECT v.counter_group_id, v.name, v.created_from_ctr_grp_tmpl_id,
v.creation_date, v.created_by
FROM cs_counter_groups_v v
WHERE v.created_from_ctr_grp_tmpl_id IS NOT NULL
ORDER BY v.creation_date DESC;

Trace provenance for a specific source object:

SELECT counter_group_id, name, source_object_code, source_object_id
FROM cs_counter_groups_v
WHERE source_object_code = :object_code
AND source_object_id = :object_id;

Because the view carries the full DFF segment set, reporting solutions can flatten CONTEXT and ATTRIBUTE1–15 for customer-specific extensions without additional joins.