Results for “mrp_sourcing_rule_type”

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

Overview

APPS.MSC_ITEM_SOURCING_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a forms-coding simplification layer, exposing a denormalized, human-readable projection of sourcing-rule assignment data maintained by Oracle Advanced Supply Chain Planning (ASCP) and the ETRM (Enterprise Territory and Resource Management) planning stack. The view consolidates planning instance context, item and organization details, sourcing-rule definitions, supplier and supplier-site identifiers, allocation percentages, ranks, and quantities into a single queryable structure. Because it is a supplementary view created to simplify forms coding, Oracle explicitly warns that it should not be queried or altered directly for transactional purposes, since its definition may change dramatically between minor or major releases. In practice, the view is most valuable for read-only reporting, data extraction, and integration logic where the caller requires an already-joined, decoded representation of item sourcing assignments rather than normalized base tables. The PLAN_INSTANCE_ID column — the term the user searched for — is central to this purpose, as it ties each sourcing row to a specific executed plan instance in the planning engine, enabling plan-scoped sourcing analysis.

Underlying Base Objects

The view is defined over a set of documented base objects, most of which are exposed through synonyms in the APPS schema. These include MSC_APPS_INSTANCES, MSC_ITEMS, MSC_ITEM_CATEGORIES, MSC_ITEM_SOURCING, MSC_PLANS, MSC_SOURCING_RULES, MSC_TRADING_PARTNERS, and MSC_TRADING_PARTNER_SITES. It also references the MSC_GET_NAME package, which is used to resolve coded numeric values into descriptive text (for example, item type, source type, assignment type, ship method, and sourcing rule type text columns). MSC_ITEM_SOURCING is the principal driving table, holding the assignment records; MSC_ITEMS and MSC_ITEM_CATEGORIES supply item and category context; MSC_PLANS and MSC_APPS_INSTANCES provide plan and plan-instance framing; MSC_SOURCING_RULES supplies rule names and rule-type decoding; and the trading-partner tables supply vendor and vendor-site names and codes. The joins across these objects allow the view to present a single row per sourcing assignment enriched with descriptive attributes.

Key Columns

• PLAN_ID, PLAN_ORGANIZATION_ID, PLAN_INSTANCE_ID — Planning plan, plan organization, and specific plan instance identifiers. PLAN_INSTANCE_ID is the primary filter for isolating a single planning run.
• INVENTORY_ITEM_ID, ITEM_SEGMENTS — Item identifier and the concatenated item segment string.
• ORGANIZATION_ID, ORGANIZATION_CODE — Destination organization key and its decoded code.
• SOURCE_ORGANIZATION_ID, SOURCE_ORGANIZATION_CODE, SOURCE_SR_INSTANCE_ID — Source organization and sourcing-rule instance context.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE, SUPPLIER_ID, SUPPLIER_SITE_ID — Supplier and supplier-site identity and descriptive names.
• SOURCE_TYPE, SOURCE_TYPE_TEXT — Coded and decoded sourcing source type (for example, inventory or supplier).
• SOURCING_RULE_ID, SOURCING_RULE_NAME, SOURCING_RULE_TYPE, SOURCING_RULE_TYPE_TEXT — Sourcing rule identity, name, and type decoding.
• ALLOCATION_PERCENT, RANK, QUANTITY, HISTORICAL_ALLOC_QTY — Allocation, ranking, and quantity metrics used to apportion supply.
• ASSIGNMENT_ID, ASSIGNMENT_SET_ID, ASSIGNMENT_TYPE, ASSIGNMENT_TYPE_TEXT, ASSIGNMENT_SET_TYPE, ASSIGNMENT_SET_TYPE_TEXT — Assignment grouping and type decoding.
• EFFECTIVE_DATE, DISABLE_DATE — Validity window for the sourcing assignment.
• SHIP_METHOD, SHIP_METHOD_TEXT, AVG_TRANSIT_LEAD_TIME — Shipping method and average transit lead time.
• CIRCULAR_SRC, CIRCULAR_SRC_RANK — Flags and rank for circular sourcing detection.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — Audit columns.

Common Use Cases and Queries

Typical uses include plan-scoped sourcing extracts, supplier allocation reports, and integration feeds into downstream planning or procurement systems. A representative query filtering by the searched column is:

SELECT plan_instance_id, inventory_item_id, item_segments, organization_code,
       source_organization_code, vendor_name, vendor_site_code,
       source_type_text, sourcing_rule_name, ranking, allocation_percent, quantity
FROM  apps.msc_item_sourcing_v
WHERE  plan_instance_id = :p_plan_instance_id
ORDER BY organization_code, item_segments, rank;

A second common pattern reports supplier allocation across a plan instance:

SELECT vendor_name, sourcing_rule_name, SUM(allocation_percent) alloc_pct
FROM  apps.msc_item_sourcing_v
WHERE  plan_instance_id = :p_plan_instance_id
GROUP BY vendor_name, sourcing_rule_name;

Because the view decodes coded values into descriptive text, it reduces the need for consumers to join MSC_SOURCING_RULES, MSC_TRADING_PARTNERS, and package-based name resolution manually. Nevertheless, Oracle's documented warning should be respected: treat this as a reporting convenience view, avoid DML through it, and validate its columns against the target EBS release before embedding it in production integrations, as its structure may change across minor or major upgrades.