Results for “activity_source_code”

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

Overview

The MTL_EAM_ASSET_ACTIVITIES_WB_V view is a reporting and integration construct in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the APPS schema and delivered under the Inventory (INV) product family. Its stated purpose is to support the Enterprise Asset Management (EAM) Activity Workbench, presenting a flattened, denormalized representation of asset activity associations that would otherwise require joining numerous maintenance, inventory, and instance-tracking tables. By consolidating lookups, item definitions, department codes, and service-date derivations into a single row per activity association, the view simplifies both the Workbench UI presentation layer and ad-hoc reporting against maintenance activities.

Its alignment with Oracle Enterprise Asset Management workflows makes it particularly relevant to shops that define preventive and corrective maintenance activities on rebuildable or rotable items. Users searching for wip_eam_activity_priority typically encounter this view because the priority codes associated with EAM activities are resolved here into user-facing meanings through the PRIORITY column.

Underlying Base Objects

Per the documented metadata, the view is constructed over the following base objects: MTL_EAM_ASSET_ACTIVITIES, EAM_ORG_MAINT_DEFAULTS, MTL_SYSTEM_ITEMS_KFV (and its underlying MTL_SYSTEM_ITEMS_B/VL), CSI_ITEM_INSTANCES, BOM_DEPARTMENTS, MFG_LOOKUPS, MTL_PARAMETERS, and the EAM_ACTIVITYUTILITIES_PVT package.

• MTL_EAM_ASSET_ACTIVITIES (EAA) — the driving table, supplying activity association IDs, asset activity IDs, effective dates, priority and cause codes, template flag, and the standard EBS WHO columns.
• EAM_ORG_MAINT_DEFAULTS (EOMD) — provides activity cause, activity type, owning department, tagging, shutdown, accounting class, and activity source codes.
• MTL_SYSTEM_ITEMS_KFV / MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_VL — provide the concatenated item segments, descriptions, and organization linkage for the activity item.
• CSI_ITEM_INSTANCES (CII) — supplies instance number, serial number, and inventory item identifier for serialized asset instances.
• BOM_DEPARTMENTS (BD) — resolves the owning department code.
• MFG_LOOKUPS (FL1–FL5) — decoded meanings for priority, activity cause, activity type, shutdown type, and activity source.
• EAM_ACTIVITYUTILITIES_PVT — a PL/SQL package invoked inline to derive NEXT_SERVICE_START_DATE and NEXT_SERVICE_END_DATE.

Key Columns

• ACTIVITY_ASSOCIATION_ID / ASSET_ACTIVITY_ID — unique identifiers for the association record and the parent activity definition.
• ORGANIZATION_ID / ACTIVITY_ORGANIZATION — maintenance organization and the item’s home organization.
• ACTIVITY / ACTIVITY_DESCRIPTION — concatenated segment and description of the activity item.
• EAM_ITEM_TYPE / ASSET_REBUILD_GROUP — asset group classification for the activity’s item.
• INVENTORY_ITEM_ID / INSTANCE_NUMBER / SERIAL_NUMBER — instance identity for serialized assets.
• PRIORITY / PRIORITY_CODE — the decoded meaning (via FL1) and the stored lookup code; this is the column pair most relevant to wip_eam_activity_priority searches.
• ACTIVITY_CAUSE / ACTIVITY_TYPE / SHUTDOWN_TYPE / ACTIVITY_SOURCE — decoded meanings with their underlying codes.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective date range of the association.
• NEXT_SERVICE_START_DATE / NEXT_SERVICE_END_DATE — derived service windows computed by EAM_ACTIVITYUTILITIES_PVT.
• TEMPLATE_FLAG — indicates whether the record is a template rather than an instance-specific activity.

Common Use Cases and Queries

The view is typically consumed for activity workbench listings, preventive maintenance reporting, and integration extracts into external CMMS or scheduling tools. A representative query to list activities by priority is shown below:

SELECT activity,
       activity_description,
       serial_number,
       priority,
       priority_code,
       next_service_start_date,
       next_service_end_date
FROM   apps.mtl_eam_asset_activities_wb_v
WHERE  organization_id = :p_org_id
AND    template_flag = 'N'
ORDER  BY priority_code, next_service_start_date;

A second common pattern filters by shutdown type and owning department for maintenance planning:

SELECT activity, shutdown_type, owning_department,
       activity_cause, activity_type
FROM   apps.mtl_eam_asset_activities_wb_v
WHERE  shutdown_type_code = 'FULL'
AND    owning_department_id = :p_dept_id;

Because NEXT_SERVICE_START_DATE and NEXT_SERVICE_END_DATE invoke PL/SQL functions per row, large unfiltered extracts may perform poorly; restricting by ORGANIZATION_ID or ACTIVITY_ASSOCIATION_ID is advisable. The view should be treated as read-only reporting infrastructure and not as a target for DML.