Results for “eam_prior_operations_v”

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

Overview

EAM_PRIOR_OPERATIONS_V is a seeded, read-only reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Enterprise Asset Management (EAM) product family and is registered as a VALID object in the EBS Technical Reference Manual (ETRM). The view presents the set of prior operations leading into a given work order operation, together with completion status, department assignment, and scheduling and actual date information. Because it joins the work order routing tables directly, it is commonly used in EAM work order reporting, operation sequencing analysis, and downstream integration extracts where users need visibility of predecessor maintenance operations.

The user search term "schedule_start_date" maps directly to the SCHEDULE_START_DATE column exposed by this view. In the ETRM column listing the view exposes OPERATION_SEQ_NUM, DESCRIPTION, DEPARTMENT_CODE, OPERATION_COMPLETED, SCHEDULE_START_DATE, SCHEDULE_END_DATE, SCHEDULE_DURATION, ACTUAL_START_DATE, ACTUAL_END_DATE, WIP_ENTITY_ID, and NEXT_OPERATION.

Underlying Base Objects

The ETRM documents the following referenced base objects, all synonyms pointing to their owning schemas:

• WIP_OPERATIONS — supplies the operation sequence number, description, department, completion flag, and the first/last unit scheduling dates used to derive SCHEDULE_START_DATE, SCHEDULE_END_DATE, and SCHEDULE_DURATION.
• WIP_OPERATION_NETWORKS — provides the work order network linkage between PRIOR_OPERATION and NEXT_OPERATION, establishing the predecessor/successor relationship.
• EAM_OP_COMPLETION_TXNS — an outer-joined table supplying actual start and end dates for completed prior operations via the most recent transaction.
• BOM_DEPARTMENTS — provides DEPARTMENT_CODE for the operation's department.
• FND_LOOKUP_VALUES — resolves the OPERATION_COMPLETED flag against the EAM_YES_NO lookup type into a display meaning.

The view text joins WIP_OPERATIONS to WIP_OPERATION_NETWORKS on WIP_ENTITY_ID and PRIOR_OPERATION = OPERATION_SEQ_NUM, outer-joins EAM_OP_COMPLETION_TXNS to the prior operation, joins BOM_DEPARTMENTS on DEPARTMENT_ID, and constrains FND_LOOKUP_VALUES by USERENV('LANG'). Because the network join is unqualified, a prior operation may appear more than once for a given work order, and callers should deduplicate when required.

Key Columns

• OPERATION_SEQ_NUM — sequence number of the prior operation within the work order routing.
• DESCRIPTION — description of that prior operation.
• DEPARTMENT_CODE — code of the department executing the operation.
• OPERATION_COMPLETED — lookup meaning derived from the EAM_YES_NO lookup (Y/N) reflecting the operation's completion state.
• SCHEDULE_START_DATE — scheduled start of the prior operation, based on FIRST_UNIT_START_DATE in WIP_OPERATIONS.
• SCHEDULE_END_DATE — scheduled completion, from LAST_UNIT_COMPLETION_DATE.
• SCHEDULE_DURATION — computed as ROUND((LAST_UNIT_COMPLETION_DATE − FIRST_UNIT_START_DATE) * 24), i.e., scheduled duration in hours.
• ACTUAL_START_DATE / ACTUAL_END_DATE — populated only when OPERATION_COMPLETED = 'Y', taken from the latest EAM_OP_COMPLETION_TXNS row; otherwise NULL.
• WIP_ENTITY_ID — work order identifier.
• NEXT_OPERATION — the successor operation sequence the prior operation feeds into.

Common Use Cases and Queries

Typical uses include generating operation-scheduling reports, computing schedule slippage by comparing scheduled versus actual dates, feeding maintenance dashboards, and extracting routing data for integration into external MES or analytics platforms. A representative query retrieving scheduled start dates for a work order is:

SELECT operation_seq_num,
       description,
       department_code,
       schedule_start_date,
       schedule_end_date,
       schedule_duration,
       operation_completed,
       next_operation
FROM   apps.eam_prior_operations_v
WHERE  wip_entity_id = :p_wip_entity_id
ORDER  BY operation_seq_num, next_operation;

To isolate operations that have actually started, filter on ACTUAL_START_DATE IS NOT NULL, or restrict by the OPERATION_COMPLETED flag via the lookup meaning. Because the view already applies language and lookup constraints, no additional FND_LOOKUP_VALUES join is required. Reports should anticipate possible duplicate prior operations arising from the WIP_OPERATION_NETWORKS join and apply DISTINCT or an aggregation where a one-row-per-operation result is expected.