Search Results csi_ctr_read_prop_interface

Overview

CSI_CTR_READ_PROP_INTERFACE is a transient staging table within the Oracle E-Business Suite Install Base (CSI) module. It is designed to hold counter reading property interface data — the property-level attributes that accompany counter readings as they are loaded into, or exported from, the Install Base counter reading framework. Counter readings are the recurring measurement values recorded against a counter (for example, meter readings on an asset), and each reading may carry one or more named property values. This table serves as the inbound interface staging area for those property values before they are validated and transferred to the permanent counter reading property tables.

Because the table functions as an interface buffer rather than a master entity, the ETRM metadata classifies it heuristically as standalone under Data Vault modeling conventions. This classification is a modeling suggestion rather than a physical constraint: the table is not a normalized hub, link, or satellite, but a staging structure that carries both the counter reading reference and the property value attributes within a single, flattened row. Its lifecycle is transactional — rows are inserted by interface programs and subsequently processed, migrated, or purged.

Key Information Stored

The 32 documented columns fall into three logical groups: identity, reference, and audit.

• COUNTER_READ_PROP_INT_ID — the surrogate primary key for the row, uniquely identifying each interface record.
• COUNTER_INTERFACE_ID — foreign key to CSI_CTR_READINGS_INTERFACE, linking the property row to its parent counter reading in the same interface batch.
• COUNTER_PROP_VALUE_ID — a business-key candidate, enforced by unique index CSI_CTR_READ_PROP_INTFACE_U01, identifying the underlying property value record.
• COUNTER_VALUE_ID and COUNTER_PROPERTY_ID — reference the counter reading value and the counter property definition, establishing which reading and which named property the row pertains to.
• PROPERTY_VALUE — the actual property value being loaded, the core payload of the row.
• VALUE_TIMESTAMP — the effective timestamp associated with the property value.
• PARALLEL_WORKER_ID — used by concurrent processing to track which worker thread claimed or processed the row.
• ERROR_TEXT — captures validation failures encountered during processing, enabling error reporting and reprocessing.
• OBJECT_VERSION_NUMBER — optimistic locking control standard to EBS tables using the ORM framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-columns for audit and concurrency tracking.
• MIGRATED_FLAG — indicates whether the row has been migrated to the permanent counter reading property tables.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for client-extensible data.

Common Use Cases and Queries

Typical scenarios center on monitoring interface throughput, reconciling unprocessed rows, and diagnosing load failures. A common query joins the interface property table to its parent reading interface to inspect error state:

• Validation backlog: SELECT counter_interface_id, COUNT(*) FROM csi_ctr_read_prop_interface WHERE error_text IS NOT NULL GROUP BY counter_interface_id; — surfaces parent readings with property-level errors.
• Migration status: SELECT migrated_flag, COUNT(*) FROM csi_ctr_read_prop_interface GROUP BY migrated_flag; — shows how many property rows remain to be transferred to permanent tables.
• Parallel worker balancing: grouping by PARALLEL_WORKER_ID reveals processing distribution across concurrent workers.
• Payload inspection: querying PROPERTY_VALUE with VALUE_TIMESTAMP and COUNTER_PROPERTY_ID for a given COUNTER_VALUE_ID confirms the property values received in the batch.

Reporting use cases include interface scorecards (success/error ratios), reconciliation reports comparing interface counts to permanent counter reading property counts, and audit extracts of the DFF attributes.

Related Objects

• CSI_CTR_READINGS_INTERFACE — the parent interface table, joined via COUNTER_INTERFACE_ID. This is the primary dependency for batch-level processing.
• Permanent counter reading property tables (CSI_CTR_READ_PROPERTIES family) — the destination of successfully processed rows, referenced through COUNTER_PROP_VALUE_ID and COUNTER_VALUE_ID.
• CSI_COUNTER_PROPERTIES — defines the property metadata referenced by COUNTER_PROPERTY_ID.
• CSI_CTR_READING_VALUES / counter value entities — referenced by COUNTER_VALUE_ID, providing the reading context.
• Install Base concurrent programs and APIs — the counter reading import and processing programs that populate, validate, and migrate rows from this interface.

Because the table is a staging buffer, its related objects are predominantly the parent interface table, the downstream permanent tables, and the concurrent processes that manage movement between them.