Search Results msc_sr_source_org_v




Overview
Explore in AI Chat

Overview

MSC_SR_SOURCE_ORG_V is a reporting and integration view owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product family. It exposes sourcing rule source organization data, presenting the source-side detail of sourcing rules as consumed by Oracle Advanced Supply Chain Planning and related supply chain execution flows. Sourcing rules define where a demand or supply is sourced from—an organization, a supplier, or a supplier site—and this view consolidates that information into a form suitable for inquiry, reporting, and downstream integration.

The view is documented as VALID in Oracle EBS 12.1.1 and 12.2.2 and is referenced primarily for read-only retrieval. It is not a transactional entity; instead it projects descriptive attributes such as organization codes, vendor names, vendor site identifiers, allocation percentages, sourcing ranks, and ship method lead times. The presence of a ROW_ID column reflects a rowid-based construction typical of Oracle Forms-based inquiry views, enabling the form to associate each displayed row with its underlying physical record.

Underlying Base Objects

The documented base objects for MSC_SR_SOURCE_ORG_V are the MSC_GET_NAME package, used here as a naming/decoding utility, and the synonym MSC_SR_SOURCE_ORG, which resolves to the sourcing rule source organization table. The view is defined by a SELECT that joins MSC_SR_SOURCE_ORG (aliased S) with MSC_INTERORG_SHIP_METHODS (aliased SM) on SHIP_METHOD, applying an outer join so that source lines without a matching ship method are still returned.

The join is further constrained so that SM.PLAN_ID equals -1, and the matching of organization and instance identifiers is controlled through DECODE logic keyed on SOURCE_TYPE. This allows the view to correctly align internal organization sources, supplier sources, and supplier-site sources with the appropriate interorganization ship method record. A correlated subquery against MSC_SR_RECEIPT_ORG resolves the receiving organization for each receipt, ensuring the ship method is validated against the correct destination. The MSC_GET_NAME package functions supply decoded values such as ORG_CODE, SUPPLIER, and SUPPLIER_SITE.

Key Columns

Common Use Cases and Queries

Typical use cases include validating sourcing rule setup, reporting allocation across multiple sources, and diagnosing ship method and lead-time configuration. The view is commonly queried directly rather than through a form.

SELECT source_organization_code,
       vendor_name,
       vendor_site,
       source_type,
       allocation_percent,
       rank,
       ship_method,
       intransit_time
FROM   apps.msc_sr_source_org_v
WHERE  sr_source_id = :p_sr_source_id
ORDER  BY rank;

A second common pattern filters by organization to review all sourcing defined from a given source:

SELECT sr_receipt_id,
       source_organization_code,
       allocation_percent,
       rank
FROM   apps.msc_sr_source_org_v
WHERE  source_organization_id = :p_org_id;

Because the view incorporates the MSC_GET_NAME package for decoding, queries against it carry the overhead of those function calls; for large extracts, restricting by SR_SOURCE_ID or SOURCE_ORGANIZATION_ID materially improves performance.