Search Results sr_source_id




Overview
Explore in AI Chat

Overview

The MSC_SR_SOURCE_ORG table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the master table for defining source organizations within the Sourcing Rules and Bills of Distribution framework. This table is essential for modeling the supply network, as it stores the specific origin points from which items are sourced to fulfill demand at designated receipt organizations. Its integrity is critical for the planning engine to accurately calculate material flows, allocate supplies, and generate feasible procurement and manufacturing plans based on the configured sourcing hierarchies and assignments.

Key Information Stored

The table's primary purpose is to link a sourcing rule assignment to a specific source entity. Its key column is the SR_SOURCE_ID, which serves as the unique primary key identifier for each source record. Each record is fundamentally associated with a parent receipt organization via the SR_RECEIPT_ID foreign key. The table then defines the source entity itself through the SOURCE_PARTNER_ID and SOURCE_PARTNER_SITE_ID columns, which are foreign keys to trading partner definitions. These columns typically hold identifiers for internal organizations (for inter-org transfers) or external supplier sites (for purchases). Additional columns, not detailed in the provided metadata but common in this structure, would include effective dates, allocation percentages, rank or priority for the source within a rule, and a reference to the parent sourcing rule or bill of distribution header.

Common Use Cases and Queries

This table is central to queries analyzing sourcing configurations. A common reporting use case is to list all active sourcing rules with their assigned sources and destinations. A typical diagnostic query would join MSC_SR_SOURCE_ORG to MSC_SR_RECEIPT_ORG and the trading partner tables to translate IDs into meaningful names. For example, to validate a specific sourcing setup, one might execute a query to see all sources for a given item and receipt organization. Data fixes often target this table when correcting misconfigured sourcing assignments, such as updating source partner IDs or allocation percentages. The planning engine itself heavily queries this table during the plan launch to build its internal supply chain model.

Related Objects

The MSC_SR_SOURCE_ORG table maintains defined foreign key relationships with several other critical MSC tables, forming the backbone of the sourcing rules data model.

  • MSC_SR_RECEIPT_ORG: Joined via MSC_SR_SOURCE_ORG.SR_RECEIPT_ID. This is the primary parent-child relationship, linking each source record to its corresponding destination or receipt organization record within a sourcing assignment.
  • MSC_TRADING_PARTNERS: Joined via MSC_SR_SOURCE_ORG.SOURCE_PARTNER_ID. This relationship provides the master definition of the source entity, whether it is an internal organization or an external supplier.
  • MSC_TRADING_PARTNER_SITES: Joined via MSC_SR_SOURCE_ORG.SOURCE_PARTNER_SITE_ID. This refines the source definition to a specific site or location of the trading partner, which is crucial for detailed planning and procurement.

The table is also a likely child of a higher-level sourcing rule header table (such as MSC_SOURCING_RULES), though that specific relationship is not listed in the provided metadata.