Search Results mrp_bom_components

Overview

The BOM_INVENTORY_COMPONENTS table is the core transactional table for storing component details within a standard bill of material (BOM) in Oracle E-Business Suite Bills of Material module. It defines the specific items, quantities, and operational instructions required to build an assembly. This table is central to manufacturing, cost roll-up, material planning (MRP), and order fulfillment processes. The table's primary key is COMPONENT_SEQUENCE_ID, which uniquely identifies each component record. The metadata indicates a notable implementation detail: for the queried database instance, this table is documented as "Not implemented," which may signify it is a seed data table or that its transactional logic is abstracted through higher-level APIs in the standard application.

Key Information Stored

The table's structure captures the complete definition of a BOM component. Key columns include COMPONENT_SEQUENCE_ID (the unique identifier), BILL_SEQUENCE_ID (linking to the parent bill in BOM_BILL_OF_MATERIALS), and COMPONENT_ITEM_ID (identifying the inventory item used as the component). The EFFECTIVITY_DATE governs the active date range for the component, allowing for engineering changes. OPERATION_SEQ_NUM specifies the manufacturing operation where the component is required. Other significant columns inferred from the foreign key relationships include REVISED_ITEM_SEQUENCE_ID for tracking component revisions and OLD_COMPONENT_SEQUENCE_ID, which supports change management by linking to a superseded component record.

Common Use Cases and Queries

This table is fundamental for generating component pick lists, calculating product costs, and driving material requirements planning. A common reporting need is to list all active components for a specific assembly. The sample query below demonstrates this, joining to item and bill master tables. Developers often query this table to validate BOM structure or to extract component data for custom integrations.

• Sample Query: SELECT bic.component_item_id, msik.concatenated_segments component, bic.component_quantity, bic.effectivity_date FROM bom_inventory_components bic, bom_bill_of_materials bbm, mtl_system_items_kfv msik WHERE bic.bill_sequence_id = bbm.bill_sequence_id AND bbm.assembly_item_id = :p_assembly_item_id AND bic.component_item_id = msik.inventory_item_id AND msik.organization_id = bbm.organization_id AND SYSDATE BETWEEN bic.effectivity_date AND NVL(bic.disable_date, SYSDATE) ORDER BY bic.operation_seq_num, bic.component_sequence_id;
• Use Case: The MRP engine heavily relies on this table, as evidenced by the MRP_BOM_COMPONENTS view which likely provides a planning-specific snapshot of this data, hence the user's search for "mrp_bom_components".

Related Objects

The table maintains integral relationships with several core EBS tables, as documented by its foreign keys. The primary relationship is with BOM_BILL_OF_MATERIALS (BILL_SEQUENCE_ID), which defines the parent assembly. It has a recursive relationship with itself via OLD_COMPONENT_SEQUENCE_ID to manage component revisions. For engineering change functionality, it links to ENG_REVISED_ITEMS. Crucially, it feeds into planning and order management modules through the MRP_BOM_COMPONENTS view, SO_LINES_ALL, and SO_LINE_DETAILS tables (via COMPONENT_SEQUENCE_ID), linking BOM data to sales orders and planned orders. It also relates to WSM_CO_PRODUCTS for complex manufacturing scenarios.