Results for “msc_boms”

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

Overview

MSC_BOMS is a table in the MSC schema (Advanced Supply Chain Planning module) of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. It represents the bills of material of an item created at source applications, serving as the planning-side staging repository for BOM structures that Advanced Supply Chain Planning consumes during plan runs. Unlike the transactional BOM tables in Oracle Bills of Material (BOM), MSC_BOMS holds a plan-scoped, instance-scoped snapshot that the planning engine uses to explode assemblies, net component demand, and evaluate alternates and effectivity. The table is populated by collections and refreshed per plan, so it is an operational data store rather than a system of record.

The documented physical schema contains 45 columns. Its primary key, MSC_BOMS_PK, is composed of PLAN_ID, SR_INSTANCE_ID, and BILL_SEQUENCE_ID. A second unique index, MSC_BOMS_U1, adds NEW_PLAN_ID, SIMULATION_SET_ID, ACTIVITY_ITEM_ID, and ASSEMBLY_ITEM_ID, reflecting the table's multi-plan, simulation-aware design. Based on the foreign key structure, the Data Vault classification is heuristic hub-leaning: MSC_BOMS behaves as a hub keyed by plan, source instance, and bill sequence, with MSC_BOM_COMPONENTS and MSC_PROCESS_EFFECTIVITY acting as dependent link/satellite structures.

Key Information Stored

The most significant columns fall into identity, planning context, and assembly definition categories:

• PLAN_ID, SR_INSTANCE_ID, BILL_SEQUENCE_ID — the composite primary key identifying a BOM header within a plan and source instance.
• ASSEMBLY_ITEM_ID, ORGANIZATION_ID — the assembly item and owning organization; ASSEMBLY_ITEM_ID references MSC_SYSTEM_ITEMS.
• ALTERNATE_BOM_DESIGNATOR, ASSEMBLY_TYPE — the BOM alternate and assembly type (e.g., standard, model, planning bill).
• ASSEMBLY_QUANTITY, UOM, SCALING_TYPE — the parent quantity basis and scaling method used for component explosion.
• SIMULATION_SET_ID, NEW_PLAN_ID, ACTIVITY_ITEM_ID — simulate-plan and activity context; part of the MSC_BOMS_U1 unique key.
• REFRESH_NUMBER, REQUEST_ID — collection/refresh lineage for audit and troubleshooting.
• YIELDING_OP_SEQ_NUM, REPAIRABLE, PENDING_FROM_ECN — operation yielding and engineering-change metadata.
• Standard WHO columns — LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, and the ATTRIBUTE1–15 flexfield set.

Common Use Cases and Queries

Typical uses include diagnosing why a component did not appear in a plan, validating BOM collection completeness, and extracting BOM structures for planning reports. A representative query joins headers to components:

SELECT b.BILL_SEQUENCE_ID, b.ASSEMBLY_ITEM_ID, b.ALTERNATE_BOM_DESIGNATOR, c.COMPONENT_ITEM_ID, c.COMPONENT_QUANTITY
FROM MSC_BOMS b, MSC_BOM_COMPONENTS c
WHERE b.PLAN_ID = c.PLAN_ID
AND b.SR_INSTANCE_ID = c.SR_INSTANCE_ID
AND b.BILL_SEQUENCE_ID = c.BILL_SEQUENCE_ID
AND b.PLAN_ID = :plan_id;

Another common pattern confirms which assemblies were collected for a given instance and organization, or compares REFRESH_NUMBER across plans to detect stale BOM data.

Related Objects

• MSC_SYSTEM_ITEMS — joined on ASSEMBLY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID.
• MSC_BOM_COMPONENTS — child table joined on SR_INSTANCE_ID, BILL_SEQUENCE_ID, and PLAN_ID.
• MSC_PROCESS_EFFECTIVITY — dependent structure using the same composite planning key.
• MSC_BOMS_PK / MSC_BOMS_U1 — primary and unique indexes enforcing plan, simulation, and activity uniqueness.