Results for “eam_forecast_wor”

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

Overview

EAM.EAM_FORECAST_WOR is a VALID table within the Enterprise Asset Management (EAM) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the resource requirements associated with forecasted work orders, serving as the resource-level detail layer beneath eAM maintenance budgeting and forecasting. Where a forecasted work order header defines the scope of anticipated maintenance, EAM_FORECAST_WOR captures the individual resources — labor, equipment, and services — planned against each operation, together with their usage rates, scheduled units, and projected cost values.

The table carries 71 documented columns and is owned by the EAM schema. Its foreign keys reference WIP_REPETITIVE_SCHEDULES, BOM_DEPARTMENTS, and BOM_SETUP_TYPES, placing it firmly within the manufacturing/WIP resource model that eAM inherits and extends. From a Data Vault modeling perspective, the mined heuristic classification is standalone, with no upstream parent link. In practice the table behaves as a satellite-like resource detail structure keyed to a forecast or work order entity, carrying descriptive and numeric measures rather than acting as a hub of business entities.

Key Information Stored

The most significant columns fall into four groups:

• Identity and key context: WIP_ENTITY_ID, ORGANIZATION_ID, FORECAST_ID, GROUP_SEQUENCE_ID, GROUP_SEQUENCE_NUMBER.
• Resource definition: RESOURCE_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, PARENT_RESOURCE_SEQ, RESOURCE_SEQ_NUM, UOM_CODE, BASIS_TYPE, USAGE_RATE_OR_AMOUNT, ASSIGNED_UNITS, MAXIMUM_ASSIGNED_UNITS, APPLIED_RESOURCE_UNITS, APPLIED_RESOURCE_VALUE.
• Scheduling and dating: START_DATE, COMPLETION_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE, PROJECTED_COMPLETION_DATE, SCHEDULED_FLAG, FIRM_FLAG.
• Relief and financial rollup: RELIEVED_RES_COMPLETION_UNITS, RELIEVED_RES_SCRAP_UNITS, RELIEVED_RES_COMPLETION_VALUE, RELIEVED_RES_SCRAP_VALUE, RELIEVED_VARIANCE_VALUE, RELIEVED_RES_UNITS, RELIEVED_RES_VALUE, TEMP_RELIEVED_VALUE.
• Classification and controls: DEPARTMENT_ID, SETUP_ID, PHANTOM_FLAG, PHANTOM_OP_SEQ_NUM, PHANTOM_ITEM_ID, SUBSTITUTE_GROUP_NUM, REPLACEMENT_GROUP_NUM, PRINCIPLE_FLAG, AUTOCHARGE_TYPE, STANDARD_RATE_FLAG.
• Flexfields and audit: ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15, plus WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Business-key candidates are the natural composite of ORGANIZATION_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, and RESOURCE_SEQ_NUM, which together isolate a single resource requirement line. No explicit unique index is documented in the provided metadata; WIP_ENTITY_ID functions as the principal entity reference rather than a surrogate primary key exposed to end users.

Common Use Cases and Queries

Typical usage centers on maintenance budget preparation and forecast variance review. A standard pattern aggregates forecasted resource value by department and organization for a budgeting period:

• Summing APPLIED_RESOURCE_VALUE grouped by DEPARTMENT_ID and ORGANIZATION_ID to produce departmental maintenance cost forecasts.
• Comparing APPLIED_RESOURCE_VALUE against RELIEVED_RES_VALUE, RELIEVED_RES_COMPLETION_VALUE, and RELIEVED_VARIANCE_VALUE to measure forecast-to-actual resource consumption.
• Filtering on BASIS_TYPE, USAGE_RATE_OR_AMOUNT, and ASSIGNED_UNITS to validate planned labor and equipment loading per operation.
• Joining to work order forecast headers via FORECAST_ID or WIP_ENTITY_ID to report forecasted maintenance by asset or schedule.
• Excluding rows where FIRM_FLAG or SCHEDULED_FLAG indicates unconfirmed plans when producing firm budget submissions.
• Using PROJECTED_COMPLETION_DATE and ACTUAL_COMPLETION_DATE for schedule adherence reporting on forecasted operations.

Related Objects

• BOM_DEPARTMENTS — joined on DEPARTMENT_ID to attribute resource cost to owning departments.
• BOM_SETUP_TYPES — joined on SETUP_ID to identify resource setup classification.
• WIP_REPETITIVE_SCHEDULES — joined on REPETITIVE_SCHEDULE_ID for repetitive maintenance resource planning.
• BOM_RESOURCES — resolves RESOURCE_ID to resource name, unit of measure, and standard rates.
• WIP_ENTITIES — resolves WIP_ENTITY_ID to the work order or forecast entity header.
• BOM_OPERATIONAL_ROUTINGS / WIP_OPERATIONS — supply operation context through OPERATION_SEQ_NUM.
• EAM_FORECAST_WO (forecast work order header) — the parent forecasting entity joined via FORECAST_ID.