Search Results csi_ctr_read_prop_intface_n01

Overview

The CSI.CSI_CTR_READ_PROP_INTERFACE table is the Open Interface staging table used by the Counter Readings Open Interface within Oracle Enterprise Business Suite (EBS) 12.1.1 and 12.2.2. It resides in the CSI (Customer Support Intelligence / Install Base) schema and holds records for counter property readings — the individual measured property values captured against a counter reading. The table functions as a child of CSI_CTR_READINGS_INTERFACE, joined through the COUNTER_INTERFACE_ID column, and is classified as a BUSINESS_ENTITY belonging to the CSI_COUNTER category. Its lifecycle status is active, it is scoped as public, and it is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. From a dimensional modeling perspective, the Data Vault classification heuristic suggests this is a standalone structure; in practice it behaves as a satellite-like staging entity carrying descriptive property values and interface error diagnostics rather than as a true hub or link.

Key Information Stored

The table contains 32 documented columns, of which the most operationally significant are listed below. The internally generated surrogate primary key is COUNTER_READ_PROP_INT_ID. A second internal key, COUNTER_INTERFACE_ID, ties each row back to its parent reading in CSI_CTR_READINGS_INTERFACE. Business-key candidates are documented through the unique index CSI_CTR_READ_PROP_INTFACE_U01 on COUNTER_PROP_VALUE_ID, with a non-unique index CSI_CTR_READ_PROP_INTFACE_N01 on COUNTER_INTERFACE_ID. Other critical columns include COUNTER_VALUE_ID and COUNTER_PROPERTY_ID, which identify the counter value and the property definition being measured; PROPERTY_VALUE (VARCHAR2 240), which holds the captured reading; VALUE_TIMESTAMP, the reading property capture date; and VALUE_TIMESTAMP-adjacent fields such as PARALLEL_WORKER_ID, which supports parallel processing of interface loads. ERROR_TEXT (VARCHAR2 240) captures interface rejection or validation messages. The MIGRATED_FLAG column indicates migration provenance. Standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER provide concurrency and audit tracking, while ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 supply the descriptive flexfield (DFF) extension framework.

Common Use Cases and Queries

The primary use case is staging, validating, and loading counter property readings into the production Install Base counter tables. Typical queries monitor the interface for failures, reconcile loaded volumes, or extract property values for reporting. For example, to identify rows pending or failed in the interface:

• SELECT COUNTER_READ_PROP_INT_ID, COUNTER_INTERFACE_ID, PROPERTY_VALUE, ERROR_TEXT FROM CSI.CSI_CTR_READ_PROP_INTERFACE WHERE ERROR_TEXT IS NOT NULL;
• To join child property readings to their parent reading for a specific counter, use COUNTER_INTERFACE_ID as the join predicate against CSI_CTR_READINGS_INTERFACE.
• To correlate a loaded property back to the source counter value and property definition, join COUNTER_VALUE_ID and COUNTER_PROPERTY_ID to the corresponding Install Base counter value and property tables.
• To analyze throughput by parallel worker, aggregate counts grouped by PARALLEL_WORKER_ID.

Because the unique index enforces uniqueness on COUNTER_PROP_VALUE_ID, duplicate insert attempts surface as constraint violations during load, making the U01 index a useful diagnostic for de-duplication logic.

Related Objects

The most significant related objects center on the confirmed foreign-key relationship between this table and its parent interface structure:

• CSI.CSI_CTR_READINGS_INTERFACE — the parent table; joined via COUNTER_INTERFACE_ID.
• Install Base counter value and counter property definition tables, referenced through COUNTER_VALUE_ID and COUNTER_PROPERTY_ID.
• The Counter Readings Open Interface concurrent program, which consumes both interface tables to import readings.
• CSI_CTR_READ_PROP_INTFACE_U01 and CSI_CTR_READ_PROP_INTFACE_N01 — supporting unique and non-unique indexes.
• Production counter reading and property tables that receive the validated records after successful import.

Together these objects form the complete counter readings interface flow, from staging property values through validation to persistence in the Install Base.