Results for “asset_activity_id”

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

Overview

The EAM_OP_COMPLETION_TXNS_V view in the APPS schema is a reporting object within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It presents the details of all completed operations of a work order, but with an important restriction: the view returns only the most recent operation completion transaction for each combination of work order and operation sequence. This makes the view a convenient source for status or progress reporting, where the interest lies in the latest completion state rather than the full transactional history.

The view is defined in the APPS schema and is documented as VALID in ETRM 12.2.2, with equivalent availability in 12.1.1. Because it is a view rather than a table, it carries no independent storage and reflects the state of its underlying table at query time. Its design intent is to expose the current operation completion picture for a work order without requiring report authors to write the correlated subquery logic themselves.

Underlying Base Objects

The view is derived from a single base object, EAM_OP_COMPLETION_TXNS, referenced as a synonym in the documented metadata. The definition uses a self-correlated subquery against the same table: for each row, the subquery selects the maximum TRANSACTION_ID for the matching WIP_ENTITY_ID and OPERATION_SEQ_NUM, and the outer query keeps only rows whose TRANSACTION_ID equals that maximum. A static filter, TRANSACTION_TYPE = 1, restricts the results to the completion transaction type.

The net effect is that any historical completions, reversals, or later transactions sharing the same work order and operation sequence are excluded from the view's output. Only one row per work order/operation sequence pair is returned, representing the latest recorded completion.

Key Columns

The view exposes thirteen columns, all inherited directly from EAM_OP_COMPLETION_TXNS:

• TRANSACTION_ID — Unique identifier of the completion transaction; also the column used in the MAX() subquery for selecting the most recent row.
• TRANSACTION_DATE — Date the completion transaction was recorded.
• TRANSACTION_TYPE — Type indicator for the transaction. Because the view filters on TRANSACTION_TYPE = 1, all rows returned are of the completion type.
• WIP_ENTITY_ID — Identifier of the work order (WIP entity) to which the operation belongs.
• ORGANIZATION_ID — Inventory organization owning the work order and transaction.
• OPERATION_SEQ_NUM — Sequence number of the operation within the work order routing.
• DEPARTMENT_ID — Department in which the operation is performed.
• ASSET_GROUP_ID — Identifier of the asset group associated with the completion.
• ASSET_NUMBER — Asset number of the asset for which the operation was completed.
• ASSET_ACTIVITY_ID — Identifier of the asset activity record associated with the completion transaction. This is the column most frequently used to tie completion transactions back to asset activity and maintenance history.
• ACTUAL_START_DATE — Actual date and time the operation started.
• ACTUAL_END_DATE — Actual date and time the operation finished.
• LAST_UPDATE_DATE — Audit column recording the last modification of the row in the base table.

Common Use Cases and Queries

Because the view deduplicates completion transactions, it is well suited to work order status dashboards, operation progress reports, and integration extracts that must not double-count operations. A typical query listing the latest completions for an organization might be:

• SELECT wip_entity_id, operation_seq_num, department_id, asset_number, actual_start_date, actual_end_date FROM eam_op_completion_txns_v WHERE organization_id = :org_id ORDER BY wip_entity_id, operation_seq_num;

To trace a specific asset's completed activities — the scenario in which the user searched for asset_activity_id — the view can be filtered directly on that column:

• SELECT transaction_id, wip_entity_id, operation_seq_num, asset_number, asset_activity_id, actual_end_date FROM eam_op_completion_txns_v WHERE asset_activity_id = :activity_id;

Note that because the view is limited to the single most recent completion per operation, it is not suitable for full audit or history reporting. When a complete transaction trail is required, the base table EAM_OP_COMPLETION_TXNS should be queried instead, using ASSET_ACTIVITY_ID and WIP_ENTITY_ID as join keys. For current-state reporting and integrations where only the latest completed operation per work order sequence matters, EAM_OP_COMPLETION_TXNS_V provides a straightforward and reliable source.