Results for “eam_pm_activitygroup_v”

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

Overview

APPS.EAM_PM_ACTIVITYGROUP_V is a reporting and integration view in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its stated purpose, per the ETRM documentation, is to "display details of Preventive Maintenance Schedule Activities." The view consolidates preventive maintenance (PM) scheduling information with asset activity definitions so that a single query can return the set of activities associated with a given PM schedule, including the interval configuration and the tolerance applied to each activity.

The object is defined with Status: VALID and is owned by the APPS schema. It is documented under ETRM 12.2.2 and applies equally to the 12.1.1 code line. Because it is a view rather than a table, it exposes no independent storage; it is a query surface that joins the PM scheduling and asset activity entities. This makes it suitable for read-only reporting, extract logic, and integration touchpoints where consumers require PM activity group detail without reconstructing the multi-table join themselves.

Note that the view does not provide every PM attribute — it is scoped to activity grouping and its scheduling characteristics. Fields such as DAY_TOLERANCE are surfaced here directly, which is a key reason the view is relevant to searches involving scheduling tolerance configuration.

Underlying Base Objects

The documented base objects referenced by this view are:

• EAM_PM_ACTIVITIES (SYNONYM) — aliased as EPA; the driving table supplying PM schedule activity rows.
• EAM_PM_SCHEDULINGS (SYNONYM) — aliased as PM; supplies the PM schedule definition.
• MTL_EAM_ASSET_ACTIVITIES (SYNONYM) — aliased as EAA; supplies asset activity and maintenance object detail.
• MTL_SYSTEM_ITEMS_KFV (SYNONYM) — the key flexfield value view used to resolve the item's concatenated segments.

The join logic runs from EAM_PM_ACTIVITIES to MTL_EAM_ASSET_ACTIVITIES on ACTIVITY_ASSOCIATION_ID, and from EAM_PM_ACTIVITIES to EAM_PM_SCHEDULINGS on PM_SCHEDULE_ID, with a further constraint linking EAA.MAINTENANCE_OBJECT_ID to PM.MAINTENANCE_OBJECT_ID. The CONCATENATED_SEGMENTS value is resolved through a scalar subquery against MTL_SYSTEM_ITEMS_KFV, filtered by INVENTORY_ITEM_ID and restricted to ROWNUM = 1. Because the view is defined over synonyms owned by APPS, it must be queried in the APPS schema context or through a granted synonym.

Key Columns

• ROW_ID — the ROWID of the underlying EAM_PM_ACTIVITIES row, useful as a surrogate identifier.
• PM_SCHEDULE_ID — identifies the PM schedule to which the activity group belongs.
• ACTIVITY_ASSOCIATION_ID — the association key linking the PM activity to the asset activity record.
• CONCATENATED_SEGMENTS — the item's concatenated flexfield segments, resolved from MTL_SYSTEM_ITEMS_KFV; may be null when no item match exists.
• MAINTENANCE_OBJECT_ID and MAINTENANCE_OBJECT_TYPE — the maintenance object (asset) that the PM applies to.
• INTERVAL_MULTIPLE — the multiplier applied to the PM interval for the activity.
• ALLOW_REPEAT_IN_CYCLE — flag indicating whether the activity may repeat within a PM cycle.
• DAY_TOLERANCE — the day tolerance associated with the PM activity; central to scheduling-window and compliance reporting.
• ASSET_ACTIVITY_ID — identifier of the asset activity being scheduled.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

The view supports PM configuration reporting, exposure of day-tolerance settings, and integration extracts requiring activity group detail. A typical query lists all activity groups for a PM schedule:

• SELECT pm_schedule_id, activity_association_id, concatenated_segments, maintenance_object_id, interval_multiple, day_tolerance FROM apps.eam_pm_activitygroup_v WHERE pm_schedule_id = :p_schedule_id;
• SELECT activity_association_id, asset_activity_id, day_tolerance, allow_repeat_in_cycle FROM apps.eam_pm_activitygroup_v WHERE maintenance_object_id = :p_object_id;
• SELECT pm_schedule_id, COUNT(*) FROM apps.eam_pm_activitygroup_v GROUP BY pm_schedule_id;

Because the view is a consolidation join, filtering by PM_SCHEDULE_ID or MAINTENANCE_OBJECT_ID is recommended to limit result sets. Consumers requiring additional PM attributes beyond those exposed should join back to the base EAM tables.