Search Results msc_sr_view_con_v

Overview

MSC_SR_VIEW_CON_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered as part of the MSC (Advanced Supply Chain Planning) product family. Within the ETRM 12.1.1 and 12.2.2 object repositories, the view carries a VALID status and is documented as a lightweight projection over sourcing-rule receipt-organization data. Rather than storing or transforming business data, the view exposes a deduplicated set of sourcing-rule-to-receipt-organization associations that supporting planning logic, concurrent programs, and reporting queries can consume without joining the underlying synonym directly.

Its role in the EBS integration layer is essentially that of a convenience access point. Because the Advanced Supply Chain Planning module resolves sourcing rules against receipt organizations when determining where supply should be received, a stable, narrow view of those mappings simplifies downstream SQL and insulates callers from the physical storage of the base object. A user searching on receipt_organization_id would typically arrive here while investigating how sourcing rules are tied to specific inventory organizations in a planning context.

Underlying Base Objects

The documented view definition is a single-statement SELECT DISTINCT over one referenced object:

• MSC_SR_RECEIPT_ORG — referenced as a SYNONYM in the APPS schema. This is the sole base object behind MSC_SR_VIEW_CON_V, holding the sourcing-rule and receipt-organization relationships that the view republishes.

Because the view performs a DISTINCT over the base synonym, it collapses duplicate rows present in MSC_SR_RECEIPT_ORG. This means the view should be treated as a read-only, deduplicated snapshot rather than a fully faithful copy of the table; row counts can differ from the underlying object. No joins to other tables, no aggregation, and no filtering predicates are documented, so the view is structurally coupled to the columns present in MSC_SR_RECEIPT_ORG and will remain dependent on that synonym's definition and privileges.

Key Columns

The documented metadata lists three exposed columns. Note that the view's declared SELECT list and its column metadata are not identical in naming, which is a common EBS view-consolidation pattern:

• SOURCING_RULE_ID — the identifier of the sourcing rule whose receipt-organization assignment is being described. This is the principal correlation key for joining back to sourcing-rule definitions.
• RECEIPT_ORGANIZATION_ID — the receipt organization associated with the sourcing rule. Although the SELECT text aliases this as SR_RECEIPT_ORG, the documented column metadata exposes it as RECEIPT_ORGANIZATION_ID, the identifier that resolved the user's search.
• RECEIPT_ORG_INSTANCE_ID — an instance identifier for the receipt organization, distinguishing organization instances where the same organization participates across logical instances or planning partitions.

Consumers should rely on the documented metadata names (SOURCING_RULE_ID, RECEIPT_ORGANIZATION_ID, RECEIPT_ORG_INSTANCE_ID) when writing queries, since Oracle exposes the view's columns under those names.

Common Use Cases and Queries

Typical uses include validating which receipt organizations a sourcing rule can deliver to, reconciling planning output against organization assignments, and driving sourcing-derived reporting. A basic query retrieving all receipt organizations for a given sourcing rule:

• SELECT sourcing_rule_id, receipt_organization_id, receipt_org_instance_id FROM apps.msc_sr_view_con_v WHERE sourcing_rule_id = :p_rule_id ORDER BY receipt_organization_id;
• SELECT receipt_organization_id, COUNT(*) FROM apps.msc_sr_view_con_v GROUP BY receipt_organization_id; — to measure how many sourcing rules reference each organization.
• SELECT v.sourcing_rule_id, v.receipt_organization_id FROM apps.msc_sr_view_con_v v, apps.msc_sr_receipt_org r WHERE v.sourcing_rule_id = r.sourcing_rule_id; — comparing the deduplicated view against the base synonym.

Because the view is read-only and DISTINCT-filtered, it is safe for reporting and validation joins; no DML should ever be directed against it. Where instance-level distinction is required, filter or group by RECEIPT_ORG_INSTANCE_ID.