Search Results eco_for_production




Overview
Explore in AI Chat

Overview

APPS.BOM_COMPONENT_ALL_OPERATIONS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates bill-of-material component data with the routing operations to which those components are assigned. It is owned by the APPS schema and is defined as a UNION of two sources: the component-level records held in BOM_INVENTORY_COMPONENTS and the component-to-operation assignments held in BOM_COMPONENT_OPERATIONS. The view's name reflects its dual nature — it returns every component row whether or not an operation assignment exists, and adds a separate row for each operation assignment. A constant ENTITY_IDENTIFIER column distinguishes the origin of each row ('COMPONENT' versus 'OPERATION'), which allows consumers to filter or aggregate the data by source. The view is primarily used in BOM inquiries, engineering change order (ECO) reporting, manufacturing execution interfaces, and custom reports that need a flattened picture of components and their operations.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects: BOM_COMPONENT_OPERATIONS (exposed as a SYNONYM) and BOM_INVENTORY_COMPONENTS (a VIEW). The first branch of the UNION selects directly from BOM_INVENTORY_COMPONENTS (aliased BIC), producing component-level rows with COMP_OPERATION_SEQ_ID set to 0 and ENTITY_IDENTIFIER set to 'COMPONENT'. The second branch joins BOM_COMPONENT_OPERATIONS (BCO) to BOM_INVENTORY_COMPONENTS (BIC) on COMPONENT_SEQUENCE_ID, producing one row per component-operation combination, carrying the real COMP_OPERATION_SEQ_ID and ENTITY_IDENTIFIER set to 'OPERATION'. Effectivity, disable, implementation, and unit-number attributes are always sourced from BIC, ensuring the component's date and range context is consistently applied across both branches.

Key Columns

  • BILL_SEQUENCE_ID — Identifier of the bill of material header to which the component belongs.
  • COMPONENT_SEQUENCE_ID — Unique identifier of the component line; the join key between the two branches.
  • COMPONENT_ITEM_ID — Inventory item identifier of the component.
  • OPERATION_SEQ_NUM — Routing operation sequence to which the component is attached.
  • COMP_OPERATION_SEQ_ID — Identifier of the component-operation assignment; 0 for pure component rows.
  • EFFECTIVITY_DATE / DISABLE_DATE — Active date range of the component.
  • IMPLEMENTATION_DATE — Date the component or assignment becomes effective.
  • FROM_END_ITEM_UNIT_NUMBER / TO_END_ITEM_UNIT_NUMBER — End-item unit range for which the component is valid.
  • ECO_FOR_PRODUCTION — Engineering change order flag indicating the component/operation was introduced for production.
  • ROW_ID — ROWID of the underlying source row (BIC or BCO).
  • ENTITY_IDENTIFIER — Literal 'COMPONENT' or 'OPERATION' identifying the row source.

Common Use Cases and Queries

A frequent requirement is to retrieve all components for a bill along with their operation assignments, including those not yet linked to any operation. Because rows carry ECO_FOR_PRODUCTION, the view is well suited to ECO impact analysis and to verifying which components are flagged for production. The following query lists components and operation assignments for a given bill:

SELECT bill_sequence_id, component_sequence_id, component_item_id,
       operation_seq_num, comp_operation_seq_id,
       effectivity_date, disable_date, eco_for_production, entity_identifier
FROM   apps.bom_component_all_operations_v
WHERE  bill_sequence_id = :p_bill_sequence_id
ORDER  BY component_sequence_id, operation_seq_num;

To isolate only operation assignments, filter on the entity identifier:

SELECT component_sequence_id, operation_seq_num, comp_operation_seq_id
FROM   apps.bom_component_all_operations_v
WHERE  entity_identifier = 'OPERATION'
AND    bill_sequence_id = :p_bill_sequence_id;

To identify components flagged by an engineering change order for production, constrain ECO_FOR_PRODUCTION to the desired value. Joining COMPONENT_ITEM_ID to MTL_SYSTEM_ITEMS_B yields item descriptions for reporting. In 12.2.2 the same view is available and can be referenced from concurrent programs, OAF pages, and integration extracts.