Results for “eam_forecast_wdj”

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

Overview

EAM_FORECAST_WDJ is a transactional table in the Oracle Enterprise Asset Management (eAM) schema that stores the discrete job (work order) header information for forecasted maintenance work orders. It is the eAM equivalent of the WIP_DISCRETE_JOBS structure but repurposed for maintenance budgeting and forecasting workflows. Records in this table represent simulated or planned work orders that have not yet been released to the shop floor, enabling organizations to project material, resource, and cost requirements across future maintenance periods.

The table sits at the intersection of eAM maintenance planning and Oracle Work in Process (WIP) job modeling. Its structure mirrors a WIP discrete job, carrying BOM/routing references, scheduling dates, quantity fields, accounting flexfield assignments, and WIP valuation accounts, but it is keyed by a FORECAST_ID that ties each record to a specific forecast run.

Under a heuristic Data Vault classification derived from the foreign-key structure, this object is best modeled as a satellite attached to a forecast hub, since it carries descriptive and mutable attributes (dates, quantities, statuses) rather than representing an independent business entity or a pure many-to-many association.

Key Information Stored

The composite primary key EAM_FORECAST_WDJ_PK is defined on (WIP_ENTITY_ID, FORECAST_ID). WIP_ENTITY_ID is the surrogate work-order identifier shared with the WIP entity model, while FORECAST_ID distinguishes the forecast scenario under which the work order was generated. Together they form the unique business key.

• WIP_ENTITY_ID, FORECAST_ID — composite primary key identifying each forecasted work order.
• ORGANIZATION_ID — inventory organization owning the job.
• PRIMARY_ITEM_ID — the asset or item being maintained.
• STATUS_TYPE, JOB_TYPE, WORK_ORDER_TYPE — classify the job's lifecycle status and category.
• SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE, DUE_DATE — core planning dates used for forecast horizons.
• START_QUANTITY, NET_QUANTITY, QUANTITY_COMPLETED — planned versus executed quantities.
• ASSET_NUMBER, ASSET_GROUP_ID, MAINTENANCE_OBJECT_ID — the maintained asset context.
• PM_SCHEDULE_ID — links forecasted work to preventive-maintenance schedules.
• ACTIVITY_TYPE, ACTIVITY_CAUSE, ACTIVITY_SOURCE — maintenance activity classification.
• MATERIAL_ACCOUNT, RESOURCE_ACCOUNT, OVERHEAD_ACCOUNT — cost/accounting assignments.
• ESTIMATION_STATUS, LAST_ESTIMATION_DATE — state of the forecast estimation process.
• ATTRIBUTE1–ATTRIBUTE15 — DFF extensibility columns.

Common Use Cases and Queries

Typical use cases include maintenance budget forecasting, PM workload projection, and asset-level cost estimation. A representative query retrieves forecasted work orders for a given forecast run and organization:

• SELECT wip_entity_id, primary_item_id, scheduled_start_date, start_quantity FROM eam.eam_forecast_wdj WHERE forecast_id = :p_forecast_id AND organization_id = :p_org_id;
• Aggregate estimated quantities and counts by activity type for budgeting: GROUP BY activity_type, activity_cause.
• Join to EAM_PM_SCHEDULINGS via PM_SCHEDULE_ID to reconcile preventive plans against their forecasted jobs.
• Track estimation progress using ESTIMATION_STATUS and LAST_ESTIMATION_DATE to identify unestimated forecasted work.

Related Objects

• EAM_PM_SCHEDULINGS — joined via PM_SCHEDULE_ID to link forecasts to PM plans.
• WIP_SCHEDULE_GROUPS — joined via SCHEDULE_GROUP_ID for schedule grouping.
• MTL_KANBAN_CARDS — joined via KANBAN_CARD_ID for kanban-driven supply.
• WIP_DISCRETE_JOBS — the released-job counterpart sharing WIP_ENTITY_ID semantics.
• EAM_FORECAST (forecast definition) — parent forecast entity referenced by FORECAST_ID.
• MTL_SYSTEM_ITEMS_B — joined via PRIMARY_ITEM_ID for item descriptions.
• BOM / WIP BOM structures — referenced through BOM_REFERENCE_ID and ROUTING_REFERENCE_ID.