Results for “msc_sr_assignments_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_SR_ASSIGNMENTS_V is an APPS-owned view within the MSC – Advanced Supply Chain Planning product family in Oracle EBS 12.1.1 and 12.2.2. It presents sourcing rule assignment data maintained by Advanced Supply Chain Planning (ASCP), exposing the association between a sourcing rule and the organizational entity to which it applies. Sourcing rule assignments determine which sourcing rules govern replenishment, procurement, transfer, or manufacturing behavior for a given organization, category, or item, and they carry the SOURCING_RULE_TYPE attribute that classifies the rule (for example, transfer from another organization, buy from a supplier, or make at a manufacturing facility).

The view serves reporting and integration purposes. Planners, supply chain analysts, and implementation teams query it to audit which sourcing rule is assigned to which organization, customer, or item, and to reconcile ASCP sourcing configuration against execution systems. Because it joins descriptive lookups and name-resolution functions, it returns human-readable values alongside the raw identifiers, making it suitable for BI Publisher reports, OBIEE/OTBI extracts, and custom concurrent programs. It is a read-only view and therefore carries no DML semantics. In the context of the search term mrp_sourcing_rule_type, this view is the primary ASCP-side repository exposing the sourcing rule type code and its decoded meaning.

Underlying Base Objects

The view is defined over the following documented base objects:

• MSC_SR_ASSIGNMENTS (synonym) – the principal table, aliased MSRA, supplying assignment identifiers, assignment type, sourcing rule identifiers, organization, partner, ship-to site, category, and item columns together with WHO columns and the descriptive flexfield attributes (ATTRIBUTE_CATEGORY through ATTRIBUTE15).
• MSC_SOURCING_RULES (synonym) – aliased MSR, providing SOURCING_RULE_NAME.
• MSC_TRADING_PARTNER_SITES (synonym) – aliased MST, supplying PARTNER_ADDRESS for the ship-to address.
• MFG_LOOKUPS (view) – aliased ML, providing the decoded MEANING for SOURCING_RULE_TYPE_TEXT.
• MSC_DRP_ALLOC_RULES and MSC_REGIONS (synonyms) – supporting distribution planning and region references.
• MSC_GET_NAME (package) – a name-resolution PL/SQL package invoked through functions such as ORG_CODE, INSTANCE_CODE, CUSTOMER, ITEM_NAME, CATEGORY_DESC, and ITEM_DESC to translate internal identifiers into display values.

Key Columns

• ASSIGNMENT_ID / ASSIGNMENT_SET_ID – primary identifier for the assignment and the set to which it belongs.
• ASSIGNMENT_TYPE – numeric discriminator whose values 1 through 6 drive the DECODE logic that returns ENTITY_NAME and DESCRIPTION; different values represent organization, category, item, customer, and related assignment scopes.
• ORGANIZATION_ID / ORGANIZATION_CODE – the owning organization; ORGANIZATION_CODE is derived via MSC_GET_NAME, returning NULL when ASSIGNMENT_TYPE equals 3.
• CUSTOMER_ID / CUSTOMER_NAME – partner identifier and resolved customer name.
• SHIP_TO_SITE_ID / SHIP_TO_ADDRESS – ship-to site and its formatted address from MSC_TRADING_PARTNER_SITES.
• ENTITY_NAME / DESCRIPTION – context-sensitive labels and descriptions resolved by assignment type.
• SOURCING_RULE_TYPE / SOURCING_RULE_TYPE_TEXT – the numeric sourcing rule type code and its lookup meaning.
• SOURCING_RULE_ID / SOURCING_RULE_NAME – the sourcing rule applied by the assignment.
• CATEGORY_NAME / CATEGORY_SET_ID / INVENTORY_ITEM_ID – the category or item targeted by the assignment.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE – concurrent program audit columns.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY – standard WHO audit columns.

Common Use Cases and Queries

A typical requirement is to list all sourcing rule assignments for an organization with decoded types:

SELECT organization_code, sourcing_rule_name,
       sourcing_rule_type_text, entity_name
FROM   apps.msc_sr_assignments_v
WHERE  organization_id = :org_id;

To isolate assignments of a specific type — for example, buy-from-supplier rules — filter on SOURCING_RULE_TYPE or the decoded text:

SELECT sourcing_rule_name, organization_code, customer_name
FROM   apps.msc_sr_assignments_v
WHERE  sourcing_rule_type_text = 'Buy';

Analysts also reconcile assignments against execution-side sourcing by joining SOURCING_RULE_ID to MRP sourcing rule definitions, and audit configuration changes using the PROGRAM_UPDATE_DATE and LAST_UPDATE_DATE columns. Because the view includes ATTRIBUTE1 through ATTRIBUTE15, it can support attribute-driven reporting where descriptive flexfields are populated.

Users should note that organization and item name resolution depends on MSC_GET_NAME and may return NULL where the assignment type does not apply, as reflected in the DECODE logic for ASSIGNMENT_TYPE values 1 through 6.