Results for “eam_resource_import”

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

Overview

EAM_RESOURCE_IMPORT is a table owned by the EAM schema within the Oracle E-Business Suite Enterprise Asset Management module. It functions as a staging and interface structure for work order resource records, supporting the bulk import of resource assignments, usage rates, and related scheduling attributes into Oracle EAM. In Oracle EBS 12.1.1 and 12.2.2, the table is documented in the ETRM physical schema with 49 columns and is classified as VALID.

From a heuristic Data Vault modeling perspective, the metadata's relationship analysis classifies EAM_RESOURCE_IMPORT as a standalone object rather than a hub, link, or satellite. This classification reflects its role as a transient import interface rather than a core master or transactional entity. Records within the table typically represent inbound resource data that is validated, transformed, and ultimately posted into the production work order resource tables.

The table's descriptive label, "Work Order Resource," indicates that its principal purpose is to capture resource-level attributes associated with work orders prior to or during import processing.

Key Information Stored

Each row in EAM_RESOURCE_IMPORT is uniquely identified by the surrogate primary key ROW_ID. The ROW_ID column carries a foreign key reference to CS_SYSTEMS_ALL_B_TEMP, which supports the temporary systems/interface infrastructure used during import. The following columns carry the most significant business content:

• HEADER_ID — identifies the import batch or interface header group.
• GROUP_ID — the batch grouping identifier used to process related import rows together.
• WIP_ENTITY_ID and ORGANIZATION_ID — link the resource row to a specific work order and operating organization.
• OPERATION_SEQ_NUM and RESOURCE_SEQ_NUM — the operation and resource sequence positions within the work order routing.
• RESOURCE_ID — the specific resource being assigned.
• UOM_CODE and BASIS_TYPE — the unit of measure and the basis on which resource usage is calculated.
• USAGE_RATE_OR_AMOUNT and ASSIGNED_UNITS — the rate or quantity of the resource and the number of units assigned.
• APPLIED_RESOURCE_UNITS and APPLIED_RESOURCE_VALUE — the applied quantity and monetary value resulting from resource consumption.
• START_DATE and COMPLETION_DATE — the scheduled window for the resource assignment.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, identifying the responsible department.
• TRANSACTION_TYPE and RETURN_STATUS — indicate the nature of the import transaction and the outcome of its processing.

Standard EBS audit and descriptive columns are also present, including LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and the fifteen ATTRIBUTE columns with ATTRIBUTE_CATEGORY for extensibility.

Common Use Cases and Queries

Typical usage centers on validating inbound resource import batches before posting. A common diagnostic query joins the import rows to their department to verify referenced values:

SELECT r.header_id, r.wip_entity_id, r.resource_id, r.assigned_units, r.transaction_type, d.department_code FROM eam.eam_resource_import r, bom.bom_departments d WHERE r.department_id = d.department_id AND r.group_id = :p_group_id;

Reconciliation reporting identifies rows that have not yet been successfully applied, filtering on RETURN_STATUS to surface errors for correction. Batch-level summaries group by HEADER_ID and GROUP_ID to report counts and total applied resource value. Interface monitoring queries compare the applied units against the assigned units to detect discrepancies before committing data to production tables.

Related Objects

The table's foreign key definitions establish primary relationships with the following objects:

• CS_SYSTEMS_ALL_B_TEMP — referenced through ROW_ID, supporting the temporary import infrastructure.
• BOM_DEPARTMENTS — referenced through DEPARTMENT_ID, providing departmental context for each resource row.
• EAM_RESOURCE_IMPORT_TEMP and related EAM interface staging tables — companion structures in the same import workflow.
• WIP_ENTITIES — the work order entity referenced via WIP_ENTITY_ID.
• BOM_RESOURCES — the resource definition referenced via RESOURCE_ID.
• EAM_WORK_ORDER_RESOURCES — the production table into which validated rows are ultimately posted.

These objects, together with the EAM import programs and concurrent processes, form the complete resource import ecosystem within Oracle Enterprise Asset Management.