Search Results msc_sr_receipt_org




Overview
Explore in AI Chat

Overview

The MSC_SR_RECEIPT_ORG table is a core data object within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as a junction table that defines the specific receiving organizations assigned to a sourcing rule or bill of distribution. In the context of Oracle's global sourcing and planning logic, a sourcing rule dictates how an item is supplied, and this table explicitly stores the list of organizations (internal or external) that are valid destinations for receipt of that supply. Its primary role is to maintain the many-to-many relationship between a parent sourcing rule header and the potential receiving entities, enabling complex, multi-tiered supply chain models.

Key Information Stored

The table's structure is designed to link sourcing rules to trading partner entities. The primary key, SR_RECEIPT_ID, uniquely identifies each receipt organization assignment. The most critical foreign key column is SOURCING_RULE_ID, which links the record back to its parent definition in the MSC_SOURCING_RULES table. The destination organization is identified through the RECEIPT_PARTNER_ID and RECEIPT_PARTNER_SITE_ID columns, which reference the MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES tables, respectively. These columns allow the system to model receipts at both the organization and specific site level, providing granular control over supply chain flows.

Common Use Cases and Queries

A primary use case is analyzing the supply network for a specific item or organization. Planners and analysts often query this table to validate or report on sourcing rule assignments. A common diagnostic query identifies all receiving organizations for a given sourcing rule name. For example:

  • SELECT sr.sourcing_rule_name, tp.partner_name AS receipt_org FROM msc_sr_receipt_org sro JOIN msc_sourcing_rules sr ON sro.sourcing_rule_id = sr.sourcing_rule_id JOIN msc_trading_partners tp ON sro.receipt_partner_id = tp.partner_id WHERE sr.sourcing_rule_name = '&RULE_NAME';

Another critical scenario involves data cleanup or migration scripts, where ensuring referential integrity between sourcing rules and their assigned receipt organizations is paramount. This table is also central to any custom reporting on the configured supply network hierarchy.

Related Objects

MSC_SR_RECEIPT_ORG is centrally connected to several key planning tables, as documented by its foreign key constraints:

  • MSC_SOURCING_RULES: The parent table. Joined via MSC_SR_RECEIPT_ORG.SOURCING_RULE_ID = MSC_SOURCING_RULES.SOURCING_RULE_ID.
  • MSC_TRADING_PARTNERS: Provides the receiving organization's details. Joined via MSC_SR_RECEIPT_ORG.RECEIPT_PARTNER_ID = MSC_TRADING_PARTNERS.PARTNER_ID.
  • MSC_TRADING_PARTNER_SITES: Provides the specific receiving site details. Joined via MSC_SR_RECEIPT_ORG.RECEIPT_PARTNER_SITE_ID = MSC_TRADING_PARTNER_SITES.PARTNER_SITE_ID.
  • MSC_SR_SOURCE_ORG: This table references MSC_SR_RECEIPT_ORG, likely to define source-to-receipt pairings within a rule. Joined via MSC_SR_SOURCE_ORG.SR_RECEIPT_ID = MSC_SR_RECEIPT_ORG.SR_RECEIPT_ID.