Results for “eam_work_order_details_u1”

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

Overview

EAM.EAM_WORK_ORDER_DETAILS is an Oracle Enterprise Asset Management (eAM) table that stores work order detail information specific to the eAM application, complementing the core work order records held in WIP. It resides in the APPS schema under the EAM owner, is registered as VALID, and has FND Design Data registered as EAM.EAM_WORK_ORDER_DETAILS. The table is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, reflecting a transaction-data orientation. In Oracle EBS 12.1.1 and 12.2.2 it carries no date-effective (11i-style) columns; instead it uses the standard WHO audit columns and enhanced WHO columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

From a Data Vault modeling perspective, the documented FK structure indicates a satellite-leaning classification: the table hangs off a work order parent key (WIP_ENTITY_ID) and carries descriptive, context-specific attributes rather than serving as a standalone hub or a many-to-many link. This is a heuristic suggestion only, since the physical schema predates Data Vault conventions.

Key Information Stored

The table documents 29 columns spanning 12.2.2. The most operationally significant are:

• WIP_ENTITY_ID — the work order identifier and the single-column primary key component (EAM_WORK_ORDER_DETAILS_PK).
• ORGANIZATION_ID — the inventory organization that owns the work order, and the second business-key column in the unique index.
• USER_DEFINED_STATUS_ID — reference to a user-defined work order status, distinct from the WIP status.
• PENDING_FLAG and ASSIGNMENT_COMPLETE — flags controlling work order processing and assignment completion.
• MATERIAL_SHORTAGE_CHECK_DATE and MATERIAL_SHORTAGE_FLAG — support material availability planning.
• DS_SCHEDULED_FLAG — marks work orders scheduled by the Detailed Scheduling engine.
• WARRANTY_ACTIVE and WARRANTY_CLAIM_STATUS — warranty tracking for the work order.
• PM_SUGGESTED_START_DATE, PM_SUGGESTED_END_DATE, PM_BASE_METER_READING, PM_BASE_METER — preventive maintenance origination data.
• ESTIMATE_ID — foreign key to EAM_CONSTRUCTION_ESTIMATES.
• FAILURE_CODE_REQUIRED and PLANNER_MAINTENANCE — maintenance-specific control fields.
• WORKFLOW_TYPE, CYCLE_ID, SEQ_ID — workflow and cycle sequencing attributes.

Two indexes exist: the unique business-key candidate EAM_WORK_ORDER_DETAILS_U1 on (WIP_ENTITY_ID, ORGANIZATION_ID), and the non-unique EAM_WORK_ORDER_DETAILS_N1 on LAST_UPDATE_DATE, which supports incremental/CDC extraction patterns.

Common Use Cases and Queries

Typical usage covers work order status enrichment, material shortage reporting, PM-based work order generation analysis, and warranty tracking. A simple retrieval by work order and organization uses the unique index:

• SELECT * FROM eam.eam_work_order_details WHERE wip_entity_id = :p_wip_entity_id AND organization_id = :p_org_id;
• Incremental extraction for a data warehouse relies on N1: SELECT * FROM eam.eam_work_order_details WHERE last_update_date >= :p_since;
• Reporting of material shortage work orders: SELECT wip_entity_id, organization_id, material_shortage_check_date FROM eam.eam_work_order_details WHERE material_shortage_flag = 1;

These patterns are frequently joined to WIP_ENTITIES and EAM_CONSTRUCTION_ESTIMATES for full work order reporting.

Related Objects

• EAM.EAM_CONSTRUCTION_ESTIMATES — referenced via ESTIMATE_ID; join on estimate_id.
• WIP_ENTITIES — the parent work order header; join on wip_entity_id.
• WIP_DISCRETE_JOBS / WIP_REPETITIVE_SCHEDULES — job-level detail for the same wip_entity_id.
• EAM_WORK_ORDERS (and related eAM views) — core eAM work order extension views built over these details.
• EAM_ORGANIZATION_DEFINITIONS — organization context for ORGANIZATION_ID.
• EAM_WORK_ORDER_STATUSES / lookups — resolves USER_DEFINED_STATUS_ID.