Search Results cs_counter_grp_log_pk

Overview

The CS_COUNTER_GRP_LOG table is a core transactional logging object within the Oracle E-Business Suite Service (CS) module, specifically for releases 12.1.1 and 12.2.2. It serves as an audit and control mechanism for tracking updates to counter readings that are processed as part of a defined group. In service management, counters are used to measure usage (e.g., machine cycles, miles, copies) for serviceable items. When counters are updated in bulk as a group—often for efficiency or to maintain transactional consistency—this table logs the overarching group transaction. Its primary role is to provide a traceable link between a group update event and the individual counter value records (CS_COUNTER_VALUES) that were modified as a result, ensuring data integrity and supporting audit requirements.

Key Information Stored

The table's structure is designed to capture the essential details of a group counter update event. Its primary key, COUNTER_GRP_LOG_ID, is a unique system-generated identifier for each log entry. A critical foreign key column is COUNTER_GROUP_ID, which references the CS_COUNTER_GROUPS table, thereby identifying the specific counter group definition under which the update was performed. While the provided ETRM metadata does not list all columns, typical columns in such a log table would likely include creation date (CREATION_DATE), created by (CREATED_BY), and possibly a timestamp for the group transaction. The existence of the primary key constraint CS_COUNTER_GRP_LOG_PK underscores the importance of the COUNTER_GRP_LOG_ID column for uniquely identifying each logged group transaction.

Common Use Cases and Queries

This table is central to troubleshooting and auditing batch counter updates. A common use case involves reconciling counter readings by tracing a discrepancy in an individual counter's history back to the original group transaction that caused the change. For reporting, it enables analysis of group update frequency and volume. A typical diagnostic query would join this log to the counter values and groups to understand the full context of an update.

• Sample Query: Find details for a specific group update:
  SELECT log.counter_grp_log_id, log.counter_group_id, grp.name, val.counter_value
  FROM cs_counter_grp_log log,
  cs_counter_groups grp,
  cs_counter_values val
  WHERE log.counter_group_id = grp.counter_group_id
  AND log.counter_grp_log_id = val.counter_grp_log_id
  AND log.counter_grp_log_id = :p_log_id;
• Audit Reporting: Generating a list of all group updates performed within a date range, including the user who initiated them, by joining with FND_USER on the CREATED_BY column.

Related Objects

The CS_COUNTER_GRP_LOG table is a nexus between counter group definitions and the actual counter reading data. As documented in the foreign keys, it has direct relationships with two key tables:

• CS_COUNTER_GROUPS: This table defines the counter groups themselves. The foreign key from CS_COUNTER_GRP_LOG.COUNTER_GROUP_ID to this table establishes which predefined group the log entry belongs to.
• CS_COUNTER_VALUES: This table stores the individual historical counter readings. The foreign key relationship is inverse here; the CS_COUNTER_VALUES table holds a COUNTER_GRP_LOG_ID column that references back to this log table. This is the critical link that allows each updated counter value record to point to the group transaction that created it.

Understanding these relationships is essential for any data extraction or integrity analysis concerning batch counter processing in Oracle Service.