Search Results eam_pm_activities_u1

Overview

EAM.EAM_PM_ACTIVITIES is a transactional table in the Oracle Enterprise Asset Management (eAM) module of Oracle E-Business Suite, present in releases 12.1.1 and 12.2.2. It stores the individual maintenance activities that belong to a Preventive Maintenance (PM) schedule. Prior to Release 12, a PM schedule could be associated with only a single activity; from R12 onward, one PM schedule may contain multiple activities, and each of those activity associations is persisted as a row in this table. In addition to the association itself, the table holds the scheduling attributes that the PM engine uses to predict and generate maintenance work, notably the next service start date and next service end date.

The table is owned by the EAM schema, resides in the APPS_TS_TX_DATA tablespace, and is classified as VALID with FND design data registered under EAM.EAM_PM_ACTIVITIES. Based on the foreign key structure—where the table carries references to both EAM_PM_SCHEDULINGS and MTL_EAM_ASSET_ACTIVITIES—the heuristic Data Vault classification of this object is a link, suggesting a modeling role as an associative entity that resolves the many-to-many relationship between PM schedules and asset activities.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• PM_SCHEDULE_ID — the identifier of the Preventive Maintenance schedule to which the activity belongs.
• ACTIVITY_ASSOCIATION_ID — the primary key of the row, generated from a sequence, and a foreign key to MTL_EAM_ASSET_ACTIVITIES.
• INTERVAL_MULTIPLE — indicates the interval multiple, or the occurrence of the maintenance activity within the PM cycle.
• ALLOW_REPEAT_IN_CYCLE — flags whether the activity may be repeated within a single cycle.
• DAY_TOLERANCE — defines how many days a planned activity may be delayed; this value is consumed by the suppression logic.
• NEXT_SERVICE_START_DATE — the next service start date of the activity as predicted by the PM engine.
• NEXT_SERVICE_END_DATE — the next service end date of the activity as predicted by the PM engine.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns that record audit and concurrency information.

The documented unique index, EAM_PM_ACTIVITIES_U1, covers PM_SCHEDULE_ID and ACTIVITY_ASSOCIATION_ID and is the business-key candidate for this entity. The physical primary key, EAM_PM_ACTIVITIES_PK, is defined over the same two columns. Note that the metadata lists EAM_PM_ACTIVITIES_U1 as NONUNIQUE while also documenting a primary key on the same column pair; in practice this combination makes the pairing the effective business key even though ACTIVITY_ASSOCIATION_ID is sequence-generated.

Common Use Cases and Queries

Typical uses of this table include reviewing the activities attached to a PM schedule, reporting upcoming predicted service windows, and analyzing how interval multiples and tolerances drive work order generation. The canonical query mirrors the documented query text:

• Retrieve all activities for a given PM schedule: SELECT ACTIVITY_ASSOCIATION_ID, PM_SCHEDULE_ID, INTERVAL_MULTIPLE, NEXT_SERVICE_START_DATE, NEXT_SERVICE_END_DATE FROM EAM.EAM_PM_ACTIVITIES WHERE PM_SCHEDULE_ID = :p_schedule_id;
• Identify activities with a looming predicted service date: filter on NEXT_SERVICE_START_DATE between SYSDATE and SYSDATE + n.
• Report on scheduling tolerance: select rows where DAY_TOLERANCE exceeds a threshold, or where ALLOW_REPEAT_IN_CYCLE = 'Y'.
• Join to EAM_PM_SCHEDULINGS and MTL_EAM_ASSET_ACTIVITIES to produce schedule-to-asset activity reporting.

Related Objects

The most significant related objects are established by the documented foreign keys and primary key relationships:

• EAM.EAM_PM_SCHEDULINGS — joined on EAM_PM_ACTIVITIES.PM_SCHEDULE_ID = EAM_PM_SCHEDULINGS.PM_SCHEDULE_ID.
• MTL_EAM_ASSET_ACTIVITIES — joined on EAM_PM_ACTIVITIES.ACTIVITY_ASSOCIATION_ID = MTL_EAM_ASSET_ACTIVITIES.ACTIVITY_ASSOCIATION_ID.

Additional objects that reference or depend on this table in a working eAM implementation include the PM scheduling and work order generation programs that read NEXT_SERVICE_START_DATE and NEXT_SERVICE_END_DATE, and the associated activity and asset definition tables surfaced through MTL_EAM_ASSET_ACTIVITIES. When the metadata does not enumerate further dependents, these may be discovered through the data dictionary views ALL_CONSTRAINTS, ALL_CONS_COLUMNS, and ALL_DEPENDENCIES for the EAM schema.