Search Results bom_component_all_operations_v




Overview
Explore in AI Chat

Overview

BOM_COMPONENT_ALL_OPERATIONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Bills of Material (BOM) product. As its ETRM description states, it provides a "view of all operation for components - all records," presenting a consolidated, uniformly structured result set that combines component-level and operation-level bill of material data into a single logical stream. Because it exposes component operation assignments without requiring callers to join BOM_INVENTORY_COMPONENTS and BOM_COMPONENT_OPERATIONS manually, it is positioned as a convenience layer for reporting, integration, and inquiry functionality across EBS 12.1.1 and 12.2.2.

The view is defined as the UNION of two SELECT statements. The first returns rows sourced only from BOM_INVENTORY_COMPONENTS and stamps each row with the literal entity identifier 'COMPONENT' and a COMP_OPERATION_SEQ_ID of 0. The second returns rows joined from BOM_COMPONENT_OPERATIONS and BOM_INVENTORY_COMPONENTS on COMPONENT_SEQUENCE_ID, stamps them with 'OPERATION', and carries the real BCO.COMP_OPERATION_SEQ_ID. This UNION design means the view returns all component rows, including those with no operation assignment, plus a distinct row for every operation assigned to a component.

Underlying Base Objects

The documented base objects referenced by the view are BOM_COMPONENT_OPERATIONS (a SYNONYM) and BOM_INVENTORY_COMPONENTS (a VIEW). BOM_INVENTORY_COMPONENTS supplies the component-level attributes — BILL_SEQUENCE_ID, COMPONENT_ITEM_ID, effectivity and disable dates, end item unit number ranges, implementation date, and ECO_FOR_PRODUCTION. BOM_COMPONENT_OPERATIONS contributes the routing/operation association through OPERATION_SEQ_NUM and COMP_OPERATION_SEQ_ID, joined to the component by COMPONENT_SEQUENCE_ID. The join is an equi-join on COMPONENT_SEQUENCE_ID; components without a matching operation row still appear through the first branch of the UNION.

Key Columns

  • BILL_SEQUENCE_ID — Identifies the parent bill (assembly) to which the component belongs.
  • COMPONENT_SEQUENCE_ID — Unique identifier of the component row; the join key between the two source objects.
  • COMPONENT_ITEM_ID — Inventory item identifier of the component.
  • OPERATION_SEQ_NUM — Operation sequence number for the routing operation associated with the component.
  • EFFECTIVITY_DATE / DISABLE_DATE — Validity window for the component.
  • FROM_END_ITEM_UNIT_NUMBER / TO_END_ITEM_UNIT_NUMBER — Unit number range for the component in a specific end item context.
  • IMPLEMENTATION_DATE — Date the component becomes effective for implementation.
  • ECO_FOR_PRODUCTION — Engineering change order reference under which the component entered production.
  • COMP_OPERATION_SEQ_ID — Identifier of the component operation record; 0 for rows emitted by the 'COMPONENT' branch.
  • ROW_ID — The ROWID of the source row (BIC or BCO respectively), useful for disambiguation.
  • ENTITY_IDENTIFIER — Literal 'COMPONENT' or 'OPERATION', indicating which branch of the UNION produced the row.

Common Use Cases and Queries

Typical uses include component-to-operation reporting, operation count validation, BOM inquiry screens, and integration extracts where both component and operation context are needed in one pass. Filtering on ENTITY_IDENTIFIER isolates the two logical result sets.

-- Components with their assigned operations
SELECT BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, COMPONENT_ITEM_ID,
       OPERATION_SEQ_NUM, COMP_OPERATION_SEQ_ID, ENTITY_IDENTIFIER
FROM   APPS.BOM_COMPONENT_ALL_OPERATIONS_V
WHERE  ENTITY_IDENTIFIER = 'OPERATION'
AND    COMPONENT_ITEM_ID = :p_item_id;

-- All operation rows for a given bill
SELECT COMPONENT_SEQUENCE_ID, COMPONENT_ITEM_ID, OPERATION_SEQ_NUM
FROM   APPS.BOM_COMPONENT_ALL_OPERATIONS_V
WHERE  BILL_SEQUENCE_ID = :p_bill_sequence_id
AND    ENTITY_IDENTIFIER = 'OPERATION'
ORDER  BY COMPONENT_SEQUENCE_ID, OPERATION_SEQ_NUM;

Because the view is a UNION without deduplication, queries counting rows must discriminate by ENTITY_IDENTIFIER to avoid double-counting components. CONNECT BY or hierarchical assembly explosion should be built on the underlying BOM structures rather than this view.