Results for “eam_work_order_import”

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

Overview

The EAM_WORK_ORDER_IMPORT table is the staging and interface table used by Oracle Enterprise Asset Management (EAM) to load work orders into Oracle E-Business Suite from external sources. It belongs to the EAM schema and is documented in ETRM 12.2.2 with 96 columns. The table functions as the inbound conduit for bulk or programmatic work order creation, whether sourced from third-party maintenance systems, legacy migrations, spreadsheet uploads, or custom integrations. Rows are inserted into this table with a batch identifier, processed by the Work Order Import concurrent program, and ultimately transferred into the live EAM work order tables (WIP entities, operations, resources, and material requirements) with status feedback written back to the import row.

From a heuristic Data Vault modeling perspective, the ETRM relationship metadata classifies this object as a standalone table. That classification reflects the absence of a normalized parent-child dependency within the FK graph; functionally, however, the import table is best understood as a transient staging satellite around the EAM work order hub, carrying descriptive, scheduling, cost, and status attributes that describe an intended work order before it becomes an authoritative transaction record.

Key Information Stored

The row-level surrogate identifier is HEADER_ID, while GROUP_ID groups rows into a single import batch and ROW_ID provides the cross-reference back to the source record via CS_SYSTEMS_ALL_B_TEMP. The principal business-key candidates for the resulting work order are WIP_ENTITY_NAME combined with ORGANIZATION_ID; once processed, WIP_ENTITY_ID holds the generated work order identifier.

Key descriptive and control columns include:

• ASSET_NUMBER, ASSET_GROUP_ID, REBUILD_ITEM_ID, REBUILD_SERIAL_NUMBER — asset or rebuild context for the work order.
• MAINTENANCE_OBJECT_ID, MAINTENANCE_OBJECT_TYPE, MAINTENANCE_OBJECT_SOURCE — the maintained object and its origin.
• CLASS_CODE, WORK_ORDER_TYPE, STATUS_TYPE, ACTIVITY_TYPE, ACTIVITY_CAUSE — work order categorization and lifecycle state.
• JOB_QUANTITY, DATE_RELEASED, REQUESTED_START_DATE, DUE_DATE, SCHEDULED_START_DATE, SCHEDULED_COMPLETION_DATE — quantities and scheduling.
• PM_SCHEDULE_ID, SCHEDULE_GROUP_ID — linkage to preventive maintenance scheduling.
• OWNING_DEPARTMENT, PRIORITY, FIRM_PLANNED_FLAG, SHUTDOWN_TYPE, NOTIFICATION_REQUIRED, TAGOUT_REQUIRED — operational and safety attributes.
• PROCESS_STATUS, RETURN_STATUS, SOURCE_CODE, TRANSACTION_TYPE — import processing feedback and row disposition.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, USER_ID, RESPONSIBILITY_ID — concurrent program and audit context.

Common Use Cases and Queries

The most common scenario is monitoring an inbound work order load. Administrators query the table to confirm that all rows in a batch completed successfully:

• SELECT header_id, wip_entity_name, process_status, return_status FROM eam.eam_work_order_import WHERE group_id = :p_group_id;
• Identifying failed rows for re-submission: WHERE process_status = 'ERROR' or where RETURN_STATUS is not null.
• Reconciling source to target using ROW_ID against CS_SYSTEMS_ALL_B_TEMP.
• Reporting on work order demand, asset coverage, and PM-driven loads by joining PM_SCHEDULE_ID to EAM_PM_SCHEDULINGS.
• Auditing who or which concurrent program loaded the batch via USER_ID, RESPONSIBILITY_ID, and REQUEST_ID.

Because PROCESS_STATUS and RETURN_STATUS capture per-row outcomes, these columns are the primary filter for operational dashboards and error resolution workflows.

Related Objects

The following objects are significant to this table based on the ETRM foreign key metadata:

• EAM_PM_SCHEDULINGS — joined on PM_SCHEDULE_ID; provides the PM definition driving scheduled work order generation.
• WIP_SCHEDULE_GROUPS — joined on SCHEDULE_GROUP_ID; groups related work orders for scheduling.
• CS_SYSTEMS_ALL_B_TEMP — joined on ROW_ID; the staging source of originating records.
• WIP_ENTITIES — the target of a successful import, populated with WIP_ENTITY_ID and WIP_ENTITY_NAME.
• EAM_WORK_ORDERS and related EAM work order interfaces — downstream recipients of imported definitions.
• FND_CONCURRENT_REQUESTS / FND_USER — resolved through REQUEST_ID, PROGRAM_ID, and USER_ID for audit tracking.

Together these relationships position EAM_WORK_ORDER_IMPORT as the bridge between external maintenance demand and the transactional EAM work order framework.