Results for “eam_pm_schedulings_u2”

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

Overview

EAM.EAM_PM_SCHEDULINGS is the master table in the Oracle E-Business Suite Enterprise Asset Management (eAM) module that stores the definition of every user-defined Preventive Maintenance (PM) schedule. Each row represents a PM program — the recurring maintenance strategy applied to an asset, rebuildable item, or maintenance object — including its scheduling method, effective dates, cycle state, template origin, and associated maintenance object. The table is owned by the EAM schema, resides in the APPS_TS_TX_DATA tablespace (PCT Free 10), and is documented with 57 columns in ETRM 12.2.2. It is a foundational definition table: the PM program header drives generation of forecasted work orders, PM activities, scheduling rules, and ultimately released WIP jobs.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as hub-leaning. Its stable business key (NAME, enforced by the unique index EAM_PM_SCHEDULINGS_U2) and its role as the anchor referenced by many downstream tables suggest it functions as a hub for the PM scheduling business concept, with descriptive and stateful attributes (effective dates, cycle counters, template flags) behaving as satellite content. This classification is a modeling heuristic rather than a physical constraint enforced by EBS.

Key Information Stored

The surrogate primary key is PM_SCHEDULE_ID, enforced by the EAM_PM_SCHEDULINGS_PK constraint and the unique index EAM_PM_SCHEDULINGS_U1. The principal business-key candidate is NAME, enforced by the unique index EAM_PM_SCHEDULINGS_U2 (the object referenced in the user search). Because both NAME and PM_SCHEDULE_ID are unique, developers should treat PM_SCHEDULE_ID as the internal foreign-key target and NAME as the user-facing identifier.

• NAME — the user-defined PM schedule name (business key).
• MAINTENANCE_OBJECT_ID / MAINTENANCE_OBJECT_TYPE — the asset or maintenance object the schedule applies to; indexed non-uniquely together with SET_NAME_ID via EAM_PM_SCHEDULINGS_N1.
• SET_NAME_ID — the PM set name (foreign key to EAM_PM_SET_NAMES) that groups related schedules.
• FROM_EFFECTIVE_DATE / TO_EFFECTIVE_DATE — the effective start and end dates of the schedule.
• NON_SCHEDULED_FLAG — indicates a run-to-failure schedule.
• SCHEDULING_METHOD_CODE / TYPE_CODE — the scheduling method (e.g., cyclic vs. meter-based) and schedule type.
• RESCHEDULING_POINT, LEAD_TIME, DAY_TOLERANCE, WHICHEVER_FIRST — scheduling control attributes governing when work is generated.
• INTERVAL_PER_CYCLE, CURRENT_CYCLE, CURRENT_SEQ, CURRENT_WO_SEQ — cycle definition and current cycle/sequence counters.
• BASE_DATE, BASE_READING, EAM_LAST_CYCLIC_ACT — base reference for cyclic and meter-based schedules.
• NEXT_SERVICE_START_DATE / NEXT_SERVICE_END_DATE — the next scheduled service window.
• TMPL_FLAG, SOURCE_TMPL_ID, AUTO_INSTANTIATION_FLAG — template origin and auto-instantiation behavior.
• GENERATE_NEXT_WORK_ORDER, GENERATE_WO_STATUS, DEFAULT_IMPLEMENT, INCLUDE_MANUAL — work-order generation controls.
• ACTIVITY_ASSOCIATION_ID — documented as no longer used, with a historical foreign key to MTL_EAM_ASSET_ACTIVITIES.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield columns.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE) — audit tracking.

Common Use Cases and Queries

Typical reporting scenarios include listing active PM schedules for a given maintenance object, auditing schedules nearing their effective end date, and reconciling cycle state against generated work orders. Because NAME is uniquely indexed, name-based lookups are efficient:

• Retrieve a schedule by business key:

  SELECT pm_schedule_id, name, maintenance_object_id, scheduling_method_code, next_service_start_date FROM eam.eam_pm_schedulings WHERE name = :pm_name;

• Find all schedules for an asset:

  SELECT pm_schedule_id, name, from_effective_date, to_effective_date FROM eam.eam_pm_schedulings WHERE maintenance_object_id = :object_id AND set_name_id = :set_name_id;

• List run-to-failure schedules:

  SELECT pm_schedule_id, name FROM eam.eam_pm_schedulings WHERE non_scheduled_flag = 'Y';

• Identify templates versus instantiated schedules via TMPL_FLAG and SOURCE_TMPL_ID.
• Join to forecasted work orders to compare planned versus actual cycle state using PM_SCHEDULE_ID.

Related Objects

EAM_PM_SCHEDULINGS participates in a fan-out of dependent tables keyed on PM_SCHEDULE_ID, and references two parent objects. The most significant related objects are:

• EAM.EAM_PM_SET_NAMES — joined via SET_NAME_ID; groups PM schedules into sets.
• MTL_EAM_ASSET_ACTIVITIES — historically joined via ACTIVITY_ASSOCIATION_ID (column no longer used).
• EAM.EAM_PM_ACTIVITIES — child table referencing PM_SCHEDULE_ID; stores the individual activities within a schedule.
• EAM.EAM_PM_SCHEDULING_RULES — child table referencing PM_SCHEDULE_ID; holds rule definitions for schedule execution.
• EAM.EAM_FORECASTED_WORK_ORDERS — references PM_SCHEDULE_ID; holds forecasted work orders produced by the schedule.
• EAM.EAM_FORECAST_WDJ — forecast work-order detail referencing PM_SCHEDULE_ID.
• WIP_DISCRETE_JOBS — references PM_SCHEDULE_ID for eAM-generated jobs.
• WIP_JOB_SCHEDULE_INTERFACE — references PM_SCHEDULE_ID during job scheduling interfaces.
• EAM.EAM_WORK_ORDER_IMPORT — references PM_SCHEDULE_ID when importing generated work orders.

These relationships confirm the table's role as the PM definition hub from which scheduling, forecasting, and work-order generation flows derive.