Results for “eam_forecast_work_order_v”

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

Overview

The APPS.EAM_FORECAST_WORK_ORDER_V view is a reporting and integration object within the Oracle E-Business Suite Enterprise Asset Management (eAM) module. Its documented purpose is to resolve all foreign keys for forecasted work orders that participate in eAM maintenance budgeting and forecasting. In this role, the view functions as a denormalized presentation layer that joins the forecasting base table EAM_FORECAST_WDJ to the master and transactional tables required to render human-readable values in place of numeric identifiers.

Because eAM forecasting is used to project future maintenance demand and cost, the view supplies the descriptive context — asset instance, item, location, department, work order type, activity type, activity cause, activity source, and project/task attributes — needed by budgeting reports, forecasting extracts, and downstream integrations. In Oracle EBS 12.1.1 and 12.2.2 the object is shipped in the APPS schema with status VALID and is owned by the EAM product. It is a view only; it stores no data and therefore reflects the current state of its underlying base objects at query time.

Underlying Base Objects

The view is defined over a mixture of eAM, inventory, work-in-process, purchasing, and project objects, most referenced as APPS synonyms. The documented referenced base objects are:

• EAM_FORECAST_WDJ — the forecast work order driver table and the primary source of forecasted work order rows.
• WIP_ENTITIES — supplies the work order entity and its name.
• CSI_ITEM_INSTANCES — provides the asset instance number and description for the maintenance object.
• MTL_SYSTEM_ITEMS_KFV — key flexfield view used twice (aliases MSI and MSI2) to resolve concatenated item segments for the asset item and the primary item.
• MTL_EAM_LOCATIONS — resolves the asset's area location code.
• BOM_DEPARTMENTS — resolves the owning department code.
• MTL_PARAMETERS — links the item organization to its maintenance organization.
• EAM_ORG_MAINT_DEFAULTS — provides organization-level maintenance defaults, including area information for the asset.
• PJM_TASKS_V — resolves project name and task name for forecasted work associated with a project.
• MFG_LOOKUPS — referenced multiple times (WOTYPE, ACTTYPE, ACTCAUSE, ACTSOURCE) to translate lookup codes into meanings.
• FND_PROFILE and PA_TASK_UTILS — supporting packages/functions used in the view logic.

Joins are largely outer joins (noted with the (+) operator), preserving forecast rows even when optional descriptive attributes such as department, location, or project/task are not present.

Key Columns

• FORECAST_ID — unique identifier of the forecasted work order record.
• WIP_ENTITY_ID and WIP_ENTITY_NAME — the work order entity identifier and its display name.
• ORGANIZATION_ID — the maintenance organization owning the forecast.
• INSTANCE_NUMBER and INSTANCE_DESCRIPTION — the asset instance and its description.
• CONCATENATED_SEGMENTS — concatenated item key flexfield segments for the asset item and, via the second alias, the primary item.
• LOCATION_CODES and DEPARTMENT_CODE — the asset area location and owning department.
• MEANING (work order type, activity type, activity cause, activity source) — decoded lookup meanings describing the nature of the forecast work.
• DESCRIPTION, SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE — forecast work description and schedule dates.
• CLASS_CODE, PLAN_MAINTENANCE, PM_SCHEDULE_ID — work classification and preventive maintenance linkage.
• PROJECT_NAME, TASK_NAME — project and task attribution where applicable.

Common Use Cases and Queries

Typical uses include maintenance budget preparation, forecast work order listings by asset or department, and integration extracts that require decoded lookup values.

Listing forecasted work orders for a maintenance organization:

SELECT forecast_id, wip_entity_name, instance_number,
       concatenated_segments, scheduled_start_date,
       scheduled_completion_date, meaning
FROM   apps.eam_forecast_work_order_v
WHERE  organization_id = :p_org_id
ORDER BY scheduled_start_date;

Summarizing forecast work by asset instance and activity type:

SELECT instance_number, instance_description, meaning,
       COUNT(*) forecast_count
FROM   apps.eam_forecast_work_order_v
WHERE  planned_start_date BETWEEN :p_from AND :p_to
GROUP BY instance_number, instance_description, meaning;

Retrieving project-linked forecast work:

SELECT wip_entity_name, project_name, task_name,
       department_code, description
FROM   apps.eam_forecast_work_order_v
WHERE  project_name IS NOT NULL;

Because the view resolves all foreign keys, queries against it avoid additional joins to lookup and master tables, simplifying both ad hoc reporting and scheduled extracts in 12.1.1 and 12.2.2.