Search Results msc_components_sc_v




Overview
Explore in AI Chat

Overview

MSC_COMPONENTS_SC_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the MSC product family — Advanced Supply Chain Planning — and its documented purpose is to show all the components in the tree, meaning the bill-of-material component relationships as they are held in the planning engine's denormalized data model. Because Advanced Supply Chain Planning (ASCP) operates on its own snapshot copies of bills and items rather than reading directly from the transactional BOM tables, this view provides a convenient, plan-aware projection of component data without requiring callers to join the MSC staging tables manually.

The view does not itself store data. It is a read-only, non-updatable construct defined by a single SELECT statement, and it returns one row for each component line belonging to a planning bill. Its primary value lies in flattening a multi-table join into a single object that exposes both raw and derived attributes, including several values returned by the MSC_GET_NAME package. This makes it useful for ad hoc reporting, downstream integration extracts, and diagnostics of planning BOM explosions.

Underlying Base Objects

The view is defined over the following documented base objects: MFG_LOOKUPS (VIEW), MSC_BOMS (SYNONYM), MSC_BOM_COMPONENTS (SYNONYM), MSC_COMPONENT_SUBSTITUTES (SYNONYM), MSC_GET_NAME (PACKAGE), MSC_ITEMS (SYNONYM), MSC_ITEM_CATEGORIES (SYNONYM), MSC_SYSTEM_ITEMS (SYNONYM), and MSC_TRADING_PARTNERS (SYNONYM).

The driving table is MSC_BOM_COMPONENTS, aliased ASSY, which supplies the component-side attributes: usage quantity, operation offset, planning factor, component sequence, and the OPTIONAL_COMPONENT flag. It is joined to MSC_BOMS (MB) to retrieve the alternate BOM designator, and to MSC_SYSTEM_ITEMS three times — once for the driving item (DRV), once for the assembly name (ASSY_NAME), and once for the component context — each join keyed on inventory item, organization, plan, and source instance so that plan isolation is preserved. MSC_ITEMS supplies the component item name through COMP_NAME, while MSC_ITEM_CATEGORIES and MFG_LOOKUPS provide category and lookup-meaning decoration. The MSC_GET_NAME package is invoked inline for organization codes, operation sequence numbers, item descriptions, and lookup meanings.

Key Columns

Common Use Cases and Queries

Typical scenarios include identifying optional components for a plan, validating BOM explosion results, and feeding component data into custom planning extracts. The following query lists optional components for a given plan and organization:

  • SELECT inventory_item_id, item_name, organization_id, plan_id, usage_quantity, operation_offset_percent FROM apps.msc_components_sc_v WHERE plan_id = :plan_id AND organization_id = :org_id AND optional_component = 1;

Where a component must be traced to its driving item, the DRIVING_ITEM_ID column and the decoded inventory use-up date can be selected directly, since the view already performs the necessary three-way join to MSC_SYSTEM_ITEMS. Because the view is read-only, all consumer logic should treat it strictly as a query surface over the planning snapshot.