Results for “value_change_dir”

49 results




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

Overview

The APPS.EAM_PM_ASSET_ACTIVITY_V view is a reporting and integration object within the Enterprise Asset Management (EAM) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of asset meters that are eligible for use in preventive maintenance (PM) scheduling activities, effectively restricting the result set to meter-to-maintenance-object associations that have been explicitly flagged for scheduling use. The view consolidates meter definition attributes from the asset meter layer with activity association identifiers from the EAM activities table, providing a denormalized, query-ready projection that application logic and custom reporting can consume without having to join the base objects directly.

Because the view enforces business filtering rules at the database level — specifically the USED_IN_SCHEDULING = 'Y' predicate and date-effectivity checks — it acts as the canonical source for determining which meters on a given maintenance object are currently valid for driving PM schedules. This makes it valuable to both standard EAM PM functionality and to downstream integrations such as interfaces that need to synchronize scheduling-relevant meters.

Underlying Base Objects

The view is defined over two referenced objects, as documented in the ETRM metadata for 12.2.2:

The join is an equi-join on MAINTENANCE_OBJECT_ID, meaning a meter is surfaced only when it shares the same maintenance object context as the activity association. The synonym MTL_EAM_ASSET_ACTIVITIES resolves to the underlying base table (typically BOM_MTL_EAM_ASSET_ACTIVITIES or its EAM equivalent), which is where the scheduling flag and effectivity windows physically reside.

Key Columns

The view exposes the following documented columns:

Note that the ETRM column listing also references USAGE_RATE; the view text projects USER_DEFINED_RATE, so consumers should verify which of these appears in their specific patch level.

Common Use Cases and Queries

Typical uses include validating which meters are scheduling-enabled for a PM program, reporting on effectivity, and feeding meter data into PM forecast calculations. A representative query:

  • List all scheduling-enabled meters for a given asset: SELECT ASSET_NUMBER, METER_NAME, METER_UOM, VALUE_CHANGE_DIR FROM EAM_PM_ASSET_ACTIVITY_V WHERE ASSET_NUMBER = :asset_number;
  • Audit recent association changes: SELECT ACTIVITY_ASSOCIATION_ID, METER_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM EAM_PM_ASSET_ACTIVITY_V ORDER BY LAST_UPDATE_DATE DESC;
  • Join to PM schedule definitions to reconcile which meters currently drive each PM routine.

Because the view already applies effectivity and the USED_IN_SCHEDULING filter, callers should not re-apply those predicates unless they intend to widen the result set beyond the documented semantics.