Search Results work_order_type_disp




Overview
Explore in AI Chat

Overview

APPS.MTL_EAM_ASSET_ACTIVITIES_V is a reporting and integration view within Oracle E-Business Suite Enterprise Asset Management (EAM). It presents maintenance activities defined against rebuildable or rotable assets, joining the transactional activity definition held in MTL_EAM_ASSET_ACTIVITIES with organization-level maintenance defaults, inventory item master information, and CSI instance data. The view is available in both 12.1.1 and 12.2.2 and is owned by the APPS schema, making it accessible to custom reports, Oracle Discoverer workbooks, XML Publisher data definitions, and interface programs that need a denormalized read of asset activity metadata without navigating the individual base tables.

The presence of the WORK_ORDER_TYPE_DISP column, derived from MFG_LOOKUPS via the EAM_WORK_ORDER_TYPE lookup type, indicates that the view is intended for display-oriented reporting. The "_DISP" suffix signals that the value has been translated through the lookup meaning rather than exposing the raw code (eomd.WORK_ORDER_TYPE).

Underlying Base Objects

The view is constructed over the following documented base objects, all referenced through APPS synonyms except where noted:

  • MTL_EAM_ASSET_ACTIVITIES — the primary transactional table holding asset activity associations and attributes.
  • EAM_ORG_MAINT_DEFAULTS — organization-level EAM maintenance defaults, supplying activity type, cause, source, shutdown type, work order type, planner, and department references.
  • MTL_SYSTEM_ITEMS_VL and MTL_SYSTEM_ITEMS_B — provide the activity's item concatenated segments, description, and item attributes.
  • MTL_SYSTEM_ITEMS_KFV — supplies the asset rebuild group concatenated segments.
  • CSI_ITEM_INSTANCES — provides instance number, serial number, and inventory item ID for the asset instance.
  • BOM_DEPARTMENTS — resolves the owning department code.
  • MTL_PARAMETERS — organization parameters joined to scope the item defaults.
  • MFG_LOOKUPS (view) — joined eight times (aliases fl1 through fl7) to translate code columns into their lookup meanings.

Joins are driven by inventory_item_id, organization_id, and lookup_type, ensuring the view returns activities scoped to a valid EAM organization.

Key Columns

The view exposes a broad set of columns grouped as follows:

  • Identity: row_id, activity_association_id, asset_activity_id, maintenance_object_id, maintenance_object_type, creation_organization_id.
  • Asset context: organization_id, activity (concatenated segments), activity_description, instance_number, inventory_item_id, serial_number.
  • Effective dating: start_date_active, end_date_active, last_service_start_date, last_service_end_date.
  • Classification (lookup-driven): priority, activity_cause, activity_type, shutdown_type, activity_source, WORK_ORDER_TYPE_DISP, PLANNER_MAINTENANCE_DISP.
  • Raw codes: priority_code, activity_cause_code, activity_type_code, shutdown_type_code, activity_source_code, WORK_ORDER_TYPE, PLANNER_MAINTENANCE.
  • Operational flags: tagging_required_flag, FIRM_PLANNED_FLAG, PLAN_MAINTENANCE, NOTIFICATION_REQUIRED, template_flag (from eaa.tmpl_flag).
  • Ownership: owning_department, owning_department_id, accounting_class_code, asset_rebuild_group, eam_item_type.
  • Audit/WHO columns: creation_date, created_by, last_update_date, last_updated_by, last_update_login, request_id, program_application_id, program_id, program_update_date, attribute_category, attribute1 through attribute15.

Common Use Cases and Queries

Typical usage includes activity listing reports filtered by organization, rebuilding activity dashboards, and integration extracts that must surface the display value of WORK_ORDER_TYPE. A representative query returning activities whose work order type is "Work Order" within a specific organization:

  • SELECT activity, activity_description, serial_number, activity_type, WORK_ORDER_TYPE_DISP, PLANNER_MAINTENANCE_DISP, start_date_active, end_date_active FROM apps.mtl_eam_asset_activities_v WHERE organization_id = :org_id AND WORK_ORDER_TYPE_DISP = 'Work Order' ORDER BY activity;

To identify preventive activities for a rebuildable item:

  • SELECT activity, WORK_ORDER_TYPE_DISP, activity_source, activity_cause, priority FROM apps.mtl_eam_asset_activities_v WHERE inventory_item_id = :item_id AND PLAN_MAINTENANCE = 'Y';

Because the view joins several master and reference tables, queries should always be constrained by organization_id or inventory_item_id to keep result sets selective. The view is read-only and is not a valid target for DML through the APPS schema.