Search Results activity_organization




Overview

APPS.MTL_EAM_ASSET_ACTIVITIES_WB_V is a supplementary view in Oracle E-Business Suite, owned by the APPS schema and registered under FND Design Data as INV.MTL_EAM_ASSET_ACTIVITIES_WB_V. Consistent with Oracle's convention for "WB" (workbench) views, it is designed to simplify forms coding rather than to serve as a stable public interface. The ETRM documentation explicitly warns that Oracle does not recommend querying or altering data through this view, as its definition may change dramatically across minor or major releases. Its core purpose is to denormalize Enterprise Asset Management (EAM) activity associations — the linkage between rebuildable assets and the maintenance activities assigned to them — so that the Asset Activities workbench form can display decoded, human-readable information without embedding complex joins.

Because the view joins organization, item, instance, department, and lookup data, it is a convenient read-only source for reporting on EAM activity assignments. The user search term "activity_organization" maps directly to the ORGANIZATION_ID column, which identifies the inventory organization in which the asset activity association is defined. This makes the view relevant to multi-organization EAM deployments where activities must be reported per maintenance organization.

Underlying Base Objects

The documented referenced base objects are MTL_EAM_ASSET_ACTIVITIES (the primary table of asset-to-activity associations), MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_KFV (item definition and concatenated segment descriptions), MTL_SYSTEM_ITEMS_VL (translated item descriptions), CSI_ITEM_INSTANCES (asset instance and serial number detail), BOM_DEPARTMENTS (owning department), MTL_PARAMETERS (organization defaults), EAM_ORG_MAINT_DEFAULTS (EAM-specific organization maintenance defaults), MFG_LOOKUPS (lookup meanings for priority, cause, type, and shutdown type), and EAM_ACTIVITYUTILITIES_PVT (the utility package supplying derived activity attributes). These sources are exposed through APPS synonyms and public views rather than directly referenced. Together they resolve foreign keys and lookup codes into descriptive values.

Key Columns

Common Use Cases and Queries

Typical uses include EAM activity assignment reports, asset maintenance plans by organization, and lookups resolved for audit. A representative query filters activities for a given organization:

SELECT activity_association_id, organization_id, activity, activity_description, instance_number, serial_number, priority, activity_type FROM apps.mtl_eam_asset_activities_wb_v WHERE organization_id = :p_org_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);

Because the view is informational and release-fragile, production integrations should query the base tables MTL_EAM_ASSET_ACTIVITIES and MTL_SYSTEM_ITEMS_B directly, reserving this view for form-level or diagnostic reporting.