Search Results msc_item_sourcing




Overview
Explore in AI Chat

Overview

The MSC_ITEM_SOURCING table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the primary table for storing and managing sourcing rules and assignments that govern how items are procured or transferred across the supply network during the planning process. Its role is critical for the planning engine to determine the optimal source of supply—be it from a specific supplier, a manufacturing organization, or a distribution center—for each item at a given organization. As noted in the documentation, this table also extends its functionality to support In Line Vehicle Sequencing (ILVS) within the Supply Chain Hub product, highlighting its importance in complex, configurable supply chain environments.

Key Information Stored

The table's structure is defined by its relationships to other master planning entities. While specific column details are not fully enumerated in the provided metadata, the foreign key relationships clearly indicate the critical data elements stored. Each record uniquely identifies a sourcing assignment for a specific item within a planning context. The key identifiers include the INVENTORY_ITEM_ID, ORGANIZATION_ID, SR_INSTANCE_ID (system instance), and PLAN_ID, which together link to the item definition in MSC_SYSTEM_ITEMS. The core sourcing logic is referenced via the SOURCING_RULE_ID (linking to MSC_SOURCING_RULES) and the ASSIGNMENT_ID (linking to MSC_SR_ASSIGNMENTS). For external sourcing, the table stores supplier details via SUPPLIER_ID and SUPPLIER_SITE_ID, which reference the MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES tables, respectively.

Common Use Cases and Queries

This table is central to planning analyses and troubleshooting. A common use case is auditing the effective sourcing rules for a set of items in a specific plan to validate planning inputs. For example, a planner may need to list all sourced items from a particular supplier site. A typical query would join MSC_ITEM_SOURCING with MSC_SYSTEM_ITEMS for item details and MSC_TRADING_PARTNERS for supplier names. Another critical scenario involves performance tuning or data cleanup, where identifying orphaned sourcing records not linked to a valid plan or item is necessary. Developers may also query this table to understand the sourcing data footprint before launching a planning run, ensuring all required assignments are present and correctly prioritized.

Related Objects

The MSC_ITEM_SOURCING table maintains integral relationships with several other planning base tables, as documented by its foreign keys:

  • MSC_SYSTEM_ITEMS: Joined via INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID. This is the primary relationship to the item master.
  • MSC_SOURCING_RULES: Joined via SOURCING_RULE_ID. Links to the definition of the sourcing rule itself.
  • MSC_SR_ASSIGNMENTS: Joined via ASSIGNMENT_ID. Links to the assignment set that groups sourcing rules.
  • MSC_TRADING_PARTNER_SITES: Joined via SUPPLIER_SITE_ID. Provides details on the specific supplier site.
  • MSC_TRADING_PARTNERS: Joined via SUPPLIER_ID. Provides details on the supplier organization.

These relationships form the foundation for the sourcing data model within Oracle ASCP, ensuring referential integrity between items, their sourcing rules, and the associated trading partners.