Search Results csi_ctr_estimated_readings_u01




Overview

CSI.CSI_CTR_ESTIMATED_READINGS is a transactional table in the Oracle Enterprise Asset Management (eAM) and Enterprise Asset Management counter subsystem, owned by the CSI (Customer Support Intelligence / Installed Base) schema. It stores estimated meter readings associated with counters, capturing the estimated consumption or usage when an actual physical reading is not available at the time of processing. In Oracle EBS 12.1.1 and 12.2.2, this table is central to counter-based billing, preventive maintenance scheduling, and service contract usage tracking, where continuous consumption data must be inferred between two known readings.

Each row represents a single estimated reading event tied to a counter and an estimation process. The table persists period boundaries, average calculation windows, reading counts, estimated usage, and the estimation date, allowing downstream processes to reconcile estimates against actuals during the next validation cycle. The record is fully enabled for Descriptive Flexfields (ATTRIBUTE1 through ATTRIBUTE15) and standard WHO audit columns, making it extensible and auditable in a multi-org environment. From a Data Vault modeling perspective, this object is heuristically classified as a standalone structure, with the surrogate key ESTIMATED_READING_ID acting as the natural hub anchor and the transactional attributes forming a satellite. Modeling it as a hub-linked satellite is a reasonable suggestion, though the metadata does not define an explicit link to a parent hub.

Key Information Stored

Common Use Cases and Queries

Typical scenarios include reconciliation of estimated versus actual readings, usage reporting for billing, and auditing counter consumption windows. A representative query retrieves the latest estimates per counter:

  • Join CSI_CTR_ESTIMATED_READINGS to the counter definition table on COUNTER_ID to report estimated usage by asset.
  • Filter by VALUE_TIMESTAMP and PERIOD_START_DATE / PERIOD_END_DATE to reconcile periods.
  • Aggregate ESTIMATED_USAGE grouped by COUNTER_ID for billing extracts.
  • Isolate MIGRATED_FLAG = 'Y' rows for migration validation.
  • Apply SECURITY_GROUP_ID predicates to enforce row-level data security.

Related Objects