Results for “eam_forecasts”

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

Overview

EAM_FORECASTS is a table in the EAM (Enterprise Asset Management) schema of Oracle E-Business Suite, present and validated in both release 12.1.1 and 12.2.2. It stores the selection criteria for forecasts and forecast templates used in EAM maintenance budgeting and forecasting. Each row defines a saved set of range and filter criteria — for example a period range, an asset range, or a work order type range — that the budgeting and forecasting concurrent programs use to select the maintenance transactions to be aggregated. The table additionally stores the identifier of the concurrent request that generates the forecast output, allowing the application to track forecast execution and to associate the resulting budget figures with the originating request. From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone; it is therefore best suggested as a hub-style or reference construct anchored on its own business identifier, with the remainder of the descriptive and range columns behaving as satellite-style attributes. No foreign key dependencies are documented, which reinforces its role as a self-contained definition repository rather than a transactional link table.

Key Information Stored

The table is defined with 57 documented columns and is uniquely identified by the primary key constraint EAM_FORECASTS_PK on FORECAST_ID, a system-generated surrogate key. FORECAST_ID is the sole documented unique key; no separate business-key unique index is documented in the metadata, so FORECAST_NAME and the combination of ORGANIZATION_ID with the range criteria serve only as informal business identifiers. The most significant columns are:

• FORECAST_ID — surrogate primary key, uniquely identifying each forecast or template definition.
• ORGANIZATION_ID — the inventory organization whose maintenance activity the forecast covers.
• TEMPLATE_FLAG — indicates whether the row is a reusable template rather than an executable forecast.
• FORECAST_NAME and DESCRIPTION — user-facing identification of the definition.
• FORECAST_TYPE — the category of forecast being produced.
• PERIOD_FROM, PERIOD_TO, PERIOD_SET_NAME_FROM, PERIOD_SET_NAME_TO — the accounting period range and the period sets that bound the forecast horizon.
• REQUEST_ID — the concurrent request identifier for the forecast run, linking the definition to its execution.
• SOURCE_TEMPLATE_ID — the template from which the forecast was instantiated.
• INCLUDE_TRANSACTED and COMPLETION_DATE — flags and dates controlling which transactions are eligible for inclusion.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns for customer-defined extensions.

The remaining columns form FROM/TO range pairs for the primary selection dimensions: ACCOUNT, WIP_ACCT_CLASS, ACTIVITY, DEPARTMENT, PROJECT, ASSET_NUM, ASSET_SERIAL_NUM, ASSET_GROUP, WORK_ORDER, WORK_ORDER_TYPE, and AREA. These pairs constitute the substantive filtering logic of the forecast.

Common Use Cases and Queries

Typical usage centers on reviewing saved forecast definitions, distinguishing templates from executable forecasts, and tracing a forecast to its concurrent request output. The following patterns reflect common reporting needs:

• List active forecasts for an organization: SELECT forecast_id, forecast_name, forecast_type, period_from, period_to FROM eam.eam_forecasts WHERE organization_id = :org_id AND template_flag = 'N';
• Identify reusable templates: SELECT forecast_id, forecast_name FROM eam.eam_forecasts WHERE template_flag = 'Y';
• Trace a forecast to its concurrent request: join REQUEST_ID to FND_CONCURRENT_REQUESTS.REQUEST_ID to obtain request status, completion time, and output.
• Audit template lineage: SELECT f.forecast_name, t.forecast_name AS template_name FROM eam.eam_forecasts f, eam.eam_forecasts t WHERE f.source_template_id = t.forecast_id;
• Extract custom attributes: report ATTRIBUTE1–ATTRIBUTE15 to satisfy site-specific classification requirements.

Because the range columns are stored as FROM/TO pairs, ad hoc analysis frequently pivots on WORK_ORDER_TYPE_FROM/TO or ASSET_GROUP_FROM/TO to explain differences between forecasted and actual maintenance spend.

Related Objects

The documented relationship data shows EAM_FORECASTS as standalone, with no foreign keys. The following objects are the most significant for practical integration and reporting:

• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to retrieve forecast run status and output.
• EAM_FORECASTS (self-reference) — joined via SOURCE_TEMPLATE_ID to FORECAST_ID to resolve template lineage.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — joined on ORGANIZATION_ID to resolve organization names and operating units.
• GL_PERIOD_SETS and GL_PERIODS — joined on PERIOD_SET_NAME_FROM/TO and the period range to validate forecast horizons.
• WIP_ACCOUNTING_CLASSES — validates values used in WIP_ACCT_CLASS_FROM/TO.
• EAM_WORK_ORDERS and the work order type lookup views — provide the transaction detail the forecast ranges select against.
• FA_ASSETS and MTL_SYSTEM_ITEMS_B — supply the asset and item context for the ASSET_NUM, ASSET_GROUP, and asset serial ranges.

Because referential integrity is not enforced by the database for these associations, joins should be validated against the concurrent program logic and the organization security model in use.