Results for “eam_material_import”

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

Overview

The EAM.EAM_MATERIAL_IMPORT table is an Enterprise Asset Management (EAM) material import staging table in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as an interim holding and processing structure through which material requirement records are loaded into Oracle EAM work order and maintenance execution flows. Records are typically populated by external systems, spreadsheets, or custom loaders and then validated or transferred into the operational work management tables. The table is owned by the EAM schema and holds 49 documented columns in the 12.2.2 data model.

From a Data Vault modeling perspective, the mined heuristic classification for this object is standalone. This suggests the table functions as an isolated staging or interface structure rather than a conformed hub, link, or satellite. Any Data Vault implementation should treat it accordingly—retaining identifying columns as business keys and the remaining attributes as descriptive context, with no implied dependent relationships beyond those evidenced by its foreign keys.

Key Information Stored

The table is structured around a header-level grouping and work order context, with material line detail attached to each record. The primary technical identifier is ROW_ID, which is documented as a foreign key to CS_SYSTEMS_ALL_B_TEMP and functions as the surrogate identity for the row within the import framework. HEADER_ID and GROUP_ID serve as the principal business-key candidates for grouping imported records into a logical import set or batch.

The work execution context is carried by WIP_ENTITY_ID, ORGANIZATION_ID, and OPERATION_SEQ_NUM, identifying the work order, inventory organization, and routing operation for which material is required. Material identity is defined by INVENTORY_ITEM_ID and COMPONENT_SEQUENCE_ID, supported by QUANTITY_PER_ASSEMBLY for the per-unit requirement. Demand information is captured through DATE_REQUIRED, REQUIRED_QUANTITY, REQUESTED_QUANTITY, RELEASED_QUANTITY, and QUANTITY_ISSUED, enabling tracking of material status across the request and issue lifecycle.

Supply-side attributes include SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID, WIP_SUPPLY_TYPE, VENDOR_ID, SUGGESTED_VENDOR_NAME, UNIT_PRICE, and TRANSACTION_TYPE. Planning flags such as MRP_NET_FLAG, MPS_REQUIRED_QUANTITY, and MPS_DATE_REQUIRED support planning integration. The DEPARTMENT_ID links to BOM_DEPARTMENTS and identifies the responsible manufacturing or maintenance department. Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, and others) and the ATTRIBUTE1–15 flexfields provide extensibility and change tracking.

Common Use Cases and Queries

Typical usage centers on batch loading and reconciliation of material requirements for maintenance work orders. A common query pattern retrieves all pending import rows for a specific work order and organization:

SELECT header_id, wip_entity_id, inventory_item_id, required_quantity, date_required
  FROM eam.eam_material_import
 WHERE wip_entity_id = :p_wip_entity_id
   AND organization_id = :p_org_id;

Reporting use cases include identifying shortages by comparing required versus issued quantities, isolating records not yet assigned a vendor for procurement action, and reviewing planning-flagged records where MRP_NET_FLAG = 'Y'. Reconciliation queries join import rows back to work order and item master tables to validate that all demand was transferred correctly.

Related Objects

• CS_SYSTEMS_ALL_B_TEMP — referenced via EAM_MATERIAL_IMPORT.ROW_ID; supplies the source system identity context for impersonation/import staging.
• BOM_DEPARTMENTS — referenced via EAM_MATERIAL_IMPORT.DEPARTMENT_ID; identifies the department owning the material requirement.
• WIP_ENTITIES — joined through WIP_ENTITY_ID to resolve the work order or maintenance activity.
• MTL_SYSTEM_ITEMS_B — joined through INVENTORY_ITEM_ID to resolve item descriptions and attributes.
• MTL_SECONDARY_INVENTORIES — joined through SUPPLY_SUBINVENTORY to validate subinventory defaults.
• PO_VENDORS — joined through VENDOR_ID for procurement and sourcing views.
• EAM_WORK_ORDERS / EAM_WO_OPERATIONS — operational targets that consume staged material records.