Results for “eam_job_txn_type”

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

Overview

APPS.EAM_CFR_WORK_COMPLETION_V is a reporting view in Oracle E-Business Suite (documented in ETRM for 12.2.2, and applicable to the 12.1.1 / 12.2.2 code lines) that presents Enterprise Asset Management (EAM) work order completion transactions in a fully decoded, presentation-ready form. The view sits over EAM_JOB_COMPLETION_TXNS, the transactional table that stores completion activity recorded against EAM work orders (e.g., completed assemblies and their associated inventory movements). Its primary role is to expose those transactions with their lookup meanings already resolved—transaction type name and reconciliation code meaning—so that reports, concurrent programs, and downstream extracts do not have to rejoin to MFG_LOOKUPS or resolve key flexfield segments themselves.

The name incorporates "CFR" and "WORK_COMPLETION," reflecting its use in the work completion reporting surface for EAM. Users searching for wip_eam_reconciliation_code will find that the view resolves the reconciliation code stored on the completion transaction into its descriptive meaning, which is the exact lookup type referenced in the view definition.

Underlying Base Objects

The ETRM metadata documents the view as being defined over the following objects:

• EAM_JOB_COMPLETION_TXNS (SYNONYM) — the primary transactional source, aliased EJCT. All completion rows are driven from this table.
• MTL_PARAMETERS (SYNONYM) — aliased MP, joined on ORGANIZATION_ID to supply ORGANIZATION_CODE.
• MFG_LOOKUPS (VIEW) — joined twice, as ML1 and ML2, to decode the transaction type (EAM_JOB_TXN_TYPE) and the reconciliation code (WIP_EAM_RECONCILIATION_CODE). The ML1 join is inner; the ML2 join is outer ((+)), so rows without a reconciliation code are retained.
• MTL_ITEM_LOCATIONS_KFV (VIEW) — the concatenated key flexfield view aliased MILK, joined outer on COMPLETION_LOCATOR_ID and ORGANIZATION_ID to return the concatenated location segment string.

The view is therefore a denormalized projection: one driving EAM completion transaction table, augmented with organizational, lookup, and locator descriptive attributes.

Key Columns

• TRANSACTION_ID, TRANSACTION_TYPE — primary identifier and lookup code for the completion transaction; TRANSACTION_NAME is the decoded meaning from EAM_JOB_TXN_TYPE.
• TRANSACTION_DATE, ACTUAL_START_DATE, ACTUAL_DURATION, ACTUAL_END_DATE — completion timing attributes for the work order.
• ORGANIZATION_ID, ORGANIZATION_CODE — inventory organization identifier and its decoded code.
• WIP_ENTITY_ID — the EAM work order (WIP entity) to which the completion belongs.
• RECONCILIATION_CODE — the decoded meaning of the WIP_EAM_RECONCILIATION_CODE lookup, resolving the raw RECONCILIATION_CODE stored on EAM_JOB_COMPLETION_TXNS.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, CONCATENATED_SEGMENTS — the completion destination subinventory and its concatenated locator flexfield value.
• LOT_NUMBER — lot associated with the completed material, where lot control applies.

Common Use Cases and Queries

The view is typically used to report EAM work completion activity, reconcile completions against reconciliation codes, and feed downstream analytics without re-deriving lookup meanings or flexfield concatenations. A representative query filtering by reconciliation meaning and organization is:

• List all completions for an organization with their transaction and reconciliation descriptions.
• Isolate rows where the reconciliation code is null (no reconciliation recorded), exploiting the outer join to ML2.
• Aggregate completion duration by work order or by concatenated locator.

Sample SQL:

SELECT v.TRANSACTION_ID,
       v.TRANSACTION_NAME,
       v.TRANSACTION_DATE,
       v.ORGANIZATION_CODE,
       v.WIP_ENTITY_ID,
       v.RECONCILIATION_CODE,
       v.COMPLETION_SUBINVENTORY,
       v.CONCATENATED_SEGMENTS,
       v.LOT_NUMBER
FROM   APPS.EAM_CFR_WORK_COMPLETION_V v
WHERE  v.ORGANIZATION_CODE = :p_org_code
AND    v.TRANSACTION_DATE BETWEEN :p_from AND :p_to
ORDER BY v.TRANSACTION_DATE;

Because the joins to MFG_LOOKUPS and MTL_ITEM_LOCATIONS_KFV are already resolved within the view, consumers need only apply their own business filters, making the view well suited to EAM work completion reporting, reconciliation monitoring, and integration extracts in Oracle EBS 12.1.1 and 12.2.2.