Results for “msc_bom_components”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_BOM_COMPONENTS is a table in the MSC schema owned by Oracle Advanced Supply Chain Planning (ASCP), part of the Advanced Planning and Supply Chain Hub product family. It stores exploded bill of material (BOM) component data for planning purposes, capturing each component's relationship to a parent assembly within a specific plan run. Rather than holding the transactional BOM as defined in the source E-Business Suite instance, this table materializes the planning copy of that structure, enriched with simulation, scaling, and planning-specific attributes that the planning engine requires.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning. This reflects the table's nature as a descriptive record attached to a parent BOM structure, keyed by plan, instance, and sequence identifiers rather than acting as an independent business hub or a pure association link. Modelers designing downstream warehouses around this table should treat it as a satellite-like attribute store anchored to the MSC_BOMS structure.

Key Information Stored

The surrogate primary key is MSC_BOM_COMPONENTS_PK, composed of PLAN_ID, COMPONENT_SEQUENCE_ID, SR_INSTANCE_ID, and BILL_SEQUENCE_ID. A parallel unique index, MSC_BOM_COMPONENTS_U1, extends this with NEW_PLAN_ID and SIMULATION_SET_ID, making it the stronger business-key candidate and supporting plan simulation comparisons.

• PLAN_ID / SR_INSTANCE_ID / BILL_SEQUENCE_ID – identify the plan, source instance, and parent BOM structure.
• COMPONENT_SEQUENCE_ID – the surrogate sequence identifying the component line.
• ORGANIZATION_ID / INVENTORY_ITEM_ID – the organization and component item involved.
• USAGE_QUANTITY / COMPONENT_YIELD_FACTOR – quantity and yield used per assembly.
• EFFECTIVITY_DATE / DISABLE_DATE – the effective window for the component.
• COMPONENT_TYPE / WIP_SUPPLY_TYPE – component classification and supply method.
• OPTIONAL_COMPONENT / PLANNING_FACTOR / ATP_FLAG – planning behavior flags.
• REFRESH_NUMBER / APPLIED – plan refresh and application state tracking.
• NEW_PLAN_ID / SIMULATION_SET_ID – simulation and versioning context.

Common Use Cases and Queries

Planners and report developers use this table to trace where-used and bill-of-material structures across a planning horizon. A typical query joins components to the parent BOM and item master to produce a multilevel where-used report for a plan:

SELECT b.assembly_item_id, c.inventory_item_id, c.usage_quantity
FROM   msc_bom_components c, msc_boms b
WHERE  c.plan_id = b.plan_id
AND    c.bill_sequence_id = b.bill_sequence_id
AND    c.plan_id = :plan_id;

Other common scenarios include yield-adjusted usage analysis, effectivity window validation to detect obsolete or future-dated components, and comparison of a base plan against a simulation set using NEW_PLAN_ID and SIMULATION_SET_ID. Reporting teams frequently extract this table into a planning data mart to support component-level demand and supply attribution.

Related Objects

• MSC_BOMS – joined on SR_INSTANCE_ID and BILL_SEQUENCE_ID; the parent BOM header.
• MSC_SYSTEM_ITEMS – joined on INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID for item attributes.
• MSC_COMPONENT_SUBSTITUTES – references this table on BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, SR_INSTANCE_ID, PLAN_ID.
• MSC_OPERATION_COMPONENTS – references this table on BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, SR_INSTANCE_ID, PLAN_ID.
• MSC_SYSTEM_ITEMS_B / item master views – supporting item description and category lookups.