Search Results mrp_bom_components




Overview
Explore in AI Chat

Overview

The MRP_BOM_COMPONENTS table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as a critical staging and processing table that holds a consolidated view of Bill of Material (BOM) component data, integrating information from standard BOM definitions with pending Engineering Change Orders (ECOs). Its primary role is to provide the Master Scheduling and Material Requirements Planning (MRP) engines with a complete, netted list of components required for planning and scheduling calculations. By compiling both current and approved future BOM structures, it ensures that material plans accurately reflect the state of manufacturing at any given point in the planning horizon.

Key Information Stored

The table's structure is designed to uniquely identify a component within a specific BOM and planning context. Its primary key is the COMPONENT_SEQUENCE_ID, which links directly to the base BOM definition in BOM_INVENTORY_COMPONENTS. The INVENTORY_ITEM_ID and ORGANIZATION_ID columns identify the specific component item and its manufacturing organization. A crucial column is the COMPILE_DESIGNATOR, which indicates the specific planning snapshot or simulation (e.g., 'MPS', 'MRP', or a custom compile) for which this component data is valid. Other significant columns typically include USING_ASSEMBLY_ID to identify the parent assembly, component quantities, effectivity dates, and sourcing details, which collectively define the component relationship for planning purposes.

Common Use Cases and Queries

This table is central to MRP explosion and pegging logic. A common use case is analyzing the component requirements for a specific assembly within a given MRP plan. Developers and analysts often query this table to generate customized component usage reports or to troubleshoot planning output. A typical query pattern involves joining to item master tables (via MRP_SYSTEM_ITEMS) to get item descriptions and planning attributes.

  • Sample Query: Retrieving all components for a specific assembly in the 'MPS' plan:
    SELECT msib.segment1 component_item,
          mbc.component_quantity, mbc.effectivity_date
    FROM mrp_bom_components mbc,
         mrp_system_items msib
    WHERE mbc.using_assembly_id = :assembly_item_id
      AND mbc.compile_designator = 'MPS'
      AND mbc.organization_id = :org_id
      AND mbc.inventory_item_id = msib.inventory_item_id
      AND mbc.organization_id = msib.organization_id
      AND mbc.compile_designator = msib.compile_designator;

Related Objects

As indicated by its foreign keys, MRP_BOM_COMPONENTS has direct dependencies on several fundamental tables. Its primary relationship is with BOM_INVENTORY_COMPONENTS, the table storing the definitive engineering BOM structures. It also has multiple foreign key relationships to MRP_SYSTEM_ITEMS, which is the planning-specific snapshot of item master data. The table is populated and maintained by the MRP planning engine's compilation process and is heavily referenced by other MRP processing tables, such as those holding planned order details and material requirements. Direct manipulation of this table via DML is not standard practice; interaction should occur through the published planning APIs and processes.