Search Results eam_meter_reading

Overview

EAM.EAM_METER_READINGS_INTERFACE is an open interface table in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It serves as a staging area for meter reading data harvested from legacy systems, external monitoring devices, or third-party applications before that data is validated and loaded into the production EAM meter reading tables. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_INTERFACE tablespace under the EAM schema, and is registered as FND Design Data EAM.EAM_METER_READINGS_INTERFACE with a status of VALID. Its lifecycle state is active, and it is classified as a public scope object with the display name EAM_METER_READINGS_INTERFACE.

The table is categorized as an OPEN_INTERFACE for the EAM_MET_RD_INTERFACE concurrent program, and as a BUSINESS_ENTITY for EAM_METER_READING. Records are inserted by users or upstream processes, then processed by the Asset Meter Import concurrent program, which validates the staged rows and transfers them into the EAM_METER_READINGS table. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone, indicating no parent-child hub/link/satellite dependencies within the vault model; it functions as a transient staging entity rather than a durable warehouse artifact.

Key Information Stored

Although the documented schema contains 46 columns, the following are the most operationally significant. GROUP_ID is the interface process group identifier and is the only indexed column, supported by the non-unique index EAM_MRS_INTERFACE_N1 on APPS_TS_INTERFACE; groups of rows are processed together by the import program. PROCESS_STATUS and PROCESS_PHASE carry the concurrency processing state, allowing the import to track which rows are pending, validated, or errored. METER_ID is a foreign key referencing EAM_METERS and identifies the target meter, while METER_NAME provides a human-readable alternative for resolution when the surrogate identifier is unavailable.

READING_VALUE holds the numeric reading, and READING_DATE records when the reading was taken. RESET_FLAG indicates whether the meter was reset, and LIFE_TO_DATE_READING captures the cumulative lifetime value. ORGANIZATION_ID and ORGANIZATION_CODE scope the reading to an inventory organization. WIP_ENTITY_ID and WORK_ORDER_NAME associate the reading with a work order. SOURCE_CODE and SOURCE_LINE_ID identify the originating system record, while INTERFACE_ID uniquely tags each staged row. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID) provide audit and concurrent request traceability, and READING_CHANGE and DISABLE_FLAG control processing behavior. No documented unique index exists; GROUP_ID plus INTERFACE_ID are the practical business-key candidates.

Common Use Cases and Queries

The primary scenario is bulk loading legacy meter readings via SQL*Loader or an external program into EAM_METER_READINGS_INTERFACE, followed by submission of the EAM_MET_RD_INTERFACE concurrent program. Monitoring query activity focuses on process status distribution and pre-validation of foreign key integrity. A representative query counts staged rows by process status:

• SELECT PROCESS_STATUS, COUNT(*) FROM EAM.EAM_METER_READINGS_INTERFACE GROUP BY PROCESS_STATUS;
• SELECT r.GROUP_ID, r.METER_NAME, r.READING_VALUE, r.READING_DATE FROM EAM.EAM_METER_READINGS_INTERFACE r WHERE r.METER_ID IS NULL; to detect rows lacking a resolvable meter.
• SELECT r.INTERFACE_ID, m.METER_NAME FROM EAM.EAM_METER_READINGS_INTERFACE r, EAM.EAM_METERS m WHERE r.METER_ID = m.METER_ID; to validate the METER_ID foreign key before import.

Reporting use cases include reconciliation of source-system extracts against imported readings and error analysis for rejected rows identified by PROCESS_STATUS.

Related Objects

The most significant related objects include EAM.EAM_METERS, referenced through the documented foreign key METER_ID, which supplies the meter master data needed for validation. The EAM_METER_READINGS table is the target of the Asset Meter Import process and receives validated rows. The concurrent program EAM_MET_RD_INTERFACE (registered in FND concurrent program definitions) orchestrates the load. The EAM_MRS_INTERFACE_N1 index on GROUP_ID supports group-based retrieval during processing. Additional dependencies include the FND design metadata tables that register the open interface, organization master data referenced by ORGANIZATION_ID, and the WIP work order entities referenced by WIP_ENTITY_ID. Together these objects complete the end-to-end meter reading import path within EAM.