Results for “reconciliation_code”

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

Overview

The APPS.EAM_CFR_WORK_COMPLETION_V view is a reporting and integration object within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its documented purpose is to display the details of maintenance work orders that have been completed or are still uncompleted, and it is specifically referenced by the ERES (Electronic Records and Electronic Signatures) framework at the time of work order completion in the XGM environment. The view consolidates transaction-level work completion data with descriptive lookup meanings, organization context, and inventory location details, allowing downstream consumers such as signature capture, audit, and reporting components to resolve coded values into human-readable text without additional joins.

Because the object is owned by the APPS schema and exposed as a standard view, it is available to any session with the appropriate grants, making it a convenient single-source reference for maintenance completion activity.

Underlying Base Objects

The view is defined over four documented base objects. The primary driving object is the synonym EAM_JOB_COMPLETION_TXNS (aliased EJCT), which supplies the core work order completion transaction records. Organization context is retrieved through a join to the MTL_PARAMETERS synonym (MP) on ORGANIZATION_ID, yielding the operating unit's organization code.

Two lookups supply descriptive meanings. The MFG_LOOKUPS view (ML1) is joined on TRANSACTION_TYPE with LOOKUP_TYPE = 'EAM_JOB_TXN_TYPE' to produce the transaction name. A second instance of the same view (ML2) is outer-joined on RECONCILIATION_CODE with LOOKUP_TYPE = 'WIP_EAM_RECONCILIATION_CODE', meaning reconciliation codes may be null. Finally, MTL_ITEM_LOCATIONS_KFV (MILK) is outer-joined to resolve the completion locator identifier into a concatenated flexfield segment value; the join includes both INVENTORY_LOCATION_ID and ORGANIZATION_ID, preserving rows where no locator is assigned.

Key Columns

• TRANSACTION_ID — Primary identifier for the work completion transaction.
• TRANSACTION_TYPE — The raw lookup code for the job transaction type.
• TRANSACTION_NAME — The decoded meaning of the transaction type from EAM_JOB_TXN_TYPE; this is the column most commonly searched using the term "transaction_name".
• TRANSACTION_DATE — Date the completion transaction was recorded.
• ORGANIZATION_ID / ORGANIZATION_CODE — Inventory organization identifier and its decoded code.
• WIP_ENTITY_ID — The work order (WIP entity) associated with the maintenance activity.
• ACTUAL_START_DATE, ACTUAL_DURATION, ACTUAL_END_DATE — Actual execution timing of the work.
• RECONCILIATION_CODE — Decoded reconciliation status, nullable due to the outer join.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, LOCATOR_NAME — Destination subinventory and resolved locator flexfield segments.
• LOT_NUMBER — Lot associated with the completion transaction, where applicable.

Common Use Cases and Queries

Typical usage includes ERES signature validation at work order completion, audit reporting of maintenance activity, and operational dashboards tracking completed versus outstanding work. A representative query filtering on the decoded transaction name is:

SELECT transaction_id,
       transaction_type,
       transaction_name,
       transaction_date,
       organization_code,
       wip_entity_id,
       actual_end_date,
       locator_name,
       lot_number
FROM   apps.eam_cfr_work_completion_v
WHERE  transaction_name = 'Completion'
ORDER  BY transaction_date DESC;

Analysts frequently aggregate by organization or transaction name to measure throughput, and join WIP_ENTITY_ID to work order tables for asset-level detail. Because reconciliation and locator columns originate from outer joins, consumers should anticipate nulls in those fields.