Search Results estimated_meter_reading




Overview
Explore in AI Chat

Overview

The APPS.CSI_CTR_ESTIMATED_READINGS_V view exposes estimated meter reading data collected and interpolated by Oracle Enterprise Asset Management (eAM) and the Enterprise Tracking and Runtime Management (ETRM) counter infrastructure. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, the object serves as a simplified, read-only projection of the underlying CSI_CTR_ESTIMATED_READINGS table, presenting one row per estimated reading record associated with a counter. Its central purpose is to make estimated consumption values — that is, meter readings that have been derived rather than physically captured — available for reporting, analytics, and downstream integration without exposing the caller to the full physical table.

The view is particularly relevant when actual readings are missing for a billing or usage period. The presence of columns such as ESTIMATED_METER_READING, ESTIMATED_USAGE, and AVG_CALCULATION_START_DATE indicates that the object supports substitution of a statistically derived value where a true reading is absent. Because the view is owned by APPS and defined as a straightforward column projection, it inherits the security, grants, and synonym conventions of standard Oracle EBS seeded views.

Underlying Base Objects

According to the ETRM metadata, the view is defined over a single referenced base object, CSI_CTR_ESTIMATED_READINGS, which is exposed to the view owner through a synonym. The view text is a direct SELECT of every column in the base table, with each column aliased to its own name. The definition carries no joins, filters, WHERE clauses, or aggregations, meaning that a row in the view corresponds exactly to a row in the base table.

Because the view is a one-to-one column mapping of the base table, it does not introduce additional derivation logic of its own; all estimation logic is performed when rows are inserted into CSI_CTR_ESTIMATED_READINGS. The MIGRATED_FLAG column included in the projection confirms that the base table supports records migrated from legacy sources, and the view preserves that indicator for consumers.

Key Columns

  • ESTIMATED_READING_ID — Primary identifier for the estimated reading record.
  • COUNTER_ID — The counter (meter) to which the estimated reading belongs; the primary join key to counter and asset master data.
  • ESTIMATION_ID — Links the reading back to the estimation run or process that generated it.
  • VALUE_TIMESTAMP — The effective date/time of the estimated value.
  • ESTIMATED_METER_READING — The derived meter reading value used when an actual reading is unavailable; this is the column most directly associated with the user search term estimated_meter_reading.
  • ESTIMATED_USAGE — The consumption derived from the estimation for the associated period.
  • NUM_OF_READINGS — Count of readings used in the estimation calculation.
  • PERIOD_START_DATE / PERIOD_END_DATE — Bounds of the interval the estimated reading covers.
  • AVG_CALCULATION_START_DATE — Lower bound of the window over which averages were computed to derive the estimate.
  • SECURITY_GROUP_ID — Multi-tenant security grouping, used for row-level access control.
  • MIGRATED_FLAG — Indicates whether the record originated from a migration.
  • Standard audit and descriptive flexfield columns (LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15) — Provide Who columns, optimistic locking, and extensibility.

Common Use Cases and Queries

Typical scenarios include reconciling estimated versus actual readings, reporting estimated usage by counter for a period, and feeding estimated consumption into billing or KPI dashboards. A representative query joining the view to counter master data:

SELECT ec.counter_id,
       ec.value_timestamp,
       ec.estimated_meter_reading,
       ec.estimated_usage,
       ec.period_start_date,
       ec.period_end_date
FROM   apps.csi_ctr_estimated_readings_v ec
WHERE  ec.counter_id = :p_counter_id
AND    ec.value_timestamp BETWEEN :p_from AND :p_to
ORDER  BY ec.value_timestamp;

To isolate migrated records or to inspect estimation provenance, filter on MIGRATED_FLAG or aggregate by ESTIMATION_ID. Because the view exposes no joins, applications requiring asset or item context must join to the counter entity tables on COUNTER_ID.