Search Results sourcing_level




Overview
Explore in AI Chat

Overview

APPS.MSC_SCATP_SOURCES_V is a reporting and integration view within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) and available-to-promise (ATP) schema. Its functional role is to expose the winning, or highest-priority, sourcing assignment for a given planning combination of item, ship-to site, session, and assignment set. It is defined as a thin filter view over MSC_SCATP_ITEM_SR_LEVELS_V, retaining only those rows whose SOURCING_LEVEL equals the minimum SOURCING_LEVEL found for the same key combination. In practice, the parent view produces a multi-level ranked list of sourcing candidates (organization, vendor, and related rule attributes), and MSC_SCATP_SOURCES_V collapses that list to the single lowest-ranked-level record, which represents the preferred source.

Because the view carries sourcing rule attributes such as ALLOCATION_PERCENT, RANK, EFFECTIVE_DATE, DISABLE_DATE, SOURCE_TYPE, and SOURCING_RULE_NAME, it is used by planning engines, ATP/scheduling logic, and downstream integrations that require the authoritative source for replenishment or demand satisfaction. The referenced package MSC_SATP_FUNC supplies supporting scheduling and ATP utility logic used throughout the SATP family of objects.

Underlying Base Objects

Per the documented ETRM metadata, the view references two base objects:

  • MSC_SCATP_ITEM_SR_LEVELS_V (VIEW) — the immediate source of all projected columns. MSC_SCATP_SOURCES_V performs no joins or transformations beyond the correlated subquery that selects the minimum sourcing level.
  • MSC_SATP_FUNC (PACKAGE) — the scheduling/ATP function package associated with the SATP object family, providing the procedural context in which these sourcing levels are generated and consumed.

The defining query selects the full column list from MSC_SCATP_ITEM_SR_LEVELS_V (aliased MSISLV) and applies a WHERE clause that correlates a nested subquery on SHIP_TO_SITE_ID, INVENTORY_ITEM_ID, SESSION_ID, and ASSIGNMENT_SET_ID. This means the view's cardinality is one row per distinct combination of those four attributes, assuming ties are resolved consistently. The SESSION_ID column indicates the view is session-scoped, so results are valid only within the planning or ATP session that populated the underlying levels view.

Key Columns

  • INVENTORY_ITEM_ID — the planned item.
  • SOURCING_LEVEL — the numeric priority level; the view retains only the minimum value, making it the definitive ranking column.
  • SOURCING_RULE_TYPE / SOURCING_RULE_ID / SOURCING_RULE_NAME — identify the sourcing rule that produced the assignment.
  • ASSIGNMENT_TYPE / ASSIGNMENT_SET_ID / ASSIGNMENT_ID — describe the assignment grouping and set context.
  • SOURCE_TYPE / SOURCE_ORGANIZATION_ID / SOURCE_ORG_INSTANCE_ID — characterize the supplying organization source.
  • VENDOR_ID / VENDOR_SITE_ID — populated when the source is an external supplier.
  • ALLOCATION_PERCENT / RANK — allocation split and ordering within the rule.
  • EFFECTIVE_DATE / DISABLE_DATE — validity window of the assignment.
  • CATEGORY_ID, CUSTOMER_ID, SHIP_TO_SITE_ID, REGION_ID — planning dimensions that scope the assignment.
  • SESSION_ID — ties rows to the originating planning session.

Common Use Cases and Queries

Typical scenarios include retrieving the preferred source for an item at a ship-to site, validating that a sourcing rule resolved to an organization rather than a vendor, and feeding ATP or order promising processes with the authoritative source. A representative query follows:

  • SELECT inventory_item_id, ship_to_site_id, source_type, source_organization_id, vendor_id, vendor_site_id, allocation_percent, sourcing_rule_name FROM apps.msc_scatp_sources_v WHERE inventory_item_id = :item AND ship_to_site_id = :site;
  • SELECT inventory_item_id, sourcing_level, source_type FROM apps.msc_scatp_sources_v WHERE session_id = :session ORDER BY inventory_item_id;

Because the view is session-scoped and restricted to the minimum sourcing level, queries should always constrain SESSION_ID (and ideally item and site) to obtain performant and meaningful results.