Results for “cs_counter_grp_log”

50+ results




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

Overview

CS_COUNTER_GRP_LOG is a Service (CS) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It functions as the counter group log that records counter updates occurring within a counter group. In the Service application, counters are used to track consumption, usage, or metered quantities against service contracts, subscriptions, and installed base records. The CS_COUNTER_GRP_LOG table maintains the historical trace of those updates, capturing the timestamp, the originating transaction, and the counter group against which the update was applied. It therefore serves as the transactional ledger that supports counter auditing, reconciliation, and downstream processing of counter values.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table holds descriptive, time-stamped update details keyed to parent entities rather than acting as an independent business hub or a pure associative link. This classification is a heuristic suggestion derived from the foreign key topology; the table's design intent is to log changes to counter groups over time.

Key Information Stored

The table contains 28 documented columns in the CS schema. The most significant are described below.

The distinction between the surrogate key and the unique index is important: COUNTER_GRP_LOG_ID functions both as the PK and as the unique business-key candidate in the documented schema, while COUNTER_GROUP_ID is a non-unique reference back to the parent counter group.

Common Use Cases and Queries

Typical reporting scenarios include reconciling counter values against their originating transactions, auditing counter consumption history for a given service contract or group, and troubleshooting discrepancies between expected and reported counter values.

  • Retrieving the update history for a counter group by joining to CS_COUNTER_GROUPS on COUNTER_GROUP_ID and ordering by VALUE_TIMESTAMP.
  • Tracing a counter update to its source transaction using SOURCE_TRANSACTION_CODE and SOURCE_TRANSACTION_ID.
  • Correlating log entries to child counter values via CS_COUNTER_VALUES.COUNTER_GRP_LOG_ID.
  • Filtering by SECURITY_GROUP_ID for security-group-specific reporting.
  • Auditing creation and last-update metadata through the standard audit columns.

Related Objects

The following objects are the most significant references or dependents based on documented foreign key relationships.

  • CS_COUNTER_GROUPS — Parent table joined via CS_COUNTER_GRP_LOG.COUNTER_GROUP_ID.
  • CS_COUNTER_VALUES — Child table referencing this table through CS_COUNTER_VALUES.COUNTER_GRP_LOG_ID.
  • CSI_TXN_TEMP — References this table via COUNTER_GRP_LOG_ID during transactional counter processing.
  • FND_SECURITY_GROUPS — Referenced through CS_COUNTER_GRP_LOG.SECURITY_GROUP_ID.
  • CS_COUNTER_GRP_LOG_PK / CS_COUNTER_GRP_LOG_U1 — The primary key constraint and unique index defining row identity.