Search Results msc_trading_partners




Overview
Explore in AI Chat

Overview

The MSC_TRADING_PARTNERS table is a core master data table within Oracle E-Business Suite's Advanced Supply Chain Planning (ASCP) module. It serves as the central repository for defining and managing all external and internal entities that participate in the planning process. Its primary role is to model trading relationships by storing information about customers, suppliers, and internal planned organizations, enabling the planning engine to accurately simulate supply and demand flows across the entire supply chain network. This table is fundamental for creating a valid planning model, as it establishes the parties between which materials, capacity, and demand are transferred.

Key Information Stored

The table's primary key is the PARTNER_ID, which uniquely identifies each trading partner record. Critical columns define the type and relationships of these partners. Key attributes include classification columns to designate an organization as a customer, supplier, or internal entity. The table also contains essential foreign key relationships that link a trading partner to its detailed definition in other schemas, such as HR_ORGANIZATION_UNITS. Furthermore, it includes modeled relationship columns like MODELED_CUSTOMER_ID and MODELED_SUPPLIER_ID, which are self-referencing foreign keys to other records within the same MSC_TRADING_PARTNERS table. These allow for the representation of complex supply chain hierarchies, such as designating a specific supplier organization as the primary source for a given customer organization within the planning context.

Common Use Cases and Queries

A primary use case is validating the setup of the planning model by querying which organizations have been successfully instantiated as trading partners. A common diagnostic query identifies all modeled customer-supplier relationships. For example:

  • Identifying all trading partners of a specific type: SELECT partner_id, sr_tp_id FROM msc_trading_partners WHERE sr_instance_id = :instance AND partner_type = 'CUSTOMER';
  • Investigating sourcing relationships within the model: SELECT mtp1.partner_name AS Supplier, mtp2.partner_name AS Customer FROM msc_trading_partners mtp1, msc_trading_partners mtp2 WHERE mtp1.modeled_supplier_id = mtp2.partner_id;

This table is also central to reporting on planned demand allocations, supplier capacity, and inter-organization transfers, as it provides the descriptive context for IDs stored in transactional planning tables like MSC_DEMANDS and MSC_SUPPLIES.

Related Objects

As indicated by its extensive foreign key relationships, MSC_TRADING_PARTNERS is a hub table with numerous dependencies. Key related objects include MSC_TRADING_PARTNER_SITES, which stores site-level details for each partner, and transactional tables like MSC_DEMANDS (CUSTOMER_ID), MSC_ITEM_SOURCING (SUPPLIER_ID), and MSC_ALLOCATIONS (PARTNER_ID). The table also has a recursive relationship with itself via the MODELED_CUSTOMER_ID and MODELED_SUPPLIER_ID columns. Other important related tables are MSC_PARTNER_CONTACTS, MSC_LOCATION_ASSOCIATIONS, and the sourcing rule tables (MSC_SR_SOURCE_ORG, MSC_SR_RECEIPT_ORG), which all rely on the PARTNER_ID to define planning assignments and constraints.