Results for “mtl_eam_activity_type”

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

Overview

APPS.EAM_FORECAST_WORK_ORDER_V is an Oracle Enterprise Asset Management (eAM) internal view that consolidates forecast work order information with associated asset, activity, and scheduling attributes. It is classified in the ETRM repository as an Oracle Internal Use Only object, carrying an explicit warning that Oracle Corporation does not support direct access to application data through this view except from standard Oracle Applications programs. The view is registered as VALID and is owned by the APPS schema, a characteristic shared by numerous eAM and Enterprise Asset Management reporting artifacts.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as an integration and reporting surface for forecasted maintenance work orders — that is, work order projections generated ahead of execution and linked to assets, asset groups, asset activities, and preventive maintenance schedules. Because the user search term "asset_activity" maps directly to the ASSET_ACTIVITY column exposed by this view, the object is commonly consulted when eAM users need to correlate forecast work orders with the activity classification recorded against an asset. The view type is documented as Internal, indicating it is consumed primarily by seeded eAM forms, concurrent programs, and Oracle-provided logic rather than by customer-developed reports.

Underlying Base Objects

The ETRM metadata lists the following dependencies for APPS.EAM_FORECAST_WORK_ORDER_V: BOM_DEPARTMENTS, CSI_ITEM_INSTANCES, EAM_FORECAST_WDJ, EAM_ORG_MAINT_DEFAULTS, FND_PROFILE (package), MFG_LOOKUPS, MTL_EAM_LOCATIONS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_KFV, PA_TASK_UTILS (package), PJM_TASKS_V, and WIP_ENTITIES. All base tables are referenced through APPS synonyms.

The central driving object is EAM_FORECAST_WDJ, which stores forecast work order definitions. It is joined to WIP_ENTITIES for the work order entity name and identifier, CSI_ITEM_INSTANCES for asset instance details, and MTL_SYSTEM_ITEMS_KFV for item information. Asset master attributes such as asset number, group, activity, and location are resolved through CSI_ITEM_INSTANCES and MTL_EAM_LOCATIONS. Department and organization context comes from BOM_DEPARTMENTS, MTL_PARAMETERS, and EAM_ORG_MAINT_DEFAULTS. Organizational profile values are retrieved via the FND_PROFILE package. Lookup decoding across activity type, activity cause, work order type, and related fields relies on MFG_LOOKUPS. Project and task linkage uses the PJM_TASKS_V view and the PA_TASK_UTILS package. The column list confirms that asset activity is expressed through the ASSET_ACTIVITY column (VARCHAR2, length 40), which is a code derived from the asset definition rather than a free-text field.

Key Columns

The view exposes a mix of work order identifiers, asset attributes, and classification codes.

• FORECAST_ID — numeric forecast identifier linking the row to the originating forecast definition.
• WIP_ENTITY_ID and WIP_ENTITY_NAME — the WIP job identifier and name representing the work order.
• ORGANIZATION_ID — the inventory organization under which the work order and asset reside.
• ASSET_NUMBER, ASSET_DESCRIPTION, ASSET_GROUP — the asset identity and its grouping classification.
• ASSET_ACTIVITY — the asset activity code associated with the work order, the column most relevant to the "asset_activity" search.
• ASSET_LOCATION — the asset area or location designation.
• WORK_ORDER_TYPE — the type of work order (for example, preventive or corrective).
• START_DATE and COMPLETION_DATE — the scheduled start and completion dates for the forecast work order.
• ACTIVITY_TYPE and ACTIVITY_CAUSE — activity classification and reason codes decoded from lookups.
• OWNING_DEPARTMENT and CLASS_CODE — the responsible department and work order class.
• PLAN_MAINTENANCE — flag indicating whether the work order arises from planned maintenance.
• PROJECT and TASK — project and project task references where the work order is project-driven.
• PM_SCHEDULE_ID and ACTIVITY_SOURCE — preventive maintenance schedule identifier and the source of the activity.

Common Use Cases and Queries

The view is typically used to inspect forecasted work order content before execution, to reconcile forecasts with asset activity classifications, and to feed downstream eAM planning queries. Because it is marked Oracle Internal Use Only, customers should treat it as read-only and be aware that its definition may change without notice; supported reporting should normally be built on the seeded eAM work order views or on the base tables directly.

A common query pattern filters by forecast and organization and returns the asset activity alongside work order dates:

• SELECT FORECAST_ID, WIP_ENTITY_NAME, ASSET_NUMBER, ASSET_ACTIVITY, WORK_ORDER_TYPE, START_DATE, COMPLETION_DATE FROM APPS.EAM_FORECAST_WORK_ORDER_V WHERE ORGANIZATION_ID = :org_id ORDER BY START_DATE;

A second pattern aggregates forecast work orders by asset activity to support maintenance planning:

• SELECT ASSET_ACTIVITY, PLAN_MAINTENANCE, COUNT(*) FROM APPS.EAM_FORECAST_WORK_ORDER_V WHERE ORGANIZATION_ID = :org_id GROUP BY ASSET_ACTIVITY, PLAN_MAINTENANCE;

A third pattern links forecasts to preventive maintenance schedules and project tasks for reporting:

• SELECT WIP_ENTITY_NAME, PM_SCHEDULE_ID, PROJECT, TASK, ACTIVITY_SOURCE FROM APPS.EAM_FORECAST_WORK_ORDER_V WHERE PM_SCHEDULE_ID IS NOT NULL;

These queries should be executed with appropriate organization and security context, since the view relies on MTL_PARAMETERS and FND_PROFILE to resolve organizational defaults.