Search Results bom_inventory_components

Overview

The BOM_INVENTORY_COMPONENTS view is a critical data object within the Bills of Material (BOM) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It provides a comprehensive, read-only perspective on the component items that constitute a bill of material. This view consolidates and presents detailed information from the underlying BOM tables, specifically focusing on the relationship between an assembly and its constituent parts. Its primary role is to serve as a reliable source for reporting, data extraction, and integration processes that require a complete picture of BOM component details, including engineering change order (ECO) data, supply attributes, and effectivity controls.

Key Information Stored

The view encompasses a wide array of columns essential for managing and analyzing BOM structures. Key fields can be categorized as follows:

• Identification & Relationships: COMPONENT_SEQUENCE_ID (primary key), BILL_SEQUENCE_ID (links to the parent assembly), COMPONENT_ITEM_ID, and ITEM_NUM define the component's place in the structure.
• Quantities & Planning: COMPONENT_QUANTITY, BASIS_TYPE, YIELD_FACTOR, PLANNING_FACTOR, and LOW/HIGH_QUANTITY govern material requirements and planning calculations.
• Supply & Manufacturing: WIP_SUPPLY_TYPE, SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID, PICK_COMPONENTS, and OPERATION_SEQ_NUM control how components are issued to production.
• Effectivity & Changes: EFFECTIVITY_DATE, DISABLE_DATE, CHANGE_NOTICE, and a suite of revision columns (e.g., FROM_END_ITEM_REV_ID, COMPONENT_ITEM_REVISION_ID) manage component validity and engineering changes.
• Component Attributes: Flags such as OPTIONAL, CHECK_ATP, INCLUDE_IN_COST_ROLLUP, REQUIRED_TO_SHIP, and MUTUALLY_EXCLUSIVE_OPTIONS define specific component behavior.

Common Use Cases and Queries

This view is extensively used for operational and analytical reporting. A common use case is generating a component pick list for a specific assembly, filtering by effective components. For example:

SELECT component_item_id, component_quantity, supply_subinventory, wip_supply_type FROM apps.bom_inventory_components WHERE bill_sequence_id = :bill_seq AND SYSDATE BETWEEN TRUNC(effectivity_date) AND NVL(TRUNC(disable_date), SYSDATE+1) ORDER BY item_num;

Another critical scenario is cost rollup analysis, identifying all components flagged for inclusion in cost calculations. The view is also pivotal for ATP (Available to Promise) checking integrations and for validating BOM structures during data migration or reconciliation projects, as it presents a unified interface to complex underlying tables.

Related Objects

BOM_INVENTORY_COMPONENTS is a denormalized view that primarily draws from the BOM_INVENTORY_COMPONENTS base table. Its key relationships, inferred from its column set, are with other core BOM and inventory entities. Essential joins include:

• BOM_BILL_OF_MATERIALS: Joined via BILL_SEQUENCE_ID to retrieve header information for the parent assembly.
• MTL_SYSTEM_ITEMS_B (Component): Joined via COMPONENT_ITEM_ID to get item descriptions, primary unit of measure, and other item master attributes.
• MTL_SYSTEM_ITEMS_B (Assembly): Joined indirectly through BILL_SEQUENCE_ID to BOM_BILL_OF_MATERIALS.ASSEMBLY_ITEM_ID for parent item details.
• ENG_REVISED_ITEMS: Related via REVISED_ITEM_SEQUENCE_ID for tracking engineering change revisions.
• BOM_COMPONENT_OPERATIONS: Can be linked using COMPONENT_SEQUENCE_ID and OPERATION_SEQ_NUM for detailed routing operation data.