Results for “msc_substitute_components_v”

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

Overview

MSC_SUBSTITUTE_COMPONENTS_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, Oracle Advanced Supply Chain Planning (ASCP), and its documented purpose is to expose substitute component relationships as resolved within the planning schema. In planning terms, a substitute component defines an alternate item that may be consumed in place of a primary bill of materials (BOM) component when the primary is unavailable, subject to a defined priority and usage quantity. ASCP evaluates these substitutions during supply chain plan generation to recommend feasible alternate sourcing.

Because the view joins planning tables rather than operational BOM tables, it surfaces substitution data as it exists inside the MSC plan workspace, scoped by plan, organization, and source instance. It is therefore a read-only integration and reporting artifact: consumers query it rather than writing to it, and its rows reflect the state of a specific plan run. This makes it valuable for custom reports, extracts, and diagnostic queries that need substitute-component detail congruent with what the planning engine actually processed.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through synonyms in the APPS schema: MSC_BOM_COMPONENTS, MSC_COMPONENT_SUBSTITUTES, and MSC_SYSTEM_ITEMS. In addition, the view text references MSC_ITEMS. The joins are driven by a composite key of PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID, which together identify the plan context.

• MSC_COMPONENT_SUBSTITUTES (SUB) — the primary driver table, supplying substitute item, usage quantity, priority, and component sequence identifiers.
• MSC_BOM_COMPONENTS (BOM) — supplies the primary component and its item, matched to the substitute row on component sequence, bill sequence, plan, instance, and organization.
• MSC_SYSTEM_ITEMS (MSI) — resolves the substitute item to its organization code and item name, joined by plan, organization, instance, and inventory item.
• MSC_ITEMS (MI) — resolves the primary component item name.

Key Columns

• PLAN_ID — identifier of the ASCP plan under which the substitution was collected.
• ORGANIZATION_ID / ORGANIZATION_CODE — the inventory organization and its human-readable code.
• SR_INSTANCE_ID — the source system instance from which planning data was collected.
• SUBSTITUTE_ITEM_ID / SUBSTITUTE_ITEM_NUMBER — the alternate item proposed in place of the primary component.
• COMPONENT_SEQUENCE_ID / COMPONENT_ID / COMPONENT_NUMBER — the primary BOM component being substituted, including the component line identifier and item number. The component_number column is the item number of the primary component and is the most common filter key for users tracing substitution records.
• USAGE_QUANTITY — the quantity of the substitute required per assembly, typically expressed relative to the component.
• PRIORITY — ordering that determines which substitute is selected first when multiple alternates exist.
• BILL_SEQUENCE_ID — identifies the bill (assembly) to which the component belongs.

Common Use Cases and Queries

The view supports plan-scoped reporting on alternate component availability, substitution priority reviews, and reconciliation between planned substitutions and engineering BOM definitions. Typical queries filter on a plan and organization and often on COMPONENT_NUMBER to trace all substitutes defined for a given component.

SELECT plan_id, organization_code, component_number,
       substitute_item_number, usage_quantity, priority
FROM   apps.msc_substitute_components_v
WHERE  plan_id = :p_plan_id
AND    organization_code = :p_org
AND    component_number = :p_component
ORDER BY priority;

A second common pattern aggregates substitutes per primary component to assess how many alternates exist and which carries the highest priority. Administrators also use the view to validate that substitution data was successfully collected for a plan by counting distinct component numbers per plan and instance.