Results for “eam_meter_readings_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The EAM_METER_READINGS_V view in the APPS schema consolidates meter definitions and their associated readings for assets managed within Oracle Enterprise Asset Management (EAM). It presents a denormalized result set that combines meter master attributes from EAM_METERS, asset-to-meter assignments from EAM_ASSET_METERS, historical counter values from EAM_METER_READINGS, and asset identification details from MTL_SERIAL_NUMBERS. The view is implemented as a UNION of two branches: the first returns populated reading rows joined through an outer join to readings (EMR.METER_ID = EMR.METER_ID (+)), while the second branch synthesizes placeholder rows for meters that have no readings yet, hard-coding DISABLE_FLAG = 'N' and nulling the reading-specific columns.

In Oracle EBS 12.1.1 and 12.2.2 this object serves reporting, dashboard, and integration workloads where a flat, query-ready meter reading record is required without navigating the underlying normalized tables. Because it exposes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the full ATTRIBUTE1–ATTRIBUTE15 DFF set, it is also commonly used for extract and interface programs that must preserve descriptive flexfield context.

Underlying Base Objects

The view text joins four primary objects. EAM_METERS supplies meter name, unit of measure, and effective date ranges. EAM_ASSET_METERS links meters to maintenance objects and organizations, and carries the DISABLE_FLAG column referenced in the user's search. EAM_METER_READINGS holds the actual reading history, including CURRENT_READING, CURRENT_READING_DATE, LIFE_TO_DATE_READING, WIP_ENTITY_ID, and the readings-level RESET_FLAG. MTL_SERIAL_NUMBERS resolves the maintained asset through MSN.GEN_OBJECT_ID = EAM.MAINTENANCE_OBJECT_ID, yielding ASSET_GROUP_ID (inventory item) and ASSET_NUMBER (serial number). The ETRM 12.2.2 metadata additionally documents referenced synonyms CSI_COUNTER_READINGS and CSI_TRANSACTIONS, and the view EAM_COUNTERS_V, reflecting the Install Base integration path through which EAM meters and counters are synchronized.

Key Columns

• METER_ID, METER_NAME, METER_UOM — meter identity and unit of measure.
• METER_READING_ID, CURRENT_READING, CURRENT_READING_DATE — the specific reading transaction; null for meters with no readings.
• LIFE_TO_DATE_READING — cumulative reading value since meter inception.
• RESET_FLAG — draws from EMR.RESET_FLAG in the first branch; the second branch supplies a null TO_CHAR(NULL) placeholder.
• DISABLE_FLAG — indicator of whether the asset-meter association is disabled; hard-coded to 'N' in the no-reading branch. This is the column most relevant to the user's disable_flag query.
• ORGANIZATION_ID, ASSET_GROUP_ID, ASSET_NUMBER — organizational and asset identification.
• VALUE_CHANGE_DIR — direction in which meter values are expected to move (ascending/descending).
• MAINTENANCE_OBJECT_TYPE, MAINTENANCE_OBJECT_ID — the maintained object reference underlying the meter assignment.
• WHO and DFF columns — audit and descriptive flexfield attributes from the reading record.

Common Use Cases and Queries

Typical scenarios include listing active meters per asset, retrieving the latest reading for a meter, and filtering out disabled meter assignments.

• Meters with active (non-disabled) assignments: SELECT METER_ID, METER_NAME, ASSET_NUMBER, DISABLE_FLAG FROM APPS.EAM_METER_READINGS_V WHERE DISABLE_FLAG = 'N';
• Latest reading per meter: SELECT METER_ID, METER_NAME, CURRENT_READING, CURRENT_READING_DATE FROM APPS.EAM_METER_READINGS_V WHERE METER_READING_ID IS NOT NULL ORDER BY CURRENT_READING_DATE DESC;
• Meters with no readings yet (returned by the second UNION branch): SELECT METER_ID, METER_NAME, ASSET_NUMBER FROM APPS.EAM_METER_READINGS_V WHERE METER_READING_ID IS NULL;

Because the view performs a multi-table join with an outer join and a UNION, queries should filter on indexed columns such as ORGANIZATION_ID, METER_ID, or ASSET_NUMBER to avoid full scans. Consumers requiring only meter definition data should prefer EAM_METERS directly, while those needing reading history benefit from the consolidated projection this view provides.