Search Results source_org




Overview

MSC_ITEM_TASK_SR_LEVELS_V is an Advanced Supply Chain Planning (MSC) view owned by the APPS schema that flattens the sourcing hierarchy for a given item into a single denormalized result set. It assembles sourcing assignments, sourcing rules, and the source and receipt organization details into one row per item/sourcing-level combination, adding a SOURCING_LEVEL column and the resolved plan context (via MSC_PLAN_ORGANIZATIONS_V) so downstream consumers can evaluate which organizations are permitted to supply a planning item.

The view is used internally by planning and sourcing-level resolution logic and by custom reporting that needs to present sourcing hierarchies in a report-friendly shape. Because the query carries an explicit ORDERED hint plus INDEX and USE_NL hints pinning the assignment lookup to the MSC_SR_ASSIGNMENTS_U2 index, the view is sensitive to index availability on the underlying objects — a point directly relevant to the search term msc_sr_assignments_u2. If that index is dropped, rebuilt, or disabled, the nested-loops plan degraded and view performance changes measurably.

Underlying Base Objects

The view is defined against the following documented base objects, joined via nested loops in the order hinted:

  • MSC_SR_ASSIGNMENTS (synonym) — sourcing-rule assignments linking items to assignment sets; drives the MSC_SR_ASSIGNMENTS_U2 index access.
  • MSC_SOURCING_RULES (synonym) — the sourcing rule header, supplying rule type, name, and description.
  • MSC_SR_RECEIPT_ORG (synonym) — receipt organization and effective/disable date information.
  • MSC_SR_SOURCE_ORG (synonym) — the actual source organization, partner, rank, allocation percent, and source type.
  • MSC_SYSTEM_ITEMS (synonym) — the planning item master (ITEMS) and a second instance (COMP_ITEMS) referenced at PLAN_ID = -1 for item attribute resolution.
  • MSC_PLAN_ORGANIZATIONS_V (view) — supplies plan context and compile designator.
  • MSC_ITEM_CATEGORIES and MSC_TRADING_PARTNERS (synonyms) — supporting objects used in the sourcing/partner resolution.

The join conditions tie items to assignments on SR_INSTANCE_ID, INVENTORY_ITEM_ID, and ORGANIZATION_ID, then link source organizations to receipt organizations through SR_RECEIPT_ID.

Key Columns

Common Use Cases and Queries

Typical uses include verifying which source organizations a planning item can source from, auditing sourcing-rule assignments, and feeding custom reports. A representative query:

  • SELECT inventory_item_id, organization_id, sourcing_rule_name, source_organization_id, allocation_percent, rank FROM msc_item_task_sr_levels_v WHERE inventory_item_id = :item_id;
  • SELECT sourcing_rule_name, COUNT(*) FROM msc_item_task_sr_levels_v GROUP BY sourcing_rule_name ORDER BY 2 DESC;
  • SELECT v.inventory_item_id, v.source_organization_id, v.effective_date FROM msc_item_task_sr_levels_v v WHERE SYSDATE BETWEEN v.effective_date AND NVL(v.disable_date, SYSDATE + 1);

Performance depends on the availability and validity of the MSC_SR_ASSIGNMENTS_U2 index and the other indexes named in the view's hint block; concurrent maintenance, statistics, or index rebuilds on those objects should be scheduled with awareness of this dependency.