Search Results eam_asset_meters




Overview
Explore in AI Chat

Overview

The EAM_ASSET_METERS table is a core Enterprise Asset Management (EAM) object within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It defines the association between a maintenance asset and the meters that measure its usage, condition, or performance. Each row effectively records that a particular meter is assigned to a particular asset (or asset group) within a given organization. This association is what allows Oracle EAM to capture meter readings against assets, drive preventive maintenance scheduling, and trigger work orders when meter thresholds are reached.

The table resides in the EAM schema and contains 30 documented columns. Based on the foreign key structure — references to EAM_METERS, MTL_SERIAL_NUMBERS, and MTL_SYSTEM_ITEMS_B — the object behaves as an intersection or association entity. In Data Vault modeling terms, the metadata's heuristic classification is link, which suggests modeling this table as a link between asset and meter hubs, with its attribute columns carried as link satellites.

Key Information Stored

The primary business content of a row is the asset-to-meter relationship itself. The most significant columns are:

The unique business key is the combination of METER_ID with the asset identifiers (ASSET_NUMBER / ASSET_GROUP_ID) and ORGANIZATION_ID, which together prevent duplicate meter assignments. METER_ID alone is not a surrogate primary key; the table is keyed by the composite association, consistent with its link classification.

Common Use Cases and Queries

Typical scenarios include reporting all meters assigned to a given asset, identifying assets that lack meter coverage, and reviewing primary failure meters for reliability analysis.

  • Meters for a specific asset: join EAM_ASSET_METERS to EAM_METERS on METER_ID filtering by ASSET_NUMBER and ORGANIZATION_ID.
  • Assets without an assigned meter: outer-join MTL_SERIAL_NUMBERS to EAM_ASSET_METERS and filter where METER_ID is null.
  • Primary failure meter listing: select rows where PRIMARY_FAILURE_METER is set, joined to asset item data via ASSET_GROUP_ID and ORGANIZATION_ID.
  • Meter reading trending: join this table to meter-reading tables through METER_ID to build usage and threshold reports.

Sample pattern:

SELECT a.asset_number, m.meter_name
FROM eam_asset_meters a, eam_meters m
WHERE a.meter_id = m.meter_id
AND a.organization_id = :org_id;

Related Objects

The following are the most significant related objects based on the documented referential relationships:

  • EAM_METERS — referenced via EAM_ASSET_METERS.METER_ID; holds meter definitions.
  • MTL_SERIAL_NUMBERS — referenced via ASSET_NUMBER; the asset instance master.
  • MTL_SYSTEM_ITEMS_B — referenced via ASSET_GROUP_ID and ORGANIZATION_ID; the asset item definition.
  • EAM_METER_READINGS — stores readings captured against meters associated here.
  • EAM_WORK_ORDERS — preventive and corrective work orders driven by meter thresholds.
  • EAM_PM_RULES — preventive maintenance rules that consume meter associations.
  • EAM_ASSET_ROUTES and EAM_ASSET_ACTIVITIES — related maintenance scheduling objects.

These objects together support the meter-driven maintenance lifecycle within Oracle Enterprise Asset Management.