Results for “msc_item_sourcing_v”

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

Overview

MSC_ITEM_SOURCING_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the MSC (Advanced Supply Chain Planning) product. It presents the sourcing rules and assignment definitions that drive supply chain planning engine behavior, resolving the internal numeric identifiers stored in MSC_ITEM_SOURCING into human-readable form. Specifically, the view joins sourcing data to item, organization, plan, trading partner, supplier site, category, and sourcing rule master records, and it invokes the MSC_GET_NAME package to translate organization IDs into organization codes and lookup codes into meaningful descriptions.

For users who search on item_segments, the view is significant because it exposes the ITEM_SEGMENTS column alongside INVENTORY_ITEM_ID. This allows a report or integration to present concatenated item segment values (the flexfield-derived item identifier) without performing a separate join to the item master. The view therefore serves as a denormalized, integration-friendly source for supply chain planning extracts, custom reports, and downstream interfaces that need sourcing rules expressed in descriptive business terms.

Underlying Base Objects

The view is defined over a set of documented MSC synonyms, with outer joins applied to the optional master records. The documented base objects are MSC_APPS_INSTANCES, MSC_ITEMS, MSC_ITEM_CATEGORIES, MSC_ITEM_SOURCING, MSC_PLANS, MSC_SOURCING_RULES, MSC_TRADING_PARTNERS, and MSC_TRADING_PARTNER_SITES, together with the MSC_GET_NAME package.

• MSC_ITEM_SOURCING is the driving table (SRC), carrying plan, item, organization, source organization, supplier, effective/disable dates, allocation percent, rank, conversion factor, and sourcing rule type.
• MSC_ITEMS (ITEM) supplies the item name and segment values.
• MSC_PLANS (ORGS) supplies plan and plan organization identifiers.
• MSC_SOURCING_RULES (RULES) supplies the sourcing rule name via an outer join on SOURCING_RULE_ID.
• MSC_TRADING_PARTNERS (VEN) and MSC_TRADING_PARTNER_SITES (SITE) supply supplier and supplier site details through outer joins.
• MSC_ITEM_CATEGORIES (CAT) supplies category set and category identifiers.
• MSC_GET_NAME is called inline to resolve organization codes, lookup meanings for MRP_SOURCING_RULE_TYPE, MRP_SOURCE_TYPE, and MRP_SR_ASSIGNMENT_TYPE.

Key Columns

• PLAN_ID, PLAN_ORGANIZATION_ID, PLAN_INSTANCE_ID – plan context for the sourcing definition.
• INVENTORY_ITEM_ID, ITEM_SEGMENTS – the numeric item key and the concatenated descriptive item segments.
• ORGANIZATION_ID, ORGANIZATION_CODE – the destination organization and its resolved code.
• SOURCE_ORGANIZATION_ID – the supplying organization where the source type is a make/transfer source.
• PARTNER_ID, PARTNER_NAME, SUPPLIER_SITE_ID – supplier and supplier site for buy sources.
• SOURCE_TYPE, SOURCING_RULE_TYPE, ASSIGNMENT_TYPE – source and rule classification, with lookup meaning columns added by MSC_GET_NAME.
• ALLOCATION_PERCENT, RANK, CONVERSION_FACTOR, AVG_TRANSIT_LEAD_TIME – sourcing allocation, ranking, conversion, and transit lead time attributes.
• EFFECTIVE_DATE, DISABLE_DATE – validity window of the sourcing rule.
• SOURCING_RULE_ID, SOURCING_RULE_NAME, ASSIGNMENT_ID, ASSIGNMENT_SET_ID – rule and assignment identity.
• SHIP_METHOD, HISTORICAL_ALLOC_QTY – shipping method and historical allocation quantity.
• Category fields (CATEGORY_SET_ID, SR_CATEGORY_ID) – category assignment context.

Common Use Cases and Queries

Typical uses include auditing sourcing rules per plan and organization, reconciling supplier-site assignments, producing descriptive extracts for planning integrations, and validating effective/disable date windows. The following query lists sourcing rules for a given item, including segment values and organization codes:

SELECT ORGANIZATION_CODE,
       ITEM_SEGMENTS,
       SOURCE_TYPE,
       SOURCING_RULE_NAME,
       PARTNER_NAME,
       ALLOCATION_PERCENT,
       RANK,
       EFFECTIVE_DATE,
       DISABLE_DATE
FROM   APPS.MSC_ITEM_SOURCING_V
WHERE  INVENTORY_ITEM_ID = :p_item_id
AND    PLAN_ID           = :p_plan_id
AND    SYSDATE BETWEEN NVL(EFFECTIVE_DATE, SYSDATE - 1)
                   AND NVL(DISABLE_DATE, SYSDATE + 1)
ORDER BY ORGANIZATION_CODE, RANK;

A second common pattern filters by assignment to review rule coverage by assignment type, joining the view to category or item master data as needed. Because the view resolves IDs to codes and names through MSC_GET_NAME, it is well suited to read-only reporting and interface extracts; however, it should not be used as a transactional update source, since the underlying MSC tables are populated and refreshed by the planning data collections and engine processes.