Search Results eam_forecasted_work_orders_n1

Overview

The EAM.EAM_FORECASTED_WORK_ORDERS table is a transient staging table within the Oracle Enterprise Asset Management (EAM) module. It stores forecasted work orders generated by the preventive maintenance (PM) scheduler that are candidates for conversion into actual work orders. Records are inserted by the PM scheduling process and are removed when the user exits the forecasting process, meaning the table functions as a working set rather than a permanent history repository. Upon conversion, the resulting work order identifier is written back to the WIP_ENTITY_ID column.

In the context of a heuristic Data Vault classification, this object exhibits link characteristics. It records a relationship between a preventive maintenance schedule, an asset activity association, and the resulting forecast, rather than acting as a standalone business hub or an immutable descriptive satellite. The table sits at the intersection of schedule definitions and asset maintenance activities, making it a natural associative entity.

Key Information Stored

The table contains 35 documented columns. The most operationally significant are:

• PM_FORECAST_ID — the surrogate primary key and forecast unique identifier, enforced by the unique index EAM_FORECASTED_WORK_ORDERS_U1 on the APPS_TS_TX_IDX tablespace. This is also the documented business-key candidate.
• PM_SCHEDULE_ID — the preventive maintenance schedule that generated the forecast; a foreign key to EAM_PM_SCHEDULINGS.
• ACTIVITY_ASSOCIATION_ID — the asset activity association identifier; a foreign key to MTL_EAM_ASSET_ACTIVITIES.
• GROUP_ID — groups related forecast records into a single logical batch.
• WIP_ENTITY_ID — the work order identifier, populated only after a forecast is assigned to an actual work order.
• SCHEDULED_START_DATE and SCHEDULED_COMPLETION_DATE — the planned execution window for the resulting work order.
• ACTION_TYPE — suggests the type of action the work order will perform.
• PROCESS_FLAG — indicates whether the work order will be processed during conversion.
• WO_STATUS, CYCLE_ID, and SEQ_ID — status and scheduling sequence attributes supporting PM cycle handling.
• PM_BASE_METER_READING — the meter reading baseline used for meter-driven PM scheduling.
• ORGANIZATION_ID — the inventory organization context for the forecast.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns complete the structure.

Common Use Cases and Queries

Forecasted work order data supports several operational and reporting scenarios. Planners review pending forecasts before committing them to actual work orders; the PROCESS_FLAG and ACTION_TYPE columns drive that filtering logic. Reporting queries typically group forecasts by schedule or asset to project upcoming maintenance load.

A representative query joins forecasts to their source schedule and asset activity:

• SELECT f.PM_FORECAST_ID, f.PM_SCHEDULE_ID, f.ACTIVITY_ASSOCIATION_ID, f.SCHEDULED_START_DATE, f.WIP_ENTITY_ID, f.PROCESS_FLAG
• FROM EAM.EAM_FORECASTED_WORK_ORDERS f
• WHERE f.ORGANIZATION_ID = :org_id
• AND f.PROCESS_FLAG = 'Y'

Because the table is truncated when users exit the forecasting process, it should not be relied upon for historical trending; instead, it is queried in real time during planning sessions. Index EAM_FORECASTED_WORK_ORDERS_N1 on GROUP_ID and ACTIVITY_ASSOCIATION_ID supports group-level and asset-level retrieval.

Related Objects

• EAM.EAM_PM_SCHEDULINGS — referenced through PM_SCHEDULE_ID; defines the preventive maintenance schedule generating the forecast.
• MTL_EAM_ASSET_ACTIVITIES — referenced through ACTIVITY_ASSOCIATION_ID; identifies the asset and activity combination.
• EAM.EAM_FORECASTED_WORK_ORDERS_U1 — unique index on PM_FORECAST_ID enforcing the primary key.
• EAM.EAM_FORECASTED_WORK_ORDERS_N1 — non-unique index on GROUP_ID and ACTIVITY_ASSOCIATION_ID.
• WIP entities — referenced through WIP_ENTITY_ID once a forecast is converted to an actual work order.
• EAM.EAM_FORECASTED_WORK_ORDERS_PK — the primary key constraint on PM_FORECAST_ID.