Results for “msc_trading_partners”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_TRADING_PARTNERS is a core reference table in the MSC (Advanced Supply Chain Planning) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about the organizations that participate in the supply chain plan: customers, suppliers (vendors), and planned organizations. Every planning run that models demand, sourcing, allocations, or supply relationships resolves the participating parties through this table. Because the table holds distinct, non-overlapping business entities keyed by a surrogate identifier, the heuristic Data Vault classification mined from its foreign-key structure is hub; this classification is a modeling suggestion rather than an EBS-imposed constraint.

The table is owned by the MSC schema and is documented with 77 columns in the ETRM 12.2.2 physical schema. It is validated and populated primarily through the collections and planning data-pull processes that load source organizations from order management, purchasing, and inventory.

Key Information Stored

The surrogate primary key is PARTNER_ID, enforced by the constraint MSC_TRADING_PARTNERS_PK and reinforced by the unique index MSC_TRADING_PARTNERS_U1. Two additional unique indexes expose business-key candidates: MSC_TRADING_PARTNERS_U2 on SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, COMPANY_ID, and ORGANIZATION_CODE; and MSC_TRADING_PARTNERS_U3 on PARTNER_TYPE, PARTNER_NAME, and COMPANY_ID.

The columns most frequently used in planning logic and reporting include:

• PARTNER_ID — surrogate primary key for the trading partner.
• PARTNER_NAME, PARTNER_NUMBER — human-readable identity of the customer, supplier, or organization.
• PARTNER_TYPE — discriminates the record among customer, supplier, and planned organization.
• COMPANY_ID — ties the partner to the owning operating company.
• ORGANIZATION_CODE — the source organization code used during collection.
• SR_TP_ID, SR_INSTANCE_ID — the source-system trading partner identifier and source instance, used to reconcile collected data back to the originating application.
• MODELED_CUSTOMER_ID, MODELED_CUSTOMER_SITE_ID, MODELED_SUPPLIER_ID, MODELED_SUPPLIER_SITE_ID — self-referencing pointers that resolve modeled relationships between partners and their sites.
• CALENDAR_CODE, CALENDAR_EXCEPTION_SET_ID — the working calendar applied to the partner.
• SOURCE_ORG_ID, ORGANIZATION_TYPE, MASTER_ORGANIZATION — organizational attributes governing plan behavior.
• STATUS, DISABLE_DATE — lifecycle flags used to include or exclude a partner from planning.
• DEFAULT_DEMAND_CLASS, SERVICE_LEVEL, CUSTOMER_CLASS_CODE — demand-side planning attributes.
• MAXIMUM_WEIGHT, WEIGHT_UOM, MAXIMUM_VOLUME, VOLUME_UOM — capacity-related attributes for transportation planning.

Common Use Cases and Queries

Typical uses include validating collected partners, reporting the planned customer and supplier master, and troubleshooting planning exceptions where a demand or sourcing line cannot resolve its partner.

• Resolving a customer on a demand line: join MSC_DEMANDS.CUSTOMER_ID to MSC_TRADING_PARTNERS.PARTNER_ID.
• Listing active suppliers: SELECT PARTNER_ID, PARTNER_NAME FROM MSC_TRADING_PARTNERS WHERE PARTNER_TYPE = 'SUPPLIER' AND STATUS = 'ACTIVE';
• Reconciling collected data: filter on SR_INSTANCE_ID and SR_TP_ID to trace a partner back to its source instance.
• Capacity reporting: aggregate MAXIMUM_WEIGHT and MAXIMUM_VOLUME by COMPANY_ID or ORGANIZATION_CODE.

Because the table is a planning staging structure, it is refreshed by the collections process and should not be updated directly; any enrichment must survive the next refresh cycle.

Related Objects

The table is central to MSC planning and is referenced by numerous dependent objects. The most significant relationships include:

• MSC_TRADING_PARTNER_SITES.PARTNER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — sites belonging to each partner.
• MSC_DEMANDS.CUSTOMER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — demand lines resolved to their customer.
• MSC_ITEM_SOURCING.SUPPLIER_ID and MSC_ITEM_SUPPLIERS.SUPPLIER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — sourcing rules and approved supplier lists.
• MSC_ALLOCATIONS.PARTNER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — allocation assignments per partner.
• MSC_LOCATION_ASSOCIATIONS.PARTNER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — location-level associations.
• MSC_PARTNER_CONTACTS.PARTNER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — contact records for the partner.
• MSC_SR_SOURCE_ORG.SOURCE_PARTNER_ID and MSC_SR_RECEIPT_ORG.RECEIPT_PARTNER_ID → MSC_TRADING_PARTNERS.PARTNER_ID — shipping and receiving organization assignments.
• Self-references via MODELED_CUSTOMER_ID and MODELED_SUPPLIER_ID, plus COMPANY_ID referencing PN_COMPANIES_ALL.

These relationships confirm MSC_TRADING_PARTNERS as the hub through which planning demand, sourcing, allocation, and receipt data converge.