Search Results eam_forecasted_work_orders




Overview
Explore in AI Chat

Overview

EAM_FORECASTED_WORK_ORDERS is a table in the EAM (Enterprise Asset Management) schema of Oracle E-Business Suite, holding forecasted work order records generated from preventive maintenance scheduling. It represents the anticipated workload that EAM projects over a future horizon, allowing maintenance planners to review upcoming labor, material, and capacity demands before actual work orders are released to the shop floor.

The table functions as a staging and planning structure between preventive maintenance definitions and executable work orders. Each row ties a forecast entry back to a PM schedule and to an asset activity association, capturing the projected start and completion dates, the asset organization, and the outcome of the forecasting process. The documented schema in ETRM 12.2.2 contains 35 columns, with a primary key of PM_FORECAST_ID enforced through EAM_FORECASTED_WORK_ORDERS_PK.

Based on the heuristic Data Vault classification derived from the foreign key structure, this object is best modeled as a link. It resolves relationships between two principal entities — the PM scheduling definition and the asset activity — while carrying its own descriptive timing attributes. This classification is offered as a modeling suggestion rather than a native Oracle designation.

Key Information Stored

The surrogate primary key is PM_FORECAST_ID, which uniquely identifies each forecasted work order row and is also the sole column in the unique index EAM_FORECASTED_WORK_ORDERS_U1, making it the documented business-key candidate.

Common Use Cases and Queries

Planners use this table to project maintenance demand and to verify that PM schedules will produce work orders on the expected dates. A typical query joins the forecast to PM schedulings to list upcoming forecasts for a given organization:

  • Forecast horizon reporting — select SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, PM_SCHEDULE_ID filtered by ORGANIZATION_ID and a date range.
  • Unprocessed forecast review — filter on PROCESS_FLAG to find rows not yet converted to work orders.
  • Asset activity traceability — join Activity association identifier to MTL_EAM_ASSET_ACTIVITIES to identify the specific asset and activity behind each forecast.
  • Group-level reconciliation — group by GROUP_ID to inspect the output of a single forecast generation run.
  • Cycle and sequence analysis — order by CYCLE_ID and SEQ_ID to reconstruct the PM cycle that produced each entry.

A representative pattern: join EAM_FORECASTED_WORK_ORDERS to EAM_PM_SCHEDULINGS on PM_SCHEDULE_ID, constrain by ORGANIZATION_ID and SCHEDULED_START_DATE, and select the date columns along with WO_STATUS to produce a forward-looking maintenance capacity report.

Related Objects

  • EAM_PM_SCHEDULINGS — referenced via PM_SCHEDULE_ID; the PM schedule definition that seeds the forecast.
  • MTL_EAM_ASSET_ACTIVITIES — referenced via ACTIVITY_ASSOCIATION_ID; the asset activity tied to the forecast.
  • EAM_FORECASTED_WORK_ORDERS_PK / _U1 — primary key constraint and unique index on PM_FORECAST_ID.
  • Work order and WIP tables referenced through WIP_ENTITY_ID, used when forecasts are firmed into executable work orders.
  • PM forecasting and work order generation concurrent programs that populate and consume this table.