Search Results eam_cfr_operations_v




Overview
Explore in AI Chat

Overview

APPS.EAM_CFR_OPERATIONS_V is a reporting view in the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It is classified as a VIEW object with VALID status in the APPS schema, and is documented in ETRM for both release 12.1.1 and 12.2.2. The view presents work order operation information, combining WIP operation records with their associated departments, standard operations, and lookup code translations. Its name prefix "CFR" reflects its origin as a concurrent program / reporting source used to surface EAM work order operations in a single, flattened result set.

The view serves a reporting and integration role: rather than joining WIP_OPERATIONS, BOM_DEPARTMENTS, BOM_STANDARD_OPERATIONS, and MFG_LOOKUPS manually, consumers query EAM_CFR_OPERATIONS_V to obtain operation detail alongside decoded display values. Columns such as COUNT_POINT_TYPE_DISP, BACKFLUSH_FLAG_DISP, OPERATION_COMPLETED_DISP, and the shutdown type MEANING provide pre-translated values, which simplifies report development and reduces the risk of missing lookup joins. Because it is an APPS-schema view, it is accessible to custom reports, Discoverer workbooks, and other EBS reporting tools that connect as the APPS user.

Underlying Base Objects

The view is defined over four documented base objects: BOM_DEPARTMENTS (SYNONYM), BOM_STANDARD_OPERATIONS (SYNONYM), MFG_LOOKUPS (VIEW), and WIP_OPERATIONS (SYNONYM). WIP_OPERATIONS is the primary driving table and supplies the majority of the columns. BOM_DEPARTMENTS is joined on DEPARTMENT_ID to retrieve DEPARTMENT_CODE and LOCATION_ID. BOM_STANDARD_OPERATIONS is an outer join (STANDARD_OPERATION_ID(+) ) used to obtain OPERATION_CODE; the join condition additionally filters BSO.OPERATION_TYPE to null or 1 and requires BSO.LINE_ID to be null. MFG_LOOKUPS is joined four times, each instance restricted to a distinct lookup type: BOM_EAM_SHUTDOWN_TYPE (ML1, outer-joined on SHUTDOWN_TYPE), BOM_COUNT_POINT_TYPE (ML2), the backflush flag lookup (ML3), and the operation completed lookup (ML4).

In 12.2.2 the referenced objects are confirmed as synonyms for the BOM and WIP base tables plus the MFG_LOOKUPS dictionary view. The structure is identical across 12.1.1 and 12.2.2 per the ETRM metadata, so no online patching differences affect the column list or joins.

Key Columns

The view exposes identification columns (WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID, OPERATION_SEQUENCE_ID, STANDARD_OPERATION_ID, DEPARTMENT_ID), descriptive columns (OPERATION_CODE, DEPARTMENT_CODE, DESCRIPTION, LONG_DESCRIPTION), and scheduling dates (FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE).

The column OPERATION_YIELD_ENABLED is notable because it indicates whether yield tracking is active for a given operation, making it directly relevant to scrap and yield reporting.

Common Use Cases and Queries

Typical scenarios include EAM work order status reporting, shop-floor operation dashboards, yield and scrap analysis, and integration extracts feeding external MES or BI systems. A representative query filtering on yield-enabled operations is:

SELECT wip_entity_id, operation_seq_num, organization_id, department_code, operation_code, scheduled_quantity, quantity_completed, operation_yield, cumulative_scrap_quantity, operation_yield_enabled FROM apps.eam_cfr_operations_v WHERE organization_id = :org_id AND operation_yield_enabled = 'Y' ORDER BY wip_entity_id, operation_seq_num;

To summarize scrap by department, group by DEPARTMENT_CODE and aggregate CUMULATIVE_SCRAP_QUANTITY against SCHEDULED_QUANTITY. Because the view pre-joins MFG_LOOKUPS, reports can reference BACKFLUSH_FLAG_DISP or COUNT_POINT_TYPE_DISP directly without additional database calls, improving query performance and consistency.