Search Results msc_trading_partner_sites

Overview

The MSC_TRADING_PARTNER_SITES table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, specifically for releases 12.1.1 and 12.2.2. It functions as the central planning engine's master table for storing site-level information associated with trading partner organizations. In the ASCP context, a trading partner can be a customer, supplier, or internal organization, and this table holds the distinct physical or logical locations (sites) for these entities. Its primary role is to provide a normalized reference for all site-specific data used in planning calculations, demand management, sourcing rules, and allocations, enabling the model to accurately represent the multi-echelon supply chain network.

Key Information Stored

The table's structure is centered on the unique identifier, PARTNER_SITE_ID, which serves as the primary key. While the provided ETRM excerpt does not list all columns, the foreign key relationships imply the existence of critical linking columns. The most significant is PARTNER_ID, which foreign keys to MSC_TRADING_PARTNERS, thereby associating each site record with its parent organization. Other essential data points typically stored include the site name, address details, and active status. The table essentially acts as the planning system's counterpart to operational tables like HR_LOCATIONS and POZ_SUPPLIER_SITES, but is populated and maintained within the MSC schema to support the specific performance and data model requirements of the planning engine.

Common Use Cases and Queries

This table is fundamental for queries and reports that analyze supply chain relationships at the site level. Common use cases include validating the setup of the planning model, troubleshooting sourcing assignments, and generating partner site master lists for data audits. A typical query would join this table to its parent to retrieve a comprehensive list of all modeled sites and their associated organizations.

• Sample Query: List All Customer Sites and Their Parent Organization
  SELECT tp.PARTNER_NAME, tps.SITE_NAME, tps.PARTNER_SITE_ID
FROM MSC_TRADING_PARTNER_SITES tps,
MSC_TRADING_PARTNERS tp
WHERE tps.PARTNER_ID = tp.PARTNER_ID
AND tp.PARTNER_TYPE = 3 -- Assuming '3' represents Customer
ORDER BY tp.PARTNER_NAME, tps.SITE_NAME;
• Data Validation: Queries are often used to ensure sites referenced in demand, sourcing, or allocation records have a valid entry in MSC_TRADING_PARTNER_SITES, which is crucial for a clean planning run.

Related Objects

As evidenced by its extensive foreign key relationships, MSC_TRADING_PARTNER_SITES is a critical hub table within the MSC schema. Key documented relationships include:

• Parent Table: MSC_TRADING_PARTNERS (via PARTNER_ID)
• Child Tables (Foreign Key References):
  • MSC_ALLOCATIONS (PARTNER_SITE_ID)
  • MSC_DEMANDS (SHIP_TO_SITE_ID, CUSTOMER_SITE_ID)
  • MSC_ITEM_SOURCING (SUPPLIER_SITE_ID)
  • MSC_ITEM_SUPPLIERS (SUPPLIER_SITE_ID)
  • MSC_LOCATION_ASSOCIATIONS (PARTNER_SITE_ID)
  • MSC_PARTNER_CONTACTS (PARTNER_SITE_ID)
  • MSC_SR_ASSIGNMENTS (SHIP_TO_SITE_ID)
  • MSC_SR_RECEIPT_ORG (RECEIPT_PARTNER_SITE_ID)
  • MSC_SR_SOURCE_ORG (SOURCE_PARTNER_SITE_ID)
• Referencing Columns in Parent Table: MSC_TRADING_PARTNERS also references this table for MODELED_CUSTOMER_SITE_ID and MODELED_SUPPLIER_SITE_ID, indicating its use in defining default sites for a partner.