Search Results csi_counter_reading_locks_u01

Overview

CSI.CSI_COUNTER_READING_LOCKS is a transaction data table within the Oracle E-Business Suite Customer Intelligence (CSI) schema. It stores the reading lock history for counters maintained in the enterprise asset and counter management functionality. A reading lock establishes a cutoff date prior to which users are prohibited from disabling, resetting, or adjusting a counter reading. This mechanism preserves the integrity of historical meter and counter data that has already been processed, billed, or used in downstream calculations.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, consistent with the transactional nature of the data it holds. Its heuristic Data Vault classification, mined from the foreign key structure, is standalone. From a dimensional modeling perspective, this suggests the object functions independently rather than as a dependent child of a well-defined hub or link, and it may be treated as a satellite-like record capturing lock events keyed by a surrogate identifier. The absence of documented foreign key relationships reinforces that it should be modeled as an autonomous entity within the CSI subject area.

Key Information Stored

The table is defined by a surrogate primary key together with a set of business columns and standard Oracle WHO audit columns. The most significant columns include:

• READING_LOCK_ID — Auto-generated internal primary key and the column underlying the unique index CSI_COUNTER_READING_LOCKS_U01. It uniquely identifies each reading lock record.
• COUNTER_ID — Identifier of the counter to which the lock applies. This column is indexed by the non-unique index CSI_COUNTER_READING_LOCKS_N01 and serves as the principal business-key candidate for lookups by counter.
• READING_LOCK_DATE — The effective lock date. Readings dated on or before this date cannot be disabled, reset, or adjusted.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent update control within the Oracle framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification metadata for each row.
• SOURCE_GROUP_REF_ID / SOURCE_GROUP_REF — Source group reference identifier and value.
• SOURCE_HEADER_REF_ID / SOURCE_HEADER_REF — Source header reference identifier and value.
• SOURCE_LINE_REF_ID / SOURCE_LINE_REF — Source line reference identifier and value.
• SOURCE_DIST_REF_ID1 / SOURCE_DIST_REF_ID2 — Source distribution reference identifiers.

The SOURCE_* columns provide traceability back to the originating document structure, allowing the lock to be associated with the transaction that triggered it.

Common Use Cases and Queries

Typical use cases include auditing when a counter was locked, determining whether a specific reading is protected from modification, and reporting lock history for compliance or billing reconciliation. A common query retrieves the current lock state for a given counter:

• SELECT READING_LOCK_ID, COUNTER_ID, READING_LOCK_DATE FROM CSI.CSI_COUNTER_READING_LOCKS WHERE COUNTER_ID = :counter_id ORDER BY READING_LOCK_DATE DESC;
• Joining to counter master data to display lock status alongside counter attributes for a reporting dashboard.
• Extracting all locks created within a date range to audit who applied locks and when, using CREATION_DATE and CREATED_BY.

Developers should be aware that the unique index on READING_LOCK_ID guarantees a single row per lock identifier, while the COUNTER_ID index supports efficient retrieval of all locks belonging to a counter.

Related Objects

Because this object is classified as standalone, the metadata documents no enforced foreign keys. Nonetheless, it is functionally related to the counter and reading entities within the CSI schema. Logical join columns are provided by the documented indexes and columns:

• CSI_COUNTER_READINGS — Joined via COUNTER_ID to relate lock dates to individual readings.
• CSI_COUNTERS — The counter master; joined on COUNTER_ID to resolve counter names and attributes.
• CSI_COUNTER_READING_LOCKS_U01 — The unique index enforcing the primary key on READING_LOCK_ID.
• CSI_COUNTER_READING_LOCKS_N01 — The non-unique index on COUNTER_ID supporting counter-based access paths.
• CSI_ITEM_INSTANCES — Instance-level records frequently associated with counters and therefore with lock history.

These relationships, while not enforced by documented referential constraints, reflect the standard integration patterns used throughout the CSI counter and reading subsystem.