Search Results msc_sr_view_v

Overview

MSC_SR_VIEW_V is a lightweight database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC (Advanced Supply Chain Planning) product family. Its status is VALID across both the 12.1.1 and 12.2.2 releases. The view exposes a simplified, two-column projection of sourcing rule data: the sourcing rule identifier and its user-facing name. In practice it functions as a convenient name-lookup view, allowing reports, concurrent programs, and integration interfaces to resolve a sourcing rule ID into a readable sourcing rule name without directly querying the underlying configuration table.

The view is significant because sourcing rules are central to Advanced Supply Chain Planning. A sourcing rule defines the assignment of supply sources to demand, specifying which organization, supplier, or transfer path should satisfy demand within a given planning horizon. External systems, custom reports, and Oracle's own planning flows frequently need to display or match sourcing rules by name. Rather than joining against the full rules table, developers and analysts can query MSC_SR_VIEW_V for a clean, focused result set. This makes it a common target when users search for metadata using the term "sourcing_rule_name," since that column is directly exposed by the view.

Underlying Base Objects

The view text is defined as a direct selection from the base object MSC_SOURCING_RULES:

• MSC_SOURCING_RULES — referenced as a SYNONYM within the APPS schema and documented as the sole base object behind MSC_SR_VIEW_V. In ETRM 12.2.2 this object is the parent of the view.

MSC_SOURCING_RULES is the primary Advanced Supply Chain Planning table that stores sourcing rule definitions, including assignment sets, rule identifiers, and descriptive attributes. MSC_SR_VIEW_V projects only two of its columns, deliberately narrowing the surface exposed to consumers. Because the view is built on a synonym, the reference resolves to the underlying MSC table at runtime, and the view inherits the data visibility and any row-level behavior applicable to that table within the APPS schema. No joins, filters, or aggregation are documented in the view text, so it preserves the row cardinality of MSC_SOURCING_RULES.

Key Columns

The view exposes two columns, both documented in the ETRM metadata:

• SOURCING_RULE_ID — the unique numeric identifier for a sourcing rule. It is the primary key-like reference used to associate the rule with other planning entities, such as assignment sets, sourcing assignments, and plan data. This is the value typically stored as a foreign key elsewhere in MSC.
• SOURCING_RULE_NAME — the descriptive, user-visible name of the sourcing rule. This is the column most frequently used for display, sorting, and lookup. Because users often know a sourcing rule by name rather than by ID, this column is the practical reason the view was created and the reason searches for "sourcing_rule_name" resolve to it.

No additional filtering or derived columns are documented, so consumers should not expect status, effective dates, or assignment context from this view; those attributes must be obtained from MSC_SOURCING_RULES or related MSC tables.

Common Use Cases and Queries

MSC_SR_VIEW_V supports several practical scenarios. Report developers use it to present sourcing rule names on planning dashboards and exception reports. Integration and interface code use it to translate an inbound or outbound SOURCING_RULE_ID into a human-readable name. DBAs and support analysts use it for quick verification that a sourcing rule exists and is correctly named before troubleshooting planning behavior.

A typical lookup by name:

• SELECT sourcing_rule_id, sourcing_rule_name FROM apps.msc_sr_view_v WHERE sourcing_rule_name = :p_rule_name;

A typical resolution by ID:

• SELECT sourcing_rule_name FROM apps.msc_sr_view_v WHERE sourcing_rule_id = :p_rule_id;

Because the view performs no filtering, it can also be used to populate list-of-values sources or to drive join clauses in custom planning extracts, with the caveat that additional sourcing attributes require joining back to MSC_SOURCING_RULES. In all cases, access should be granted through the APPS schema or the appropriate MSC responsibility, consistent with standard EBS security practice. The view remains valid and available in both 12.1.1 and 12.2.2, making it a stable reference for sourcing rule name resolution across releases.