Results for “eam_operation_import”

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

Overview

EAM.EAM_OPERATION_IMPORT is an Enterprise Asset Management (EAM) interface table that serves as the staging and import mechanism for work order operations. In Oracle EBS 12.1.1 and 12.2.2, the table is used by the Work Order Operations Import process, which reads operation records from this interface table and validates and transfers them into the live EAM work order operation tables. It is a transient, batch-oriented object: rows are typically loaded by external systems, spreadsheets, or feeder programs, processed by a concurrent program, and then purged or marked with a return status. The table holds 40 documented columns in the ETRM 12.2.2 release and is owned by the EAM schema, with public synonyms and grants configured for application access.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as standalone. Given its interface-table nature — a batch container with no strongly enforced parent/child cardinality — it is most naturally modeled as a staging or raw satellite rather than a true hub or link. The surrogate ROW_ID, which references CS_SYSTEMS_ALL_B_TEMP, functions as a temporary identifier rather than an enduring business key, reinforcing the satellite interpretation.

Key Information Stored

The table's most significant columns fall into three functional groups:

• Batch control: HEADER_ID and GROUP_ID identify the import batch and group the interface rows processed by a single concurrent request. ROW_ID is the surrogate row identifier linked to CS_SYSTEMS_ALL_B_TEMP.
• Work order context: WIP_ENTITY_ID ties the operation to a specific work order, while ORGANIZATION_ID establishes the inventory organization. OPERATION_SEQ_NUM gives the sequence position of the operation on the work order routing.
• Operation definition: STANDARD_OPERATION_ID (referencing WSM_OPERATION_DETAILS) and DEPARTMENT_ID (referencing BOM_DEPARTMENTS) define the standard operation and performing department. DESCRIPTION and LONG_DESCRIPTION carry short and long operation text. OPERATION_SEQUENCE_ID links to the resulting live operation row after import.
• Scheduling and behavior flags: START_DATE, COMPLETION_DATE, MINIMUM_TRANSFER_QUANTITY, COUNT_POINT_TYPE, BACKFLUSH_FLAG, and SHUTDOWN_TYPE control execution semantics. RETURN_STATUS and TRANSACTION_TYPE report the processing outcome.
• Audit and DFF: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and ATTRIBUTE_CATEGORY with ATTRIBUTE1–ATTRIBUTE15 support auditing and descriptive flexfield capture.

Common Use Cases and Queries

The principal use case is bulk maintenance of work order routings. Teams load an Excel or external file, insert rows into this interface table, and run the Work Order Operations Import concurrent program. Reporting scenarios include:

• Monitoring import success and error rates by batch:

  SELECT GROUP_ID, RETURN_STATUS, COUNT(*)
  FROM   EAM.EAM_OPERATION_IMPORT
  GROUP  BY GROUP_ID, RETURN_STATUS;

• Identifying failed rows for correction prior to reprocessing, filtering on RETURN_STATUS not equal to success.
• Reconciling imported operations back to the work order via WIP_ENTITY_ID and OPERATION_SEQUENCE_ID.
• Auditing who loaded a batch using the CREATED_BY and LAST_UPDATED_BY audit columns.

Related Objects

The FK metadata identifies three direct references, and processing logic touches several other EAM and Work in Process objects:

• CS_SYSTEMS_ALL_B_TEMP — referenced by ROW_ID; supplies the temporary row identifier.
• WSM_OPERATION_DETAILS — referenced by STANDARD_OPERATION_ID; defines the standard operation being imported.
• BOM_DEPARTMENTS — referenced by DEPARTMENT_ID; identifies the department performing the operation.
• WIP_ENTITIES (via WIP_ENTITY_ID) — the work order header the operation belongs to.
• WIP_OPERATIONS (via WIP_ENTITY_ID and OPERATION_SEQ_NUM) — the destination table populated after successful import.
• MTL_SYSTEM_ITEMS_B and MTL_PARAMETERS (via ORGANIZATION_ID) — validate the organization and item context.
• The Work Order Operations Import concurrent program — the API that consumes this table.