Results for “eam_pm_last_service_v”

18 results




Overview
Explore in AI Chat

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

Overview

The EAM_PM_LAST_SERVICE_V view is a reporting object within the Oracle E-Business Suite Enterprise Asset Management (EAM) module, owned by the APPS schema and documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to expose "last service information" for preventive maintenance (PM) activities associated with assets and their meters. In practice, the view answers the operational question implied by the search term "last_service_reading": for a given PM activity association and meter, what was the most recent meter reading recorded at the time that service was performed?

Because PM scheduling in EAM is frequently driven by meter-based thresholds (for example, service every 250 operating hours), the last service reading is a critical input for determining when the next service is due. This view therefore serves as a lightweight, query-ready projection that joins asset/meter activity definitions to their corresponding last-service snapshots, avoiding the need for ad hoc correlation between the asset activity view and the last service table in custom reports, dashboards, or integration extracts.

Underlying Base Objects

The view text is defined as an outer join between two objects:

The join condition is EPAAV.METER_ID = EPLS.METER_ID(+) and EPAAV.ACTIVITY_ASSOCIATION_ID = EPLS.ACTIVITY_ASSOCIATION_ID(+). Both predicates use the Oracle outer-join operator (+) on the EPLS side, meaning the view preserves every row from the asset activity view even where no last service record yet exists. In those cases LAST_SERVICE_READING is returned as NULL. This design is important: it allows listings of all PM asset/meter activities to display uniformly, with the last reading populated only once servicing has actually been recorded.

Key Columns

  • ACTIVITY_ASSOCIATION_ID — Identifier linking the PM activity to its asset/meter association; part of the composite join key.
  • LAST_SERVICE_READING — The most recent meter reading captured for the service; NULL when no service has been recorded. This is the column most directly associated with the "last_service_reading" search.
  • ASSET_NUMBER — The asset to which the PM activity and meter belong.
  • METER_ID / METER_NAME / METER_UOM — Identity, descriptive name, and unit of measure of the associated meter, providing context for interpreting the reading.
  • VALUE_CHANGE_DIR — Direction of meter value change (typically ascending/descending), relevant to threshold logic.
  • DESCRIPTION — Descriptive text for the activity association.
  • USAGE_RATE — Rate of meter usage, useful for projecting when the next threshold will be reached.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns carried through from the asset activity view, supporting audit and incremental extract patterns.

Common Use Cases and Queries

Typical scenarios include PM due-date projection, fleet/asset servicing dashboards, and integration extracts into maintenance planning tools. A representative query lists assets whose last service reading is approaching a threshold:

  • Detail lookup by asset: SELECT asset_number, meter_name, meter_uom, last_service_reading FROM apps.eam_pm_last_service_v WHERE asset_number = :p_asset;
  • Identify activities lacking service history: SELECT activity_association_id, asset_number, meter_name FROM apps.eam_pm_last_service_v WHERE last_service_reading IS NULL;
  • Meter-based due analysis: SELECT asset_number, meter_name, last_service_reading, usage_rate FROM apps.eam_pm_last_service_v ORDER BY asset_number, meter_name;

Because the view is read-only and defined over an outer join, it is safe for query-only integration usage. Standard EBS security applies, and the object should be accessed through the APPS schema with the appropriate MO: Operating Unit and EAM responsibility context.