Results for “eam_op_completion_txns”

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

Overview

EAM_OP_COMPLETION_TXNS is the Work Order Operation Completion Transaction History table within the Oracle Enterprise Asset Management (EAM) module. It resides in the EAM schema and is classified as VALID in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The table records the audit trail of every operation completion transaction executed against an EAM work order, capturing the asset affected, the department and operation sequence involved, the accounting period in which the transaction was posted, and the timing metrics of the work performed. It functions as the transactional ledger that bridges shop-floor execution and asset history reporting, and it is a core source for maintenance cost analysis, asset utilization reporting, and reconciliation of work order activity against the general ledger.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure suggests this object behaves as a link table. It records the association between a discrete maintenance event (the transaction) and the participating business entities — asset, organization, department, accounting period, transaction type, and reason — rather than acting as a standalone hub of a single business concept or a pure descriptive satellite.

Key Information Stored

The table contains 48 documented columns. The most significant include:

• TRANSACTION_ID — surrogate primary key, enforced by EAM_OP_COMPLETION_TXNS_PK and reinforced by the unique index EAM_OP_COMPLETION_TXNS_U1. It uniquely identifies each operation completion transaction.
• TRANSACTION_DATE — the effective date the completion transaction was executed.
• TRANSACTION_TYPE — the classification of the transaction, referencing MTL_TRANSACTION_TYPES.
• WIP_ENTITY_ID — the work order (WIP entity) against which the operation was performed.
• ORGANIZATION_ID — the inventory organization owning the transaction.
• OPERATION_SEQ_NUM and HANDOVER_OPERATION_SEQ_NUM — the operation sequence completed and, where applicable, the sequence handed over.
• DEPARTMENT_ID — the department executing the operation, referencing BOM_DEPARTMENTS.
• ASSET_NUMBER, ASSET_GROUP_ID, and ASSET_ACTIVITY_ID — identify the maintainable asset and the specific asset activity to which the transaction applies.
• ACCT_PERIOD_ID — the accounting period for posting, referencing ORG_ACCT_PERIODS.
• ACTUAL_START_DATE, ACTUAL_END_DATE, and ACTUAL_DURATION — the realized timing and duration of the operation.
• REASON_ID — the transaction reason, referencing MTL_TRANSACTION_REASONS.
• QA_COLLECTION_ID and RECONCILIATION_CODE — quality collection linkage and reconciliation tagging.
• VENDOR_ID, VENDOR_SITE_ID, and VENDOR_CONTACT_ID — supplier attribution for externally performed work.
• WHO columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE, plus 15 descriptive ATTRIBUTE columns.

Common Use Cases and Queries

Typical use cases include work order completion auditing, mean-time-to-repair analysis, department labor utilization, asset maintenance history reporting, and periodic reconciliation against the general ledger. A frequently used query pattern aggregates actual duration by asset and operation:

• SELECT WIP_ENTITY_ID, ASSET_NUMBER, OPERATION_SEQ_NUM, ACTUAL_START_DATE, ACTUAL_END_DATE, ACTUAL_DURATION FROM EAM_OP_COMPLETION_TXNS WHERE ORGANIZATION_ID = :org_id AND TRUNC(TRANSACTION_DATE) BETWEEN :from_date AND :to_date;
• SELECT DEPARTMENT_ID, SUM(ACTUAL_DURATION) FROM EAM_OP_COMPLETION_TXNS WHERE ACCT_PERIOD_ID = :period_id GROUP BY DEPARTMENT_ID;
• SELECT t.TRANSACTION_ID, t.TRANSACTION_TYPE, m.TRANSACTION_TYPE_NAME FROM EAM_OP_COMPLETION_TXNS t, MTL_TRANSACTION_TYPES m WHERE t.TRANSACTION_TYPE = m.TRANSACTION_TYPE_ID;

Related Objects

The foreign key relationships define the principal related objects:

• MTL_SERIAL_NUMBERS — joined on ASSET_NUMBER and ORGANIZATION_ID to resolve the maintainable asset.
• MTL_SYSTEM_ITEMS_B — joined on ASSET_ACTIVITY_ID and ORGANIZATION_ID to resolve the asset activity item.
• ORG_ACCT_PERIODS — joined on ACCT_PERIOD_ID and ORGANIZATION_ID for period and ledger validation.
• MTL_TRANSACTION_TYPES — joined on TRANSACTION_TYPE to obtain the transaction type description.
• MTL_TRANSACTION_REASONS — joined on REASON_ID for reason code resolution.
• BOM_DEPARTMENTS — joined on DEPARTMENT_ID for department name and resource context.
• Work order and asset activity master data (WIP entities and EAM asset activity definitions) provide the contextual join path used in most operational reports.