Search Results component_yield_factor




Overview
Explore in AI Chat

Overview

BOM_INVENTORY_COMPONENTS is a read-only view owned by the APPS schema in Oracle E-Business Suite (12.1.1 and 12.2.2). It exposes single-level bill of material component information and is defined over BOM_COMPONENTS_B, the base table that stores bill of material component records. The view presents the first-level components of an assembly item, meaning that it returns the immediate children of a given parent assembly rather than a fully exploded, multi-level indented bill. Because it is a view and not a table, no data is stored within it; all query results are derived dynamically from BOM_COMPONENTS_B at runtime.

The view plays a significant role in reporting, data extraction, and integration scenarios where external systems or custom concurrent programs need to interrogate component assignments without navigating the full set of BOM tables. Its status is VALID, and it is classified under the BOM – Bills of Material product module.

Underlying Base Objects

The documented metadata identifies a single referenced base object: BOM_COMPONENTS_B, accessed through a synonym. BOM_COMPONENTS_B holds bill of material component definitions at the single level, including component item references, quantities, effectivity controls, supply attributes, and descriptive flexfield segments. The view selects from this table and surfaces the component attributes directly to the calling application. Because the view is defined only over BOM_COMPONENTS_B, it does not itself join to the bill header table (BOM_BILL_OF_MATERIALS) or to item master tables; consumers requiring parent assembly context or item descriptions must join those tables separately using the sequence and item identifiers exposed by the view.

Key Columns

Common Use Cases and Queries

The view is typically used to retrieve a flat listing of the first-level components for an assembly, to audit effectivity and change control data, or to feed external planning and integration processes. The following example lists active components for a specified bill:

  • SELECT component_sequence_id, component_item_id, component_quantity, basis_type, effectivity_date, disable_date FROM apps.bom_inventory_components WHERE bill_sequence_id = :p_bill_sequence_id ORDER BY component_sequence_id;
  • SELECT component_item_id, wip_supply_type, supply_subinventory, planning_factor FROM apps.bom_inventory_components WHERE bill_sequence_id = :p_bill_sequence_id AND NVL(disable_date, SYSDATE + 1) > SYSDATE;
  • SELECT component_item_id, change_notice, implementation_date FROM apps.bom_inventory_components WHERE component_sequence_id = :p_component_sequence_id;

Because the view is limited to single-level components, multi-level explosion requirements should be handled with the BOM explosion APIs or the standard indented bill reports rather than by self-joining this view. All access should respect the APPS schema grants and standard Oracle EBS security and MOAC considerations.