Results for “msc_sc_bill_bom_v”

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

Overview

MSC_SC_BILL_BOM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the MSC (Advanced Supply Chain Planning) product family. It presents a denormalized, plan-aware representation of bill of material (BOM) structures in which the assembly and its components are resolved to organization-qualified item identifiers, and in which component usage is filtered against a valid calendar date range. The view is intended for reporting, data extraction, and integration scenarios in which a planner, integration engineer, or external planning engine requires a flat list of assembly-component relationships tied to a specific source instance, organization, and plan.

Because the view joins the planning BOM snapshots rather than the transactional BOM tables in the BOM module, it reflects the state of the supply chain planning data model. The distinguishing characteristic of the view is that it emits, for each component, a row per calendar date on which that component is effective, which makes it possible to reason about component validity over time without writing date-range logic against the base planning tables.

Underlying Base Objects

The view is defined over synonyms that resolve to the underlying MSC planning tables. The documented base objects are:

• MSC_BOMS — the planning BOM header snapshot, supplying the assembly item, alternate BOM designator, plan, and bill sequence identifiers.
• MSC_BOM_COMPONENTS — the planning BOM component snapshot, supplying component item, usage quantity, effectivity and disable dates, and operation linkage.
• MSC_OPERATION_COMPONENTS — the association of components to routing operations, including operation, routing, and plan sequence keys.
• MSC_ROUTING_OPERATIONS — the routing operation snapshot, supplying the operation sequence number.
• MSC_ITEMS — referenced twice under the aliases ITEM1 and ITEM2, once for the assembly and once for the component, to resolve inventory item identifiers to item names.
• MSC_CALENDAR_DATES — the planning calendar date dimension, used to explode component effectivity into discrete dates.
• MSC_TRADING_PARTNERS — used to resolve the organization identifier and calendar code for the partner type that represents a source organization.
• MSC_ASSIGNMENT_SETS — the assignment set definition, exposing ASSIGNMENT_SET_ID as a scoping attribute.
• MSC_GET_NAME — a package referenced in the documented metadata, typically used for name resolution or formatting within the planning data model.

The joins among MSC_BOMS, MSC_BOM_COMPONENTS, MSC_OPERATION_COMPONENTS, and MSC_ROUTING_OPERATIONS are keyed on plan, source instance, bill sequence, and organization, while the joins to MSC_OPERATION_COMPONENTS and MSC_ROUTING_OPERATIONS are outer joins, so components that are not attached to a routing operation are still returned.

Key Columns

• ASSEMBLY_ITEM_ORG — a concatenation of the assembly item name, a slash, and the organization code, giving a fully qualified assembly identifier.
• COMPONENT_ITEM_ORG — the equivalent qualified identifier for the component, prefixed by the rounded usage quantity and an "X" multiplier (for example, "2X COMPONENT/ORG").
• ASSIGNMENT_SET_ID — the assignment set to which the BOM data belongs, used to scope planning results.
• ORGANIZATION_ID and ORGANIZATION_CODE — the planning organization identifier and its resolved code.
• SR_INSTANCE_ID — the source instance identifier, which distinguishes data originating from different source systems.
• INVENTORY_ITEM_ID, ITEM_NAME, COMPONENT_ITEM_ID, and COMPONENT_NAME — the raw and resolved identifiers and names for the assembly and component items.
• OPERATION_SEQ_NUM — the routing operation sequence to which the component is assigned, when present.
• CALENDAR_DATE, EFFECTIVE_DATE, and the disable date — the effective window of the component, with the calendar date falling between the effectivity date and the disable date (or an open-ended maximum date when no disable date exists).
• USAGE_QUANTITY — the component quantity per assembly, rounded to six decimal places.
• ALTERNATE_BOM_DESIGNATOR — the alternate BOM under which the component is defined.

Common Use Cases and Queries

Typical uses include reporting the effective components for an assembly on a given date, extracting BOM structures for a specific plan and organization, and validating component-to-operation assignments in the planning model.

A basic query lists all components of a given assembly in a specific organization:

• SELECT assembly_item_org, component_item_org, usage_quantity, operation_seq_num, calendar_date FROM msc_sc_bill_bom_v WHERE organization_code = :org AND assembly_item_org LIKE :item || '/%' ORDER BY component_item_org;

A point-in-time effectivity query restricts the calendar date:

• SELECT assembly_item_org, component_item_org, usage_quantity, effective_date FROM msc_sc_bill_bom_v WHERE organization_code = :org AND calendar_date = :as_of_date;

A scoping query by plan attributes uses the assignment set and source instance:

• SELECT DISTINCT assembly_item_org, component_item_org, alternate_bom_designator FROM msc_sc_bill_bom_v WHERE assignment_set_id = :set_id AND sr_instance_id = :instance_id;

Because the view explodes effectivity across calendar dates, queries should generally apply a calendar date predicate or an aggregate to avoid returning one row per effective day.