Search Results msc_item_supplier_v




Overview
Explore in AI Chat

Overview

MSC_ITEM_SUPPLIER_V is a reporting and integration view owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product family of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. The view consolidates sourcing information for planned items, combining supplier records, supplier site details, item definitions, and planning organization context into a single denormalized result set. It exposes both surrogate identifiers and readable code values — for example, supplier IDs alongside partner names, and organization IDs alongside organization codes — which makes it suitable for external reporting, custom concurrent programs, and integration extracts without requiring downstream joins to resolve descriptive attributes. The view is a lightweight presentation layer over the underlying planner tables rather than a transactional entity in its own right.

Underlying Base Objects

The view is defined over several documented base objects. The driving table is MSC_ITEM_SUPPLIERS (referenced as a synonym), which holds the actual supplier-item sourcing rows keyed by plan, supplier, item, and organization. It is joined to MSC_TRADING_PARTNERS twice: once filtered to PARTNER_TYPE = 1 (suppliers) to resolve the supplier name, and once filtered to PARTNER_TYPE = 3 (organizations) matching on SR_TP_ID and SR_INSTANCE_ID to resolve the organization code. MSC_TRADING_PARTNER_SITES is outer-joined (via the (+) operator) on partner ID and partner site ID, so item-supplier rows without a matching site definition are still returned. Item descriptions come from MSC_ITEMS on INVENTORY_ITEM_ID, and the MSC_GET_NAME package function, specifically MSC_GET_NAME.ORG_CODE, is invoked to derive the using organization code from the using organization ID and source instance ID. The ETRM metadata also lists MSC_ITEM_CATEGORIES and MSC_SYSTEM_ITEMS among referenced objects, reflecting the broader synonym relationships in the MSC schema.

Key Columns

The view returns the following principal columns:

Common Use Cases and Queries

Typical uses include extracting approved supplier lists for a plan, validating sourcing setup ahead of a plan run, and feeding external procurement or analytics systems. A representative query returns sourcing rows for a specific plan and item:

SELECT supplier_name, supplier_site, organization_code, item_name, processing_lead_time, minimum_order_quantity, supplier_price FROM msc_item_supplier_v WHERE plan_id = :p_plan_id AND item_name = :p_item ORDER BY supplier_name;

A second common pattern profiles lead times across suppliers for a given organization to support sourcing decisions:

SELECT item_name, supplier_name, processing_lead_time, fixed_lot_multiplier FROM msc_item_supplier_v WHERE organization_code = :p_org AND collected_flag = 'Y';

Because the view resolves code values inline, it reduces join complexity for ad hoc reporting, though consumers should note the outer join to supplier sites may yield null site values when no site record exists.