Results for “value_timestamp”

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

Overview

OKX_COUNTER_GRP_LOG_V is a reporting view owned by the APPS schema within the OKX – Contracts Integration product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to present a counter group log: a record of counter updates that occur within a counter group. In the Oracle EBS architecture, views such as this are typically created to provide a stable, denormalized, or simplified projection of one or more base tables so that concurrent programs, Oracle Reports, Oracle Forms LOVs, and external integrations can query the data without depending directly on the underlying physical table definition. Since the OKX module handles contracts integration, this view supports the tracking and auditing of counter values that drive document numbering, sequence generation, or similar contract-processing logic. The view is documented as VALID in both release levels, indicating that its definition is consistent with the current base object structure.

Underlying Base Objects

The view is defined over a single base object: CS_COUNTER_GRP_LOG, which is accessible in the APPS schema through a SYNONYM. The view definition is a straightforward projection:

• SELECT CGL.COUNTER_GRP_LOG_ID, CGL.COUNTER_GROUP_ID, CGL.VALUE_TIMESTAMP FROM CS_COUNTER_GRP_LOG CGL

Because there is a one-to-one mapping between the view columns and the underlying columns, the view adds no join logic, aggregation, or filtering. Its value is primarily architectural: it masks the base table name so that integrations and custom code reference the OKX-prefixed view rather than the CS_COUNTER_GRP_LOG table directly. This decoupling allows the underlying table to be reorganized or renamed in a future patch or upgrade without breaking dependent code, provided the view definition is maintained. No additional tables, lookup objects, or synonyms are documented as part of the view's definition.

Key Columns

The view exposes exactly three columns, each mirroring a column on CS_COUNTER_GRP_LOG:

• COUNTER_GRP_LOG_ID — The unique identifier for an individual counter group log entry. This is the primary key for the log record and is typically generated from a sequence. It should be used when joining the view back to other log-related tables or when deduplicating records.
• COUNTER_GROUP_ID — The foreign key identifying the counter group to which the log entry belongs. A single counter group may accumulate multiple log entries over time, so this column is the principal grouping dimension for reporting counter activity per group.
• VALUE_TIMESTAMP — The timestamp associated with the counter value recorded in the log. This column corresponds directly to the "value_timestamp" term commonly searched by developers and DBAs working with OKX counter data. It supports chronological ordering and time-range filtering of counter updates, enabling audits of when a group counter was last incremented or changed.

Common Use Cases and Queries

Typical uses include auditing counter activity for a specific counter group, identifying the most recent counter update, and feeding reports that reconcile contract document numbering against counter history. The following examples illustrate standard access patterns:

• List all log entries for a given counter group, newest first:
  SELECT counter_grp_log_id, counter_group_id, value_timestamp FROM okx_counter_grp_log_v WHERE counter_group_id = :p_group_id ORDER BY value_timestamp DESC;
• Retrieve the latest counter update per counter group:
  SELECT counter_group_id, MAX(value_timestamp) last_update FROM okx_counter_grp_log_v GROUP BY counter_group_id;
• Filter log entries within a reporting window for audit or reconciliation:
  SELECT counter_grp_log_id, counter_group_id, value_timestamp FROM okx_counter_grp_log_v WHERE value_timestamp BETWEEN :p_from_date AND :p_to_date ORDER BY value_timestamp;

Because the view contains no joins, queries against it are inexpensive and can be safely embedded in concurrent programs or BI Publisher data templates. As with all APPS-owned OKX objects, custom code should reference the view rather than CS_COUNTER_GRP_LOG to remain upgrade-safe.