Results for “cs_ctr_counter_grp_log_v”

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

Overview

CS_CTR_COUNTER_GRP_LOG_V is a reporting view within the Oracle E-Business Suite Service (CS) module. It is documented in the ETRM reference as "Counter group log view," and its purpose is to present the transactional history of counter group activity in a denormalized, human-readable form. In Oracle Service, counter groups define sets of meters or counters (for example, copies produced, hours run, or units consumed) that are tracked against serviceable inventory items such as customer products or assets. Each time a counter value is captured, an entry is written to the counter group log. The view joins that log to the counter group definition so that the group name and description are available alongside the logged value, rather than requiring the consumer to perform the join manually.

The view is read-only and is intended for reporting, inquiry, and integration rather than for direct data maintenance. Because it exposes descriptive attributes such as the counter group name and description together with timestamp and source transaction information, it is a convenient source for dashboards, extracts, and custom concurrent programs that need counter group history without navigating the underlying normalized schema. Note that the ETRM metadata records the object as not implemented in the reference database, meaning the definition is documented but no live instance existed in that environment.

Underlying Base Objects

The view is defined over two base tables of the Service module:

• CS_COUNTER_GRP_LOG (aliased A) — the transactional log that stores individual counter value records, including the counter group identifier, the source transaction that triggered the log entry, the value timestamp, and the standard EBS WHO columns and descriptive flexfield attributes.
• CS_COUNTER_GROUPS (aliased C) — the counter group definition table that holds the group name, description, and active date range.

The two are connected by an equijoin on COUNTER_GROUP_ID (A.COUNTER_GROUP_ID = C.COUNTER_GROUP_ID). Because the join is an inner join, only log rows whose counter group still exists in CS_COUNTER_GROUPS will be returned. The view also selects A.ROWID as ROW_ID, an EBS convention that preserves a row identifier for downstream processing even though the view itself is non-updatable.

Key Columns

• COUNTER_GRP_LOG_ID — primary identifier of the individual log entry.
• COUNTER_GROUP_ID — foreign key to the counter group definition.
• COUNTER_GROUP_NAME (C.NAME) — the name of the counter group, useful for filtering and display.
• COUNTER_GROUP_DESCRIPTION (C.DESCRIPTION) — the descriptive text of the counter group; this is the column most commonly targeted by users searching on the term "counter_group_description."
• SOURCE_TRANSACTION_ID / SOURCE_TRANSACTION_CODE — identify the business event or transaction that generated the counter reading.
• VALUE_TIMESTAMP — the effective date and time of the logged counter value.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range of the counter group definition (from C).
• OBJECT_VERSION_NUMBER — optimistic locking version, carried through for consistency.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — descriptive flexfield segments and their context, enabling reporting on customer-defined attributes.

Common Use Cases and Queries

Typical uses include retrieving the full counter history for a given group, restricting to a date window, or reporting by source transaction. A simple query by description follows:

• SELECT counter_group_name, counter_group_description, value_timestamp, source_transaction_code FROM cs_ctr_counter_grp_log_v WHERE UPPER(counter_group_description) LIKE UPPER('%meter%') ORDER BY value_timestamp DESC;
• SELECT counter_grp_log_id, counter_group_name, value_timestamp FROM cs_ctr_counter_grp_log_v WHERE counter_group_id = :p_group_id AND value_timestamp BETWEEN :p_from AND :p_to;
• SELECT source_transaction_code, COUNT(*) FROM cs_ctr_counter_grp_log_v GROUP BY source_transaction_code;

Because the view performs the join to CS_COUNTER_GROUPS automatically, it is preferable to querying the log table directly when the group name or description is required. Performance is generally driven by indexed access on COUNTER_GROUP_ID in both underlying tables.