Search Results activity_source

Overview

MTL_EAM_ASSET_ACTIVITIES_V is an APPS-owned database view in Oracle E-Business Suite (documented as valid in both 12.1.1 and 12.2.2) that exposes Enterprise Asset Management (EAM) activity associations in a fully denormalized, reporting-ready form. It belongs to the INV — Inventory product family and is defined in the APPS schema. Its stated purpose in the ETRM repository is "View for Asset Activities."

Functionally, the view answers the question: which maintenance activities — the asset activities defined in MTL_EAM_ASSET_ACTIVITIES — are associated with which maintenance objects (assets, rebuildable items, or rebuild groups), and what are the descriptive attributes of those activities? Rather than requiring a report or integration to join EAM activity tables to item master, maintenance defaults, item instances, and lookup tables, this view performs those joins internally and presents a single flat row per activity association. Because it resolves the user-facing ACTIVITY concatenated segment and its ACTIVITY_DESCRIPTION, it is frequently the object reached for when a report or query needs to display an activity by name or description rather than by internal ID. It is read-only and must never be used as a DML target.

Underlying Base Objects

The view is defined over the following documented base objects:

• MTL_EAM_ASSET_ACTIVITIES — the primary EAM table holding activity associations (driver alias EAA). Supplies ACTIVITY_ASSOCIATION_ID, ASSET_ACTIVITY_ID, date ranges, priority, maintenance object reference, template flag, and the standard WHO/audit and DFF columns.
• MTL_SYSTEM_ITEMS_KFV — key flexfield view over MTL_SYSTEM_ITEMS_B, used twice: once for the activity item and once, as alias AG, for the asset rebuild group.
• MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_VL — the underlying item base table and its translated (VL) view that back the KFV access paths.
• EAM_ORG_MAINT_DEFAULTS — organization-level maintenance defaults, joined on ORGANIZATION_ID and on OBJECT_ID / OBJECT_TYPE = 60, supplying the owning department, accounting class, tagging-required flag, shutdown type, and activity cause/type/source codes.
• BOM_DEPARTMENTS — source of OWNING_DEPARTMENT by DEPARTMENT_CODE.
• CSI_ITEM_INSTANCES — installed base instance records, providing INSTANCE_NUMBER, SERIAL_NUMBER, and INVENTORY_ITEM_ID for the maintained asset.
• MFG_LOOKUPS — joined five times (FL1–FL5) to decode PRIORITY_CODE, ACTIVITY_CAUSE_CODE, ACTIVITY_TYPE_CODE, SHUTDOWN_TYPE_CODE, and ACTIVITY_SOURCE_CODE into their MEANING text.
• MTL_PARAMETERS — organization parameters, referenced to enforce organization context.

The joins are non-optional in the documented definition: the view filters on EAA.MAINTENANCE_OBJECT_TYPE = 3 and constrains EAM_ORG_MAINT_DEFAULTS to OBJECT_TYPE = 60, so only activity associations whose maintenance object is an asset (item) are returned. Each association is tied back to a specific organization and to the item master record of the activity item.

Key Columns

• ACTIVITY_DESCRIPTION — the DESCRIPTION of the activity item from MTL_SYSTEM_ITEMS_KFV. This is the most commonly searched column; users search for "activity_description" to locate activities by their business name in reports and integrations.
• ACTIVITY — the CONCATENATED_SEGMENTS of the activity item, i.e., the fully qualified item flexfield value.
• ASSET_ACTIVITY_ID / ACTIVITY_ASSOCIATION_ID — the inventory item identifier of the activity and the surrogate key of the association row; the latter is the logical primary key.
• ORGANIZATION_ID / CREATION_ORGANIZATION_ID — the organization in which the association is valid and that in which it was created.
• INSTANCE_NUMBER, SERIAL_NUMBER, INVENTORY_ITEM_ID — identity of the installed asset instance from CSI_ITEM_INSTANCES.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the association.
• PRIORITY, ACTIVITY_CAUSE, ACTIVITY_TYPE, SHUTDOWN_TYPE, ACTIVITY_SOURCE — decoded MEANING text from MFG_LOOKUPS; the corresponding raw codes (PRIORITY_CODE, ACTIVITY_CAUSE_CODE, ACTIVITY_TYPE_CODE, SHUTDOWN_TYPE_CODE, ACTIVITY_SOURCE_CODE) are also exposed.
• OWNING_DEPARTMENT / OWNING_DEPARTMENT_ID, ACCOUNTING_CLASS_CODE, TAGGING_REQUIRED_FLAG — maintenance defaults relevant to work execution and accounting.
• ASSET_REBUILD_GROUP — concatenated segments of the rebuild group item, where applicable.
• TEMPLATE_FLAG — the TEMPLATE_FLAG of the association row.
• LAST_SERVICE_START_DATE / LAST_SERVICE_END_DATE — most recent service interval recorded for the association.
• ROW_ID — the ROWID of the MTL_EAM_ASSET_ACTIVITIES row, provided for direct row addressing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE and the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — descriptive flexfield and audit context.

Common Use Cases and Queries

The view supports EAM reporting, extensions, and interface extracts. Typical scenarios include listing all activities defined for a given asset, resolving an activity name from its description, extracting activity definitions for an external maintenance system, and joining maintenance history to activity metadata.

SELECT activity, activity_description, priority, activity_type
FROM   apps.mtl_eam_asset_activities_v
WHERE  organization_id = 204
AND    UPPER(activity_description) LIKE '%INSPECT%';

To report activities for a specific asset instance:

SELECT instance_number, serial_number, activity, activity_description,
       activity_cause, activity_type, owning_department
FROM   apps.mtl_eam_asset_activities_v
WHERE  instance_number = 'ASSET-10023'
AND    SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                    AND NVL(end_date_active, SYSDATE);

To exclude template rows when listing live activity definitions:

SELECT activity_description, activity_source, last_service_start_date
FROM   apps.mtl_eam_asset_activities_v
WHERE  template_flag = 'N'
AND    organization_id = :p_org_id;

Because MFG_LOOKUPS is joined five times, the view carries meaningful overhead; queries should always filter by ORGANIZATION_ID, ASSET_ACTIVITY_ID, or ACTIVITY_ASSOCIATION_ID to drive the joins efficiently. The view returns no rows for activity associations that are not tied to an asset-type maintenance object, and consumers should treat ORGANIZATION_ID as a mandatory predicate in multi-org deployments.