Search Results csi_ctr_readings_interface_u01

Overview

CSI.CSI_CTR_READINGS_INTERFACE is the open interface table for the Counter Readings Open Interface in Oracle E-Business Suite, owned by the CSI (Installed Base / Counters) product schema. It serves as the staging area into which external sources load counter readings before they are validated and processed into the base counter reading tables by the Counter Readings API. Readings may originate from multiple sources, each identified by the SOURCE_TRANSACTION_TYPE_ID column, and the interface accommodates different reading types including standard readings, resets, and adjustments.

The table is classified as a PUBLIC, ACTIVE business entity (CSI_COUNTER) and resides in the APPS_TS_TX_DATA tablespace. Processing logic reads rows in ascending order of VALUE_TIMESTAMP and COUNTER_ID, filtered by the input parameters BATCH_NAME and SOURCE_TRANSACTION_DATE, then invokes the Counter Readings API for further processing. From a Data Vault modeling perspective, the heuristic mined from its foreign key structure classifies this table as standalone; it is therefore best modelled as a staging or interface object rather than as a true hub, link, or satellite, since it captures an inbound transactional feed (readings) rather than a core business entity or relationship.

Key Information Stored

The primary key is COUNTER_INTERFACE_ID, the internally generated surrogate key, and it is also the sole unique index business-key candidate (CSI_CTR_READINGS_INTERFACE_U01). Because the surrogate key is the only unique constraint, the table may accept multiple interface rows referencing the same counter and timestamp, supporting batch and parallel loads.

• COUNTER_INTERFACE_ID – surrogate primary key, internally generated.
• BATCH_NAME and SOURCE_TRANSACTION_DATE – the two processing parameters that drive which rows the concurrent program picks up.
• COUNTER_ID and COUNTER_NAME – the counter to which the reading belongs.
• VALUE_TIMESTAMP – capture date of the counter reading; governs processing order alongside COUNTER_ID.
• COUNTER_READING, NET_READING, LIFE_TO_DATE_READING – the actual reading, net, and life-to-date values.
• RESET_MODE, RESET_REASON, RESET_COUNTER_READING – reset semantics for counters that roll back.
• ADJUSTMENT_TYPE and ADJUSTMENT_READING – adjustment classification and value.
• AUTOMATIC_ROLLOVER_FLAG and INCLUDE_TARGET_RESETS – rollover control flags.
• SOURCE_TRANSACTION_TYPE_ID, SOURCE_TRANSACTION_ID, SOURCE_CODE, SOURCE_LINE_ID – origin identification of the incoming reading.
• PROCESS_STATUS and ERROR_TEXT – processing outcome and rejection messages.
• PARALLEL_WORKER_ID – enables parallel worker partitioning of a batch.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS for multi-org/security enforcement.

The table also carries a full WHO audit set (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and 30 descriptive ATTRIBUTE columns, all documented in the 65-column physical schema for 12.2.2.

Common Use Cases and Queries

Typical usage involves loading readings from meter or asset systems, then running the Counter Readings Open Interface concurrent program to process them. Common queries include checking unprocessed rows, isolating errors, and reconciling readings against source transactions.

• Pending load inspection: SELECT counter_interface_id, counter_id, value_timestamp, counter_reading FROM csi_ctr_readings_interface WHERE process_status IS NULL AND batch_name = :p_batch;
• Error triage: SELECT counter_interface_id, error_text FROM csi_ctr_readings_interface WHERE process_status = 'ERROR';
• Duplicate detection by counter and timestamp: SELECT counter_id, value_timestamp, COUNT(*) FROM csi_ctr_readings_interface GROUP BY counter_id, value_timestamp HAVING COUNT(*) > 1;
• Source reconciliation: filter by SOURCE_TRANSACTION_TYPE_ID, SOURCE_CODE, and SOURCE_TRANSACTION_DATE.
• Reporting on reset vs. standard readings via RESET_MODE and ADJUSTMENT_TYPE.

Related Objects

• CSI.CSI_CTR_READ_PROP_INTERFACE – child interface table referencing this parent via COUNTER_INTERFACE_ID, storing reading properties to accompany each reading row.
• FND_SECURITY_GROUPS – referenced through SECURITY_GROUP_ID for security group enforcement.
• Counter Readings API – the validation and processing entry point invoked after staging.
• CSI_COUNTERS – base counter definition table, related through COUNTER_ID and COUNTER_NAME.
• CSI counter values / readings base tables – the post-processing targets of successful interface rows (via COUNTER_VALUE_ID and SOURCE_COUNTER_VALUE_ID).
• Counter Readings Open Interface concurrent program – drives batch selection by BATCH_NAME and SOURCE_TRANSACTION_DATE.