Search Results msc_sr_assignments

Overview

The MSC_SR_ASSIGNMENTS table is a core data repository within Oracle E-Business Suite's Advanced Supply Chain Planning (ASCP) module. It functions as the central table for managing and storing sourcing rule assignments, a critical component of supply chain planning. The table's role is to define the linkage between a sourcing rule (or bill of distribution) and the specific entities to which that rule applies. These assignments can be made at various levels of granularity, including a specific item, an organization, an item category, or globally, enabling planners to model complex, multi-tiered supply networks.

Key Information Stored

The table's primary purpose is to capture the context of a sourcing assignment. Its key columns include the unique ASSIGNMENT_ID, which serves as the primary key. The SOURCING_RULE_ID is a critical foreign key that links to the MSC_SOURCING_RULES table, identifying the specific sourcing strategy being applied. The ASSIGNMENT_SET_ID groups multiple assignments together for management and reporting. To define the scope of the assignment, the table holds identifiers such as INVENTORY_ITEM_ID, ORGANIZATION_ID, CATEGORY_SET_ID, and CATEGORY_ID. Furthermore, it stores partner information via PARTNER_ID and SHIP_TO_SITE_ID to specify the supplier and destination within the trading partner relationship, allowing for precise definition of sourcing paths from a specific source to a specific destination.

Common Use Cases and Queries

A primary use case is analyzing the sourcing strategy for a specific item or organization to validate planning inputs. Planners and analysts frequently query this table to audit assignments, troubleshoot planning results, or generate custom reports. Common SQL patterns involve joining to related master data tables to translate IDs into meaningful names. For example, to list all sourcing rule assignments for a specific item, a query would join MSC_SR_ASSIGNMENTS to MSC_SOURCING_RULES and MSC_SYSTEM_ITEMS. Another typical scenario is identifying all assignments within a specific assignment set for migration or comparison purposes. Reporting often focuses on the hierarchy of assignments, showing whether a given item is sourced via a rule assigned directly to it, to its category, or to its organization.

Related Objects

MSC_SR_ASSIGNMENTS is a central hub within the ASCP data model with several documented foreign key relationships. The most significant dependencies are:

• MSC_SOURCING_RULES: Joined via SOURCING_RULE_ID to retrieve the definition of the sourcing rule (MSC_SR_ASSIGNMENTS.SOURCING_RULE_ID = MSC_SOURCING_RULES.SOURCING_RULE_ID).
• MSC_ASSIGNMENT_SETS: Joined via ASSIGNMENT_SET_ID to group assignments (MSC_SR_ASSIGNMENTS.ASSIGNMENT_SET_ID = MSC_ASSIGNMENT_SETS.ASSIGNMENT_SET_ID).
• MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES: Joined via PARTNER_ID and SHIP_TO_SITE_ID to resolve trading partner details.
• MSC_CATEGORY_SETS: Joined via CATEGORY_SET_ID for category-based assignments.
• MSC_ITEM_SOURCING: This table has a foreign key referencing MSC_SR_ASSIGNMENTS.ASSIGNMENT_ID, indicating it consumes the assignment data to determine item-specific sourcing during the planning run.