Results for “eam_meter_readings_interface_v”

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

Overview

The EAM_METER_READINGS_INTERFACE_V view is a reporting and integration construct within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Owned by the APPS schema and documented as VALID in both release 12.1.1 and 12.2.2, it exposes meter and meter reading interface details in a denormalized, user-friendly form. The view resolves raw foreign-key identifiers held on the interface staging table — such as lookup codes, organization identifiers, work order references, and user IDs — into their human-readable meanings, making it suitable for diagnostics, reconciliation, and custom reporting on meter reading imports.

Rather than presenting raw interface rows, the view joins the underlying staging table to lookups, organization definitions, work-in-process entities, meters, and FND users, and filters records to those where both PROCESS_PHASE and PROCESS_STATUS are populated. This makes it a dependable source for tracking the lifecycle of inbound meter reading records as they progress through interface processing.

Underlying Base Objects

Per the documented 12.2.2 view metadata, EAM_METER_READINGS_INTERFACE_V is defined over the following referenced objects:

• EAM_METERS (SYNONYM) — supplies the resolved meter name via NVL against the interface-staged meter name.
• EAM_METER_READINGS_INTERFACE (SYNONYM) — the primary staging table holding the meter reading interface rows (aliased MRI).
• FND_USER (SYNONYM) — resolved twice to translate CREATED_BY and LAST_UPDATED_BY identifiers into user names.
• MFG_LOOKUPS (VIEW) — resolves PROCESS_PHASE and PROCESS_STATUS codes into meanings using lookup types WIP_ML_PROCESS_PHASE and WIP_PROCESS_STATUS.
• ORG_ORGANIZATION_DEFINITIONS (VIEW) — provides the organization code.
• WIP_ENTITIES (SYNONYM) — supplies the work order name associated with the reading.
• HR_GENERAL and HR_SECURITY (PACKAGES) — leveraged by the organization definitions view for organization access resolution.

All joins to the descriptive tables are outer joins (denoted by the (+) operator), ensuring that interface rows are not lost when reference data is missing.

Key Columns

• INTERFACE_ID, GROUP_ID — primary staging identifiers for each interface record and its processing batch.
• PROCESS_PHASE / PROCESS_PHASE_MEANING — the numeric phase code and its decoded meaning.
• PROCESS_STATUS / PROCESS_STATUS_MEANING — the numeric status code and its decoded meaning.
• METER_ID, METER_NAME — the meter being reported; METER_NAME falls back to the interface value when no master record is linked.
• ORGANIZATION_ID, ORGANIZATION_CODE — the owning organization, resolved through ORG_ORGANIZATION_DEFINITIONS with a decode fallback.
• WIP_ENTITY_ID, WORK_ORDER_NAME — the associated work order where applicable.
• READING_VALUE, READING_DATE, READING_CHANGE — the measured reading, its effective date, and the delta applied to the meter.
• RESET_FLAG, LIFE_TO_DATE_READING, DISABLE_FLAG — control flags governing reset behavior, cumulative life-to-date accumulation, and meter disabling.
• SOURCE_CODE, SOURCE_LINE_ID — the originating source of the reading for traceability.
• CREATED_BY_NAME, LAST_UPDATED_BY_NAME, CREATION_DATE, LAST_UPDATE_DATE — auditing information joined to FND_USER.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — the concurrent request and program that processed the row.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard DFF extension columns.

Common Use Cases and Queries

Typical use cases include reconciling imported meter readings, diagnosing failed or pending interface rows, auditing who loaded readings and when, and validating reading deltas. A representative query filtering on processed rows follows:

• SELECT interface_id, group_id, meter_name, organization_code, reading_value, reading_change, process_status_meaning FROM eam_meter_readings_interface_v WHERE process_status_meaning = 'PROCESSED';
• SELECT meter_id, meter_name, reading_date, life_to_date_reading FROM eam_meter_readings_interface_v WHERE reading_change IS NOT NULL ORDER BY reading_date DESC;

Because the view already decodes lookups and users, it is well suited to ad-hoc reporting and to feeding downstream reconciliation reports without additional joins.