Search Results csi_counter_readings_pk

Overview

The CSI_COUNTER_READINGS table resides in the CSI schema, which supports the Install Base module of Oracle E-Business Suite 12.1.1 and 12.2.2. This table stores counter readings along with their historical readings data, forming the meter-reading backbone for installed assets tracked in the Install Base. In the context of Oracle EBS servicing, counters represent measurable usage quantities — such as odometer distance, operating hours, or units produced — associated with an instance or item. Each row captures a single counter value recorded at a specific point in time, together with the reset, adjustment, and rollover attributes that govern how the counter is interpreted across its lifecycle.

From a Data Vault modeling perspective, the mined metadata classifies this table as standalone. The heuristic is derived from the foreign-key structure, which shows only a single outbound reference to FND_SECURITY_GROUPS. This suggests the table behaves as a self-contained record rather than participating in a broader hub-and-link topology. Practitioners applying Data Vault principles may therefore treat it as a satellite-like store of measurement events anchored to a counter identifier, rather than as a link joining multiple business entities.

Key Information Stored

The table carries 58 documented columns. The most significant operational columns include:

• COUNTER_VALUE_ID — the surrogate primary key, defined by CSI_COUNTER_READINGS_PK and also backed by the unique index CSI_COUNTER_READINGS_U01.
• COUNTER_ID — identifies the parent counter to which the reading belongs.
• VALUE_TIMESTAMP — the effective date and time of the reading.
• COUNTER_READING, ADJUSTMENT_READING, NET_READING — the raw, adjusted, and net computed readings.
• LIFE_TO_DATE_READING — cumulative reading since counter inception.
• RESET_MODE, RESET_REASON — control how and why a counter was reset.
• ADJUSTMENT_TYPE, AUTOMATIC_ROLLOVER_FLAG — adjustment and overflow behavior.
• SOURCE_COUNTER_VALUE_ID, INITIAL_READING_FLAG — lineage to a prior reading and delta capture.

The surrogate key is CO UNTER_VALUE_ID; no separate business-key column is documented beyond this unique index. The SECURITY_GROUP_ID foreign key enforces multi-tenant data security.

Common Use Cases and Queries

Typical usage centers on retrieving the latest reading for a counter, reconstructing reading history, and validating resets or rollovers.

• Current reading lookup: SELECT * FROM csi.csi_counter_readings WHERE counter_id = :p_counter_id ORDER BY value_timestamp DESC.
• Lifecycle reporting: aggregate NET_READING and LIFE_TO_DATE_READING by counter for usage analytics.
• Audit queries filtering RESET_MODE, RESET_REASON, or DISABLED_FLAG to isolate anomalies.
• Security-scoped extracts joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

The documented foreign key links CSI_COUNTER_READINGS.SECURITY_GROUP_ID to FND_SECURITY_GROUPS. Logical relationships bind COUNTER_ID to the CSI counter definition, while SOURCE_COUNTER_VALUE_ID self-references prior readings. Related CSI Install Base tables and public APIs that create or consume readings include the counter definition entity, the Install Base instance tables, and meter-reading APIs exposed through the CSI module. Query SOURCE_COUNTER_VALUE_ID and COUNTER_ID joins when tracing reading lineage across service and billing processes.