Search Results msc_st_trading_partners




Overview
Explore in AI Chat

Overview

The MSC_ST_TRADING_PARTNERS table is a staging table within the MSC (Advanced Supply Chain Planning) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to receive and validate data prior to loading into the base table MSC_TRADING_PARTNERS, which stores trading partner definitions used by Advanced Supply Chain Planning. Trading partners in this context represent the modeled organizations, suppliers, customers, and internal entities that participate in the planning supply chain network, together with attributes governing capacity costs, sourcing defaults, and ATP behavior.

From a Data Vault modeling perspective, the heuristic classification of this table is standalone, meaning it is not a dependent satellite or link in the mined foreign-key graph but functions as an independent hub-like entity. Each row is a candidate business entity keyed by PARTNER_ID, carrying descriptive attributes alongside operational staging metadata. This classification is a modeling suggestion derived from the FK structure, not a mandatory design constraint.

As a staging object, the table is populated by the collection program. Records flow through a validation and processing cycle, controlled by the PROCESS_FLAG, ERROR_TEXT, and MESSAGE_ID columns, which allow rejected rows to be inspected and corrected before final promotion.

Key Information Stored

The table contains 81 documented columns. The most consequential are:

Common Use Cases and Queries

The principal use case is diagnosing collection failures. Rows that failed validation remain flagged and carry an explanatory message, enabling targeted correction and re-collection.

SELECT partner_id, partner_name, partner_number,
       process_flag, error_text
  FROM msc.msc_st_trading_partners
 WHERE process_flag = 'E';

Analysts also reconcile staging content against the base table before and after a collection refresh, and profile cost and service attributes for supply chain tuning:

SELECT sr_tp_id, partner_name, demand_lateness_cost,
       supplier_cap_overutil_cost
  FROM msc.msc_st_trading_partners
 WHERE refresh_id = :refresh_id
   AND process_flag = 'S';

Reporting scenarios include partner master-data extracts, ATP-rule assignment audits, and legal-entity reconciliation using COMPANY_ID and SET_OF_BOOKS_ID.

Related Objects