Search Results csi_counter_reading_locks




Overview
Explore in AI Chat

Overview

The CSI_COUNTER_READING_LOCKS table is a core data object within the CSI – Install Base product module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. The table resides in the CSI schema and holds the counter reading lock data used by Oracle's Enterprise Asset Management (eAM) and Install Base counter functionality. In operational terms, an equipment counter records cumulative usage — meter readings, cycle counts, run hours, or units produced — and the reading lock mechanism prevents overlapping or conflicting counter readings from being recorded against the same counter for the same period. This table therefore acts as the authoritative registry of active locks that gate counter reading transactions.

From a heuristic Data Vault perspective, the mined metadata classifies this object as standalone, meaning that its foreign key structure does not clearly resolve to a parent hub or link in the surrounding model. In modeling terms, this suggests the table is best treated as an independent satellite-like construct, with its own surrogate key (READING_LOCK_ID) rather than as a dependent child of a broader business entity. This classification should be regarded as a modeling suggestion rather than a definitive architectural statement.

Key Information Stored

The documented physical schema for release 12.2.2 defines 17 columns, with the following being the most materially significant:

Common Use Cases and Queries

Administrators and developers query this table to determine why a counter cannot accept a new reading, to audit stale locks, and to trace locks back to source documents. A typical diagnostic query retrieves active locks for a specific counter:

  • SELECT reading_lock_id, counter_id, reading_lock_date, source_header_ref FROM csi.csi_counter_reading_locks WHERE counter_id = :p_counter_id ORDER BY reading_lock_date DESC;
  • SELECT reading_lock_id, counter_id, created_by, creation_date FROM csi.csi_counter_reading_locks WHERE creation_date >= SYSDATE - 1; — to identify locks created in a recent window, aiding troubleshooting of failed counter entry.
  • Joins against counter definition tables on COUNTER_ID to report which assets hold the most locks, or to reconcile lock records against source header references during periodic data cleanup.

Related Objects

The table's standalone classification means no strong foreign key relationships were mined, but the following objects are operationally significant:

  • CSI_COUNTER_READINGS — the transactional counterpart where accepted readings are stored; locks in this table govern whether a new reading may be inserted.
  • CSI_COUNTERS — the counter definition table, joined via COUNTER_ID.
  • CSI_ITEM_INSTANCES — the installed base instance to which counters belong, reachable through the counter definition.
  • CSI_COUNTER_READINGS_PUB and related PL/SQL APIs in the CSI schema, which enforce lock validation during reading insertion.
  • Source document tables referenced by the SOURCE_* columns, such as work order and manufacturing transaction headers, used to reconcile the origin of each lock.