Results for “interval_per_cycle”

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

Overview

EAM_PM_SCHEDULINGS is the master definition table for Preventive Maintenance schedules within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It stores the header-level configuration that governs how recurring preventive maintenance work orders are generated against assets, maintenance objects, and asset activities. Each row represents a single PM schedule, identified by its surrogate primary key PM_SCHEDULE_ID, and carries the control parameters that determine cycle intervals, effective date ranges, rescheduling logic, and work order generation behavior.

The table is owned by the EAM schema and is documented as VALID in ETRM 12.2.2 with 57 physical columns. It is present in both 12.1.1 and 12.2.2, though the column inventory may vary slightly between releases. Functionally, EAM_PM_SCHEDULINGS sits at the center of the PM forecasting chain: it is the parent of PM activities, scheduling rules, and forecasted work orders, and it is referenced by work order import, discrete job, and forecast staging tables. Under a Data Vault modeling heuristic, the foreign-key profile classifies this object as hub-leaning — it behaves as a business entity hub keyed on PM_SCHEDULE_ID, with descriptive and temporal attributes bordering on satellite semantics.

Key Information Stored

The most significant columns of EAM_PM_SCHEDULINGS include:

• PM_SCHEDULE_ID — surrogate primary key (EAM_PM_SCHEDULINGS_PK) and unique index EAM_PM_SCHEDULINGS_U1.
• NAME — business-key candidate enforced by unique index EAM_PM_SCHEDULINGS_U2; the user-visible schedule name.
• ACTIVITY_ASSOCIATION_ID — foreign key to MTL_EAM_ASSET_ACTIVITIES linking the schedule to an asset activity.
• SET_NAME_ID — foreign key to EAM_PM_SET_NAMES defining the set membership for the schedule.
• SCHEDULING_METHOD_CODE and TYPE_CODE — determine the algorithmic basis (e.g., calendar-based or meter/reading-based) and the PM type.
• INTERVAL_PER_CYCLE, CURRENT_CYCLE, CURRENT_SEQ — drive cyclic recurrence and current progress state.
• FROM_EFFECTIVE_DATE / TO_EFFECTIVE_DATE — validity window for the schedule.
• RESCHEDULING_POINT, LEAD_TIME, DAY_TOLERANCE — control when the next work order is forecasted relative to the due date.
• BASE_DATE, BASE_READING — anchors for calendar and meter-based schedules respectively.
• NEXT_SERVICE_START_DATE, NEXT_SERVICE_END_DATE — projected service window used by forecasting processes.
• MAINTENANCE_OBJECT_ID and MAINTENANCE_OBJECT_TYPE — the asset or maintenance object the schedule applies to.
• WHICHEVER_FIRST, INCLUDE_MANUAL, AUTO_INSTANTIATION_FLAG — behavioral flags affecting work order generation.
• GENERATE_WO_STATUS, GENERATE_NEXT_WORK_ORDER — govern the status and trigger for auto-generated work orders.
• PLANNER_MAINTENANCE, SOURCE_TMPL_ID, TMPL_FLAG — template sourcing and planner assignment.

Common Use Cases and Queries

Typical applications of EAM_PM_SCHEDULINGS include PM program review, forecast reporting, work order generation validation, and migration or template analysis. A common reporting pattern joins the schedule header to its child activities:

• Listing all active PM schedules plus their next service dates: SELECT pm.NAME, pm.SCHEDULING_METHOD_CODE, pm.NEXT_SERVICE_START_DATE, pm.NEXT_SERVICE_END_DATE FROM EAM_PM_SCHEDULINGS pm WHERE pm.TO_EFFECTIVE_DATE IS NULL OR pm.TO_EFFECTIVE_DATE > SYSDATE;
• Identifying schedules due within a tolerance window using RESCHEDULING_POINT, LEAD_TIME, and DAY_TOLERANCE.
• Auditing auto-instantiation: filtering on AUTO_INSTANTIATION_FLAG and GENERATE_WO_STATUS to confirm which schedules will produce work orders automatically.
• Linking schedules to activities: joining ACTIVITY_ASSOCIATION_ID to MTL_EAM_ASSET_ACTIVITIES to enumerate the maintenance tasks within each PM program.
• Comparing template schedules (TMPL_FLAG = 'Y') to instantiated schedules via SOURCE_TMPL_ID to trace template propagation.

Related Objects

• EAM_PM_ACTIVITIES — child table; join on PM_SCHEDULE_ID, FK EAM_PM_ACTIVITIES.PM_SCHEDULE_ID.
• EAM_PM_SCHEDULING_RULES — child table; join on PM_SCHEDULE_ID, FK EAM_PM_SCHEDULING_RULES.PM_SCHEDULE_ID.
• EAM_FORECASTED_WORK_ORDERS — forecast staging; FK EAM_FORECASTED_WORK_ORDERS.PM_SCHEDULE_ID.
• EAM_FORECAST_WDJ — forecast work order staging interface; join on PM_SCHEDULE_ID.
• EAM_WORK_ORDER_IMPORT — import staging table; join on PM_SCHEDULE_ID.
• WIP_DISCRETE_JOBS and WIP_JOB_SCHEDULE_INTERFACE — reference PM_SCHEDULE_ID for PM-generated discrete work.
• MTL_EAM_ASSET_ACTIVITIES — referenced via EAM_PM_SCHEDULINGS.ACTIVITY_ASSOCIATION_ID.
• EAM_PM_SET_NAMES — referenced via EAM_PM_SCHEDULINGS.SET_NAME_ID.