Search Results msc_scatp_item_sr_levels_v




Overview

MSC_SCATP_ITEM_SR_LEVELS_V is an Advanced Supply Chain Planning (MSC) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents sourcing rule assignments that are resolved at the item and organization level, keyed by assignment type 6 (ITEM-ORG). The view exists to flatten the multi-table sourcing model — system items, sourcing rules, receipt organizations, source organizations, assignments, and trading partner site identifiers — into a single denormalized row set that planning and ATP (Available-to-Promise) engines can query efficiently.

Its role is primarily internal to the SATP (Sourcing and ATP) processing logic. The view supplies the resolved sourcing hierarchy used by the supply chain planning engine to determine valid source organizations, vendors, allocation percentages, and effective date windows for an item within a given organization. Because the rows are filtered to active sourcing rules and to receipt organizations whose effective and disable dates bracket the current system date, the view reflects only sourcing that is valid at runtime.

Underlying Base Objects

The view is defined over the following documented base objects, most exposed through APPS synonyms:

Because the view is read-only aggregation of these objects, it inherits their security and indexing characteristics and should be treated as a planning-internal construct rather than a transactional table.

Key Columns

Common Use Cases and Queries

The most frequent use is resolving the valid sourcing path for a specific item and organization during ATP or planning diagnostics:

  • Item-org sourcing lookup: SELECT sourcing_rule_name, source_organization_id, allocation_percent, rank FROM msc_scatp_item_sr_levels_v WHERE inventory_item_id = :item AND source_organization_id = :org;
  • Vendor sourcing resolution: query VENDOR_ID and VENDOR_SITE_ID for a given item to identify approved external sources and their allocation splits.
  • Validity auditing: inspect EFFECTIVE_DATE and DISABLE_DATE to confirm which sourcing assignments are currently in force, since the view already filters on SYSDATE.
  • Allocation analysis: aggregate RANK and ALLOCATION_PERCENT across rows to validate that percentage allocations for a rule sum appropriately.

Queries should always filter on INVENTORY_ITEM_ID or SOURCE_ORGANIZATION_ID to avoid full scans, given the joins across the sourcing tables. The view is not designed for direct DML; write-back is performed through the SATP package APIs.