Search Results csi_ctr_property_readings_u01

Overview

CSI.CSI_CTR_PROPERTY_READINGS is a transactional table in the Oracle E-Business Suite Customer Intelligence (CSI) schema that stores property attribute values associated with counter readings. In the Enterprise Asset Management (EAM) and telemetry context, a counter instance may be associated with one or more counter properties that describe the nature, unit, or context of a counter reading. When a property reading is required, the user must specify the corresponding attributes so that the reading can be captured successfully. CSI_CTR_PROPERTY_READINGS therefore preserves the supplementary detail that enriches a base counter reading, supporting analysis, condition monitoring, and warranty or maintenance decisions derived from asset usage data.

From a data modeling perspective, the metadata classifies this object heuristically as a standalone entity in a Data Vault sense. There are no documented foreign key constraints connecting it to a parent hub or link, and its grain is governed entirely by the internally generated primary key. Where a normalized Data Vault model is being designed, this table is best treated as a satellite-style attribute store anchored on the counter value or counter property business keys that it references by value rather than by enforced constraint. The physical storage uses the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and the unique index resides in APPS_TS_TX_IDX.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• COUNTER_PROP_VALUE_ID — Internally generated primary key (NUMBER). This is the enforced primary key via CSI_CTR_PROPERTY_READINGS_PK, and it is also the sole column of the unique index CSI_CTR_PROPERTY_READINGS_U01, making it the business-key candidate at the physical level.
• COUNTER_VALUE_ID — Identifier of the parent counter value (reading) to which this property reading belongs. This is the principal join back to the counter reading itself.
• COUNTER_PROPERTY_ID — Identifier of the counter property definition that this reading instance measures or qualifies.
• PROPERTY_VALUE — VARCHAR2(240) holding the captured value for the property.
• VALUE_TIMESTAMP — DATE on which the property value was recorded or observed.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking who created and last modified each row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Standard Descriptive Flexfield (DFF) columns available for client-specific extension.
• MIGRATED_FLAG — Indicator used to mark rows introduced through data migration or conversion.

Common Use Cases and Queries

Typical scenarios include retrieving all property values for a given counter reading, reporting on properties recorded during a specific period, and auditing migrated versus organically captured data.

• Join property readings to their counter values: SELECT p.COUNTER_PROP_VALUE_ID, p.COUNTER_PROPERTY_ID, p.PROPERTY_VALUE, p.VALUE_TIMESTAMP FROM CSI.CSI_CTR_PROPERTY_READINGS p WHERE p.COUNTER_VALUE_ID = :counter_value_id;
• Time-bounded reporting: filter on VALUE_TIMESTAMP BETWEEN :from_date AND :to_date and group by COUNTER_PROPERTY_ID to trend a given property over time.
• Migration audit: SELECT COUNT(*) FROM CSI.CSI_CTR_PROPERTY_READINGS WHERE MIGRATED_FLAG = 'Y';
• DFF extension queries: select ATTRIBUTE_CATEGORY, ATTRIBUTE1..ATTRIBUTE15 when client-specific attributes have been enabled for this entity.
• Concurrency-safe updates: include OBJECT_VERSION_NUMBER in the WHERE clause of any UPDATE to enforce optimistic locking.

Related Objects

Although the metadata documents no enforced foreign keys, the following objects are the most significant for joining and integration:

• CSI.CSI_CTR_PROPERTY_READINGS_U01 / CSI_CTR_PROPERTY_READINGS_PK — Unique index and primary key on COUNTER_PROP_VALUE_ID.
• Counter value table (referenced by COUNTER_VALUE_ID) — Join key back to the parent counter reading.
• Counter property definition table (referenced by COUNTER_PROPERTY_ID) — Provides property name, data type, and unit metadata.
• Counter instance tables — Define which properties are applicable to a given counter instance.
• CSI_CTR_PROPERTY_READINGS history / audit equivalents — Where row-level change tracking is enabled.
• PL/SQL APIs and concurrent programs in the CSI schema that insert, update, or validate counter property readings, using OBJECT_VERSION_NUMBER for concurrency control.

Because the table is classified as standalone, integrators should rely on the value columns COUNTER_VALUE_ID and COUNTER_PROPERTY_ID for logical joins rather than expecting database-enforced referential integrity.