Search Results msc_boms

Overview

The MSC_BOMS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the central planning engine's representation of Bills of Material (BOM) structures, which define the components required to manufacture an assembly. This table stores BOM data sourced and synchronized from the transactional manufacturing applications (such as Oracle Bills of Material) into the MSC planning schema. Its primary role is to provide the essential product structure relationships that the planning engine uses to perform multi-level material requirements planning, capacity planning, and what-if simulations. Without this accurate BOM data, the planning process cannot correctly explode demand through the supply chain to generate planned orders for components.

Key Information Stored

The table's structure is designed to uniquely identify a BOM within the context of a specific plan and source system instance. The primary key columns are PLAN_ID, SR_INSTANCE_ID, and BILL_SEQUENCE_ID. The PLAN_ID links the BOM to a specific planning run or scenario. The SR_INSTANCE_ID identifies the source application instance from which the BOM was collected. The BILL_SEQUENCE_ID is the unique identifier for the BOM itself. Other critical columns include ASSEMBLY_ITEM_ID and ORGANIZATION_ID, which together identify the item being built and the manufacturing organization where the BOM is defined. The table also typically holds metadata such as the BOM type, effectivity dates, and alternate designator, enabling the planning engine to select the correct BOM version for a given time period and planning context.

Common Use Cases and Queries

A primary use case is analyzing BOM structures within a specific plan to understand sourcing or component usage. For instance, a planner may need to identify all assemblies that use a specific component item that is facing a supply shortage. A common reporting query involves joining MSC_BOMS with the MSC_SYSTEM_ITEMS table to resolve item identifiers into names and descriptions.

• Sample Query: Find Assemblies in a Plan
  SELECT msib.assembly_item_id, msi.item_name, msib.organization_id
FROM msc_boms msib, msc_system_items msi
WHERE msib.plan_id = 1001
AND msib.assembly_item_id = msi.inventory_item_id
AND msib.organization_id = msi.organization_id
AND msib.sr_instance_id = msi.sr_instance_id
AND msib.plan_id = msi.plan_id;
• Data Validation: Queries are often used to verify BOM data collection from source instances by checking counts or effectivity dates against the source transactional tables.
• Impact Analysis: Before deleting or modifying a plan, analysts query dependencies in MSC_BOMS to understand the scope of affected data.

Related Objects

As indicated by the foreign key relationships, MSC_BOMS is a foundational parent table within the planning data model. Its most direct child is the MSC_BOM_COMPONENTS table, which holds the detailed list of component items, quantities, and operations for each BOM header defined in MSC_BOMS. It is also linked to MSC_PROCESS_EFFECTIVITY, which manages date-effective changes to BOMs. The table has a critical foreign key relationship to MSC_SYSTEM_ITEMS on the ASSEMBLY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID columns, ensuring that every BOM references a valid item master record within the plan. These relationships enforce data integrity and enable the cascading explosion of demand through the multi-level BOM structure during the planning run.