Search Results msc_bom_components




Overview
Explore in AI Chat

Overview

The MSC_BOM_COMPONENTS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) and Supply Chain Planning Hub modules. It functions as the central planning engine's representation of bill of material (BOM) component data. Unlike transactional BOM tables in the manufacturing schema (e.g., BOM_INVENTORY_COMPONENTS), this table stores BOM structures specifically for use within planning simulations and plan runs. Its primary role is to provide the component-level detail required for planning engines to perform material explosion, calculate dependent demand, and generate planned orders for subassemblies and purchased components based on a master production schedule.

Key Information Stored

The table's structure is designed to uniquely identify a component within a specific BOM and plan context. Its primary key is a composite of PLAN_ID, COMPONENT_SEQUENCE_ID, SR_INSTANCE_ID, and BILL_SEQUENCE_ID. Critical columns include PLAN_ID, which links the component to a specific planning run; SR_INSTANCE_ID and BILL_SEQUENCE_ID, which together identify the specific parent BOM definition; and COMPONENT_SEQUENCE_ID, a unique identifier for the component line within that BOM. Other essential columns are INVENTORY_ITEM_ID and ORGANIZATION_ID, which identify the component item and its sourcing organization, and OPERATION_SEQ_NUM for operation-specific component assignments. The table also holds planning-specific attributes such as component yield factors, effectivity dates, and planning percentages that may differ from transactional manufacturing data.

Common Use Cases and Queries

A primary use case is analyzing the component demand generated by a plan. Planners often query this table to validate BOM data loaded into planning or to troubleshoot material shortages. Common SQL patterns involve joining to MSC_SYSTEM_ITEMS to get item details and to MSC_BOMS for parent assembly information. For example, to list all components for a specific assembly in a plan, a query would filter on the parent BILL_SEQUENCE_ID and PLAN_ID. Another critical scenario is comparing component usage across different plan versions or analyzing the impact of component yield on planned order quantities. Reporting use cases include generating component where-used reports within the planning context and validating that alternate and phantom components are correctly represented for the plan's calculations.

Related Objects

As indicated by its foreign keys, MSC_BOM_COMPONENTS has integral relationships with several other planning tables. It is a child of MSC_BOMS, which stores the parent BOM headers. It references MSC_SYSTEM_ITEMS to obtain the component item's planning attributes. Furthermore, it is a parent table to MSC_COMPONENT_SUBSTITUTES, which holds substitute component data for the plan, and to MSC_OPERATION_COMPONENTS, which details operation-specific component requirements. These relationships form a cohesive data model that allows the planning engine to accurately simulate complex manufacturing and sourcing scenarios based on configured product structures.