Search Results eam_pm_scheduling_rules




Overview
Explore in AI Chat

Overview

The EAM_PM_SCHEDULING_RULES table is a core configuration object within Oracle Enterprise Asset Management (EAM). It stores the scheduling rules that govern how Preventive Maintenance (PM) schedules are generated and executed against assets. Each row represents a single rule that determines the trigger methodology — a fixed calendar interval, a meter or counter-based interval, or a combination of both — for an associated PM schedule defined in EAM_PM_SCHEDULINGS. In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the EAM schema and is fundamental to the automatic work order generation engine used by maintenance planners.

From a data modeling perspective, the ETRM relationship metadata classifies this object heuristically as a link table. This classification is suggested because EAM_PM_SCHEDULING_RULES carries foreign keys that connect the EAM_PM_SCHEDULINGS table to the CSI_COUNTERS_B meter table, effectively resolving a many-to-many style association between a PM schedule and its metered assets. The presence of descriptive attributes such as rule type, base date, and interval values means the table also exhibits satellite-like characteristics, but its dominant role is that of an associative link carrying relationship-level attributes.

Key Information Stored

The documented physical schema for this table contains 22 columns. The most significant columns are:

Common Use Cases and Queries

Maintenance planners and developers query this table to audit why a PM generated at a particular time, to troubleshoot missing work orders, or to report on meter-driven maintenance programs. A typical query retrieves all active rules for a given asset's PM schedule:

SELECT r.RULE_TYPE, r.BASE_DATE, r.DAY_INTERVAL, r.RUNTIME_INTERVAL FROM EAM.EAM_PM_SCHEDULING_RULES r WHERE r.PM_SCHEDULE_ID = :schedule_id;

Meter-based analysis joins to CSI_COUNTERS_B to obtain counter names and current readings, comparing them against LAST_SERVICE_READING and RUNTIME_INTERVAL to predict the next due service. Reporting use cases include PM program coverage reports, interval-effectiveness analysis, and migration validation using MIGRATED_FLAG.

Related Objects

  • EAM_PM_SCHEDULINGS — Parent table; joined on PM_SCHEDULE_ID. Defines the PM schedule header each rule belongs to.
  • CSI_COUNTERS_B — Meter definition table; joined on METER_ID. Supplies counter identity and current readings.
  • CSI_COUNTER_READINGS — Historical meter readings used to evaluate runtime intervals against LAST_SERVICE_READING.
  • EAM_WORK_ORDERS — Downstream output; work orders generated when a scheduling rule becomes due.
  • EAM_PM_SCHEDULE_TEMPLATES / EAM_PM_SCHEDULE_SETS — Related EAM PM configuration objects that leverage scheduling rules.
  • EAM_ORG_ASSETS / CSI_ITEM_INSTANCES — Asset master records linked through the PM schedule for reporting asset-level PM exposure.