Results for “eam_forecast_wedi”

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

Overview

EAM_FORECAST_WEDI is an Enterprise Asset Management (EAM) table in the Oracle E-Business Suite that stores direct item information associated with forecasted work orders used in eAM maintenance budgeting and forecasting. Its design deliberately mirrors the structure of WIP_EAM_DIRECT_ITEMS, which holds equivalent direct-item detail for live (non-forecast) eAM work orders. This parallel construction allows budgeting and forecasting engines, as well as reporting layers, to apply the same material planning logic to projected maintenance activity that they apply to actual work orders.

In Oracle EBS 12.1.1 and 12.2.2, the table is owned by the EAM schema and is documented with 46 columns. It supports the broader eAM forecasting flow in which planners model anticipated maintenance work, estimate the direct material and outside-processing requirements of that work, and attach vendor and pricing information for budgetary evaluation. Because direct items represent material or service requirements issued straight to a work order rather than components consumed through a bill of material, this table is central to cost estimation accuracy in maintenance forecasting.

ETRM classifies the object heuristically as standalone within a Data Vault model. Treated as a modeling suggestion, this implies the table is not a natural hub or link but rather behaves as a satellite-like or transactional record whose meaning depends on its parent forecast and work order context. The single documented foreign key, EAM_FORECAST_WEDI.DEPARTMENT_ID referencing BOM_DEPARTMENTS, reinforces that the table is largely self-contained with limited enforced referential dependencies.

Key Information Stored

The most significant columns include the following:

• DIRECT_ITEM_SEQUENCE_ID — the surrogate identifier for each direct item line; the principal unique key candidate within the forecast line set.
• FORECAST_ID — the business key linking the line to its parent forecast; the most important join driver for forecasting reports.
• WIP_ENTITY_ID — the work order entity associated with the forecasted direct item, mirroring the live WIP construct.
• ORGANIZATION_ID — the inventory organization in which the item requirement is evaluated.
• OPERATION_SEQ_NUM — the routing operation sequence to which the direct item applies.
• DEPARTMENT_ID — the department owning the requirement; the sole documented foreign key to BOM_DEPARTMENTS.
• REQUIRED_QUANTITY and UOM — the quantity and unit of measure needed.
• NEED_BY_DATE — the date by which the material or service is required.
• UNIT_PRICE — the estimated cost per unit used in budgeting.
• PURCHASING_CATEGORY_ID — the category used for sourcing and spend analysis.
• SUGGESTED_VENDOR_ID, SUGGESTED_VENDOR_SITE_ID, SUGGESTED_VENDOR_ITEM_NUM, SUGGESTED_VENDOR_NAME — vendor sourcing details.
• AUTO_REQUEST_MATERIAL — flag governing automatic requisition generation.
• DESCRIPTION — free-text identification of the direct item.

The fifteen ATTRIBUTE1–15 columns plus the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and concurrent program columns (PROGRAM_ID, REQUEST_ID) provide extensibility and audit traceability.

Common Use Cases and Queries

Typical usage centers on forecasting reports that aggregate estimated direct material cost by organization, department, or forecast. A representative query joins the line to its forecast and resolves the department name:

• SELECT w.FORECAST_ID, w.DIRECT_ITEM_SEQUENCE_ID, w.DESCRIPTION, w.REQUIRED_QUANTITY, w.UOM, w.UNIT_PRICE, d.DEPARTMENT_CODE FROM EAM.EAM_FORECAST_WEDI w, BOM.BOM_DEPARTMENTS d WHERE w.DEPARTMENT_ID = d.DEPARTMENT_ID AND w.ORGANIZATION_ID = :org_id;
• Budget rollups summing REQUIRED_QUANTITY * UNIT_PRICE grouped by FORECAST_ID or ORGANIZATION_ID.
• Vendor spend projections grouping by SUGGESTED_VENDOR_ID and PURCHASING_CATEGORY_ID.
• Comparison of forecasted direct items against actual WIP_EAM_DIRECT_ITEMS rows for variance analysis.
• Need-by scheduling to identify direct items required within a planning horizon.

Related Objects

The most significant related objects are WIP_EAM_DIRECT_ITEMS, whose structure this table mirrors; the parent eAM forecast objects keyed by FORECAST_ID; BOM_DEPARTMENTS via DEPARTMENT_ID; WIP entities referenced by WIP_ENTITY_ID; inventory organizations via ORGANIZATION_ID; purchasing categories via PURCHASING_CATEGORY_ID; supplier and supplier site tables via SUGGESTED_VENDOR_ID and SUGGESTED_VENDOR_SITE_ID; and the standard FND audit and concurrent program tables referenced by the WHO and PROGRAM columns.