Search Results eam_pm_activities_pk

Overview

EAM_PM_ACTIVITIES is a transactional table in the Oracle Enterprise Asset Management (EAM) module, owned by the EAM schema. It stores the preventive maintenance (PM) schedule activities together with the attributes that govern how those activities are executed against an asset. Each row represents the association between a PM schedule and a specific asset activity, forming the operational backbone of PM forecasting, scheduling, and generation in Oracle EBS 12.1.1 and 12.2.2.

Within the Oracle EBS EAM data model, the table sits at the intersection of the PM definition and the asset activity definitions. A PM schedule (held in EAM_PM_SCHEDULINGS) can encompass one or more asset activities (held in MTL_EAM_ASSET_ACTIVITIES); EAM_PM_ACTIVITIES is the resolution of that many-to-many relationship, carrying the scheduling parameters specific to each pairing.

According to the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link. It connects two parent hubs — the PM scheduling hub and the asset activity hub — while carrying descriptive and scheduling attributes such as interval multiples and service dates. Foreign keys are enforced to MTL_EAM_ASSET_ACTIVITIES via ACTIVITY_ASSOCIATION_ID and to EAM_PM_SCHEDULINGS via PM_SCHEDULE_ID, consistent with the link classification.

Key Information Stored

The table contains twelve documented columns. The composite primary key is defined by the unique constraint EAM_PM_ACTIVITIES_PK, composed of PM_SCHEDULE_ID and ACTIVITY_ASSOCIATION_ID. A second unique index, EAM_PM_ACTIVITIES_U1, repeats the same column pair, confirming it as the business-key candidate for the entity.

• PM_SCHEDULE_ID — Foreign key to EAM_PM_SCHEDULINGS; identifies the parent PM schedule to which the activity belongs.
• ACTIVITY_ASSOCIATION_ID — Foreign key to MTL_EAM_ASSET_ACTIVITIES; identifies the asset activity being scheduled.
• INTERVAL_MULTIPLE — Defines how many intervals of the PM schedule must pass before the activity is executed.
• ALLOW_REPEAT_IN_CYCLE — Flag indicating whether the activity may recur more than once within a single PM cycle.
• DAY_TOLERANCE — The permitted variance in days around the target service date, used for scheduling flexibility.
• NEXT_SERVICE_START_DATE — The projected start date of the next service occurrence for the activity.
• NEXT_SERVICE_END_DATE — The projected end date of the next service occurrence.

The remaining documented columns are the standard Oracle EBS audit attributes: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. These support change tracking and concurrency control but carry no business meaning beyond audit.

Common Use Cases and Queries

EAM_PM_ACTIVITIES is central to PM forecasting and work order generation. Typical reporting scenarios include listing all activities for a given PM schedule, determining upcoming service windows, and auditing interval configuration.

To retrieve all activities for a specific schedule:

• SELECT ACTIVITY_ASSOCIATION_ID, INTERVAL_MULTIPLE, NEXT_SERVICE_START_DATE FROM EAM_PM_ACTIVITIES WHERE PM_SCHEDULE_ID = :p_schedule_id;

To identify activities due within a window:

• SELECT PM_SCHEDULE_ID, ACTIVITY_ASSOCIATION_ID, NEXT_SERVICE_END_DATE FROM EAM_PM_ACTIVITIES WHERE NEXT_SERVICE_START_DATE BETWEEN :start_date AND :end_date;

To join activities to their parent PM schedulings and asset activities for a comprehensive forecast report, query EAM_PM_ACTIVITIES as the link, joining PM_SCHEDULE_ID to EAM_PM_SCHEDULINGS and ACTIVITY_ASSOCIATION_ID to MTL_EAM_ASSET_ACTIVITIES. These queries support maintenance planners reviewing upcoming workload and analysts validating PM configuration.

Related Objects

The table participates in a tightly coupled cluster within the EAM data model. Significant related objects include:

• EAM_PM_SCHEDULINGS — Parent PM schedule definition; joined on PM_SCHEDULE_ID.
• MTL_EAM_ASSET_ACTIVITIES — Parent asset activity definition; joined on ACTIVITY_ASSOCIATION_ID.
• EAM_PM_SCHEDULES — Related scheduling entity in the PM hierarchy.
• EAM_WORK_ORDERS and EAM_WORK_ORDER_OPERATIONS — Downstream objects populated when PM activities generate maintenance work orders.
• MTL_EAM_ASSET_NUMBERS — Asset master referenced indirectly through the activity association.

Because EAM_PM_ACTIVITIES is a link entity, any change to its parent schedulings or asset activities can affect PM forecast output, making it a high-impact table for integration and data migration efforts.