Results for “workflow_type”

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

Overview

EAM_WORK_ORDER_DETAILS is a table in the EAM (Enterprise Asset Management) schema of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It holds supplementary work order attributes that extend the core work order record maintained by Oracle Work in Process for maintenance activities. The object is documented by ETRM as VALID in the EAM product module, with a primary key constraint named EAM_WORK_ORDER_DETAILS_PK defined on WIP_ENTITY_ID.

The table carries a heuristic Data Vault classification of satellite-leaning, mined from its foreign key structure. Within a Data Vault model, this suggests treating the table as a satellite attached to a work order hub keyed on the WIP entity, rather than as an independent hub or a link between business entities. This classification reflects the table's role as a store of descriptive, non-key context for an existing work order.

Key Information Stored

The documented physical schema for 12.2.2 contains 29 columns. The most operationally significant are:

• WIP_ENTITY_ID — the primary key column and the surrogate identifier of the work order header this detail row describes.
• ORGANIZATION_ID — the inventory organization context; combined with WIP_ENTITY_ID it forms the unique business-key candidate EAM_WORK_ORDER_DETAILS_U1.
• USER_DEFINED_STATUS_ID — the user-defined work order status referenced by maintenance workflows.
• PENDING_FLAG, MATERIAL_SHORTAGE_FLAG, and MATERIAL_SHORTAGE_CHECK_DATE — indicate whether the work order is held and whether a material availability check has been performed and when.
• WORKFLOW_TYPE — identifies the workflow context applied to the order.
• WARRANTY_ACTIVE and WARRANTY_CLAIM_STATUS — track warranty coverage and claim processing state.
• ASSIGNMENT_COMPLETE — records completion of work order assignment.
• PM_SUGGESTED_START_DATE, PM_SUGGESTED_END_DATE, PM_BASE_METER, and PM_BASE_METER_READING — carry preventive maintenance scheduling and meter baselines.
• FAILURE_CODE_REQUIRED — flags whether failure capture is mandatory on completion.
• ESTIMATE_ID — foreign key to EAM_CONSTRUCTION_ESTIMATES.
• PLANNER_MAINTENANCE, CYCLE_ID, SEQ_ID, and DS_SCHEDULED_FLAG — support maintenance planning and scheduling logic.
• Standard WHO columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical reporting joins this table to WIP_ENTITIES on WIP_ENTITY_ID to combine work order detail flags with the work order header. A representative query for material-shortages in a given organization:

• SELECT d.wip_entity_id, d.material_shortage_flag, d.pending_flag FROM eam.eam_work_order_details d WHERE d.organization_id = :org AND d.material_shortage_flag = 'Y';
• Warranty tracking: filter on WARRANTY_ACTIVE and WARRANTY_CLAIM_STATUS to report open claims.
• PM compliance: compare PM_SUGGESTED_START_DATE against actual dates from the work order header.
• Failure analysis readiness: list orders where FAILURE_CODE_REQUIRED = 'Y' and completion is pending.

Related Objects

• EAM_CONSTRUCTION_ESTIMATES — referenced via ESTIMATE_ID, linking work orders to construction estimates.
• WIP_ENTITIES — the work order header joined on WIP_ENTITY_ID and ORGANIZATION_ID.
• WIP_DISCRETE_JOBS — associated maintenance job records for the same WIP entity.
• EAM_WORK_ORDERS and related EAM work order views/APIs — present the assembled work order for maintenance users.
• EAM_USER_DEFINED_STATUSES — resolves USER_DEFINED_STATUS_ID to the status definition.
• PER_ALL_PEOPLE_F — resolves planner and assignment personnel references.