Search Results csi_ctr_property_readings_pk

Overview

The CSI_CTR_PROPERTY_READINGS table is a core transactional data object within the Oracle E-Business Suite Install Base module (CSI). It stores counter readings property data, capturing the individual measured values, attributes, and timestamps associated with counters installed on customer assets. In the broader Enterprise Asset Management and Install Base context, counters represent cumulative or point-in-time measurements (such as meter readings, cycle counts, or usage hours) recorded against an asset, and this table persists the detailed property values generated when such readings are captured.

The table resides in the CSI schema and holds 28 documented columns in ETRM 12.2.2. Its structure follows the standard Oracle EBS audit and extensibility conventions, incorporating WHO columns and 15 descriptive flexfield (DFF) attribute columns. From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests the table can be modeled as an independent structure rather than a dependent satellite or link, although in practice it functions as a child of the counter and counter-value entities through its key columns.

Key Information Stored

The physical schema centers on a surrogate primary key and a set of operational and audit columns. The most significant columns include:

• COUNTER_PROP_VALUE_ID — The surrogate primary key, enforced by CSI_CTR_PROPERTY_READINGS_PK and also documented as the unique index CSI_CTR_PROPERTY_READINGS_U01. It uniquely identifies each counter property reading row.
• COUNTER_VALUE_ID — References the parent counter value record (the reading event) to which this property belongs.
• COUNTER_PROPERTY_ID — Identifies the specific property definition associated with the reading, linking to counter property setup.
• PROPERTY_VALUE — Holds the actual measured or captured property value.
• VALUE_TIMESTAMP — The date and time at which the property value was recorded, critical for chronological reporting.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrency control during updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit WHO columns tracking row provenance.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments enabling client-specific extensibility without schema changes.
• MIGRATED_FLAG — Indicates whether the row originated from a data migration, useful for reconciliation.

The distinction between the surrogate key (COUNTER_PROP_VALUE_ID) and any natural business-key candidates is important; here the documented unique index simply reinforces the surrogate key rather than defining a separate composite business key.

Common Use Cases and Queries

Typical usage revolves around asset counter analysis, meter-based billing, and preventive maintenance scheduling. A common query retrieves all property readings for a given counter value:

• SELECT counter_prop_value_id, counter_value_id, counter_property_id, property_value, value_timestamp FROM csi_ctr_property_readings WHERE counter_value_id = :p_counter_value_id;
• Joining to counter property definitions to translate COUNTER_PROPERTY_ID into human-readable property names for reports.
• Filtering by VALUE_TIMESTAMP to produce trending and consumption reports across time windows.
• Querying MIGRATED_FLAG to isolate legacy-migrated readings for validation after an upgrade or data conversion.

Reporting use cases include warranty validation based on usage counters, preventive maintenance triggers when thresholds are exceeded, and asset utilization dashboards.

Related Objects

Because the heuristic classification is standalone, documented FK relationships are limited, but the table logically references surrounding Install Base counter entities through its key columns:

• CSI_COUNTER_VALUES — Parent reading event, joined on COUNTER_VALUE_ID.
• CSI_COUNTER_PROPERTIES — Property definitions, joined on COUNTER_PROPERTY_ID.
• CSI_COUNTERS — Counter configuration master.
• CSI_ITEM_INSTANCES — The installed asset instances to which counters are attached.
• CSI_CTR_PROPERTY_READINGS_PK / _U01 — Primary and unique indexes enforcing key integrity.

Together these objects form the counter-reading chain within the CSI Install Base data model, with CSI_CTR_PROPERTY_READINGS serving as the detailed property-level store.