Search Results csi_ctr_readings_interface_pk

Overview

CSI_CTR_READINGS_INTERFACE is a staging and inbound-processing table within the CSI (Install Base) product family of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to hold counter readings interface data — that is, the denormalized, transient representation of meter, counter, and usage readings that arrive from external sources before Oracle validates, transforms, and applies them to the production counter value structures in the Install Base repository.

The table is owned by the CSI schema and is populated exclusively through programmatic interfaces: concurrent programs, the public Install Base counter reading APIs, or direct SQL loads performed by integration and data-migration developers. It is not an end-user maintenance table. Records pass through a status lifecycle, advancing from an unprocessed state to either successful application or a logged error, at which point the offending rows remain available for correction and reprocessing. This design isolates inbound volume from the production counter tables and makes the interface independently restartable.

Mining of the foreign-key structure classifies the object heuristically as standalone, with no parent link into a core business entity hub — a modeling suggestion that reflects its role as a self-contained staging area rather than a persistent dimension or transactional fact. Row identity is anchored by the surrogate primary key CSI_CTR_READINGS_INTERFACE_PK on COUNTER_INTERFACE_ID, which is also enforced by the unique index CSI_CTR_READINGS_INTERFACE_U01.

Key Information Stored

• COUNTER_INTERFACE_ID — surrogate primary key and the business-key candidate enforced by the unique index; the value propagated to child interface tables.
• BATCH_NAME and PARALLEL_WORKER_ID — the inbound batch identifier and worker assignment used to partition and parallel-process large loads.
• COUNTER_ID, COUNTER_NAME, and COUNTER_VALUE_ID — the target counter in the Install Base repository and the counter value row being created or updated.
• COUNTER_READING, VALUE_TIMESTAMP, and SOURCE_TRANSACTION_DATE — the incoming measurement, its effective date, and the originating transaction date.
• RESET_MODE, RESET_REASON, RESET_COUNTER_READING, and AUTOMATIC_ROLLOVER_FLAG — control attributes governing rollover, reset, and wrap-around behavior for the submitted reading.
• ADJUSTMENT_TYPE, ADJUSTMENT_READING, NET_READING, and LIFE_TO_DATE_READING — derived quantities computed during validation.
• PROCESS_STATUS and ERROR_TEXT — the processing state and the diagnostic message retained when a row fails.
• SOURCE_CODE, SOURCE_TRANSACTION_TYPE_ID, SOURCE_TRANSACTION_ID, SOURCE_LINE_ID, and SOURCE_COUNTER_VALUE_ID — lineage back to the originating application document.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-tenant data isolation.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and ATTRIBUTE1 through ATTRIBUTE30 — standard who-columns and the DFF flexfield segment.

Common Use Cases and Queries

Typical scenarios include bulk migration of historical meter readings, scheduled polling of telemetry feeds, and integration from third-party service-management systems into Install Base counters. Operational monitoring focuses on the backlog and failure profile of the interface.

• Backlog by batch: SELECT BATCH_NAME, PROCESS_STATUS, COUNT(*) FROM CSI.CSI_CTR_READINGS_INTERFACE GROUP BY BATCH_NAME, PROCESS_STATUS;
• Error triage: SELECT COUNTER_INTERFACE_ID, COUNTER_ID, COUNTER_READING, ERROR_TEXT FROM CSI.CSI_CTR_READINGS_INTERFACE WHERE PROCESS_STATUS = 'ERROR';
• Lineage reconciliation joining on SOURCE_TRANSACTION_ID and SOURCE_COUNTER_VALUE_ID to confirm which submitted readings reached production.
• Security-scoped reporting filtered by SECURITY_GROUP_ID in multi-org deployments.

Related Objects

• CSI_CTR_READ_PROP_INTERFACE — child interface table referencing COUNTER_INTERFACE_ID; carries per-reading property and attribute detail for the same inbound record.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID, supplying the security-group definition used for row-level access control.
• CSI_COUNTER_VALUES — the production counter value table populated once interface rows are validated and applied.
• CSI_COUNTERS — the counter definition table referenced by COUNTER_ID and COUNTER_NAME.
• Install Base counter reading public APIs and the associated concurrent programs — the supported mechanisms for loading and processing this interface.