Results for “eam_operations_details_v”

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

Overview

APPS.EAM_OPERATIONS_DETAILS_V is a reporting view within the Enterprise Asset Management (EAM) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to provide details about the operations of a work order. In EAM, a work order is modeled on a discrete job, and each job carries one or more operations, which in turn carry resources and resource instances. This view flattens that hierarchy — work order header, operation, operation resource, resource instance, and associated asset instance — into a single denormalized row set suitable for operational reporting, dashboards, and interface extracts.

The view is read-only and contains no business logic beyond joins, NVL defaults, and scalar subqueries for lookup descriptions. It is owned by the APPS schema and is intended to be queried directly, typically filtered by organization, work order, or asset number.

Underlying Base Objects

Per the documented metadata, the view is defined over the following base objects, all referenced through APPS synonyms or views:

• WIP_ENTITIES — the work order entity header (source of WIP_ENTITY_NAME).
• WIP_DISCRETE_JOBS — the work order detail record (description, asset group, rebuild item, primary item, maintenance object).
• WIP_OPERATIONS — the operation records attached to the work order, including sequence number, dates, department, and the OPERATION_COMPLETED flag.
• WIP_OPERATION_RESOURCES — resources assigned to each operation.
• WIP_OP_RESOURCE_INSTANCES — the resource instance rows linking a resource to an asset instance.
• BOM_RESOURCE_EMPLOYEES — the employee/resource association supplying person identifiers.
• CSI_ITEM_INSTANCES — the installed asset instance (asset number and instance ID).
• MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_B_KFV — item master and its key flexfield concatenated segments, used for asset group, activity, and EAM asset type lookups.
• BOM_DEPARTMENTS — department code.
• MFG_LOOKUPS — lookup meanings for priority and asset type.

The joins are driven from WIP_DISCRETE_JOBS and WIP_OPERATIONS outward, so a work order with multiple operations and resources returns one row per operation/resource/resource-instance combination.

Key Columns

• WIP_ENTITY_ID, WIP_ENTITY_NAME — work order identifier and number.
• ORGANIZATION_ID — the asset organization owning the work order.
• OPERATION_SEQ_NUM, OP_DESCRIPTION — operation sequence and description.
• OPERATION_COMPLETED — the completion flag for the operation, defaulted to 'N' via NVL. This is the column users most often search for when auditing whether an operation has been closed.
• FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, DUE_DATE — scheduling and completion dates at operation level.
• ASSET_NUMBER, INSTANCE_ID — the installed asset instance.
• ASSET_GROUP, ASSET_GROUP_ID, ACTIVITY, ACTIVITY_ID — asset group and activity item identifiers and concatenated segments.
• PRIORITY, ASSETTYPE, DEPARTMENT_ID, DEPARTMENT_CODE — classification and responsibility attributes.
• STATUS_ASSIGN, STATUS_DEPARTMENT — status descriptors, the former hard-coded as 'ASSIGNED'.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

The principal use case is tracking operation status by work order and asset. A typical query returning open operations is:

• SELECT wip_entity_name, operation_seq_num, op_description, operation_completed, due_date FROM eam_operations_details_v WHERE organization_id = :org AND NVL(operation_completed,'N') = 'N' ORDER BY wip_entity_name, operation_seq_num;

Asset-centric reporting joins the view on ASSET_NUMBER to summarize maintenance history per asset instance:

• SELECT asset_number, wip_entity_name, operation_seq_num, first_unit_completion_date FROM eam_operations_details_v WHERE asset_number = :asset_number ORDER BY first_unit_completion_date DESC;

Because the view exposes resource sequence, resource ID, person ID, and department, it also supports labor and resource utilization extracts, and it is frequently used as a source in custom concurrent programs, BI Publisher reports, and inbound/outbound interfaces that synchronize EAM work order operations with external maintenance systems. When querying, filter on ORGANIZATION_ID and WIP_ENTITY_ID for performance, since the view joins several high-volume WIP and CSI tables.