Search Results msc_assignment_sets




Overview
Explore in AI Chat

Overview

The MSC_ASSIGNMENT_SETS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the master definition table for sourcing rule assignments, a critical component of supply chain planning. An assignment set is a logical container that groups together specific sourcing rules (or bills of distribution) and defines their applicability to various entities within the supply chain. These entities can be individual items, entire organizations, item categories, or a global default. During a planning run, the planning engine references a specified assignment set to determine the appropriate sourcing instructions for material flow, making this table fundamental to modeling the supply network.

Key Information Stored

The table's primary purpose is to define and identify distinct assignment sets. Its most critical column is the ASSIGNMENT_SET_ID, which serves as the unique primary key for each set. While the provided metadata does not list all columns, typical supporting columns in such a table would include fields for the assignment set name, a description, an effective date range (from/to), and a status indicator (e.g., active, inactive). The table does not store the detailed assignment rules themselves; instead, it provides the header under which those specific assignments, stored in related tables like MSC_SR_ASSIGNMENTS, are organized.

Common Use Cases and Queries

The primary use case is the creation and maintenance of sourcing strategies for planning. Analysts create different assignment sets to model various sourcing scenarios, such as a primary set for normal operations and an alternate set for contingency planning. A common reporting need is to list all active assignment sets available for use in a plan. A typical query would be:

  • SELECT assignment_set_id, name, description, effective_date, disable_date FROM msc_assignment_sets WHERE SYSDATE BETWEEN effective_date AND NVL(disable_date, SYSDATE);

Another critical operation is identifying which specific plan or assignment records depend on a given set, which involves joining to its foreign key references. For instance, to find plans using a specific assignment set, one would join MSC_PLANS.ASSIGNMENT_SET_ID to MSC_ASSIGNMENT_SETS.ASSIGNMENT_SET_ID.

Related Objects

MSC_ASSIGNMENT_SETS has defined relationships with several other key planning tables, as indicated by the foreign key metadata. The MSC_PLANS table references it via MSC_PLANS.ASSIGNMENT_SET_ID, linking a specific plan instance to the sourcing rule set it should use. More directly, the MSC_SR_ASSIGNMENTS table references it via MSC_SR_ASSIGNMENTS.ASSIGNMENT_SET_ID. This table holds the detailed assignment lines—the actual mapping of a sourcing rule to an item, organization, or category—that belong to a parent set defined in MSC_ASSIGNMENT_SETS. Therefore, the data model follows a header-detail relationship: MSC_ASSIGNMENT_SETS (header) to MSC_SR_ASSIGNMENTS (detail).