Search Results backflush_flag_disp

Overview

APPS.EAM_CFR_OPERATIONS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates work order operation data for Enterprise Asset Management (EAM) and Work in Process (WIP) environments. It presents a denormalized, human-readable projection of operation-level records drawn primarily from WIP_OPERATIONS, enriched with departmental and standard-operation descriptive attributes. The view supports reporting on shop-floor execution, operation status, and progress, and is typically consumed by CFR (Continuous Flow Routing / Configure-to-Order reporting) style components and custom reporting or integration layers.

The view is registered under the APPS schema and is commonly referenced by Oracle-provided EAM/CFR pages as well as customer extensions that require operation-level detail without joining multiple base tables manually. Because it exposes both coded values and their decoded meanings, it reduces the amount of lookup resolution required by downstream reports.

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 driving table and supplies the core operation record, including work order identity, sequence numbers, quantities, dates, and status flags. BOM_DEPARTMENTS is joined on DEPARTMENT_ID to provide department codes and location context. BOM_STANDARD_OPERATIONS is joined via an outer join on STANDARD_OPERATION_ID to supply the OPERATION_CODE and to constrain rows to routing operations (null OPERATION_TYPE or type 1, with LINE_ID null). MFG_LOOKUPS is referenced multiple times (aliases ML1–ML4) to translate coded lookup values into display meanings for shutdown type, count point type, backflush flag, and operation completed flag.

Key Columns

• WIP_ENTITY_ID, OPERATION_SEQ_NUM, ORGANIZATION_ID, OPERATION_SEQUENCE_ID, REPETITIVE_SCHEDULE_ID — identify the work order and operation context.
• STANDARD_OPERATION_ID, OPERATION_CODE, DEPARTMENT_ID, DEPARTMENT_CODE, LOCATION_ID — routing and departmental detail.
• SCHEDULED_QUANTITY, QUANTITY_IN_QUEUE, QUANTITY_RUNNING, QUANTITY_WAITING_TO_MOVE, QUANTITY_REJECTED, QUANTITY_SCRAPPED, QUANTITY_COMPLETED — operation-level quantities.
• FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE, DATE_LAST_MOVED — scheduling and movement dates.
• PREVIOUS_OPERATION_SEQ_NUM, NEXT_OPERATION_SEQ_NUM — sequence navigation.
• COUNT_POINT_TYPE and COUNT_POINT_TYPE_DISP — the count point flag and its decoded meaning, sourced from lookup BOM_COUNT_POINT_TYPE. This is the column most directly associated with the user search term "bom_count_point_type."
• BACKFLUSH_FLAG and BACKFLUSH_FLAG_DISP — backflush indicator and its SYS_YES_NO meaning.
• OPERATION_COMPLETED and OPERATION_COMPLETED_DISP, plus OPERATION_YIELD, CUMULATIVE_SCRAP_QUANTITY, OPERATION_YIELD_ENABLED, PROGRESS_PERCENTAGE — completion and yield metrics.
• Attributes, LONG_DESCRIPTION, X_POS, Y_POS, SHUTDOWN_TYPE, DISABLE_DATE, RECOMMENDED — descriptive and configuration fields.

Common Use Cases and Queries

Typical usage includes operation status dashboards, EAM work order reporting, and integration extracts. A representative query filters by organization and work order and lists count point and backflush meanings:

• SELECT wip_entity_id, operation_seq_num, operation_code, count_point_type_disp, backflush_flag_disp, quantity_completed, progress_percentage FROM apps.eam_cfr_operations_v WHERE organization_id = :org AND wip_entity_id = :wo ORDER BY operation_seq_num;
• Account for outer joins and filter operations by count_point_type when building shop-floor move transactability reports.
• Join to WIP_ENTITIES or BOM_STANDARD_OPERATIONS for additional routing context where required.