Results for “msc_partner_contacts”

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

Overview

MSC_PARTNER_CONTACTS is a table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) product within Oracle E-Business Suite, and is documented as VALID in both 12.1.1 and 12.2.2. The table stores partner contact information associated with trading partners and their partner sites. In the ASCP data model, trading partners represent suppliers, customers, and other external entities participating in the supply chain, and contacts are the individual people associated with those partners through whom planning, sourcing, and collaboration communications are directed.

Under the heuristic Data Vault classification mined from the foreign key structure, MSC_PARTNER_CONTACTS is modeled as a link. This suggests it functions as an associative entity that connects a trading partner (and optionally a partner site) to an individual contact record, rather than acting as a standalone hub of business keys or as a descriptive satellite. Modeling it as a link reflects its role in resolving many-to-many relationships between partners, sites, and contacts within the planning repository.

Key Information Stored

The table contains 19 documented columns. The most significant include:

• PARTNER_ID — Foreign key referencing MSC_TRADING_PARTNERS, identifying the trading partner with which the contact is associated.
• PARTNER_SITE_ID — Foreign key referencing MSC_TRADING_PARTNER_SITES, identifying the specific site of the partner when the contact is site-level rather than partner-level.
• PARTNER_TYPE — Categorizes the partner contact, contributing to the business key of the table.
• NAME — The name of the contact individual.
• DISPLAY_NAME — The formatted or preferred display name used in planning and collaboration user interfaces.
• EMAIL — Electronic mail address for the contact, used for notification and collaboration workflows.
• FAX — Facsimile number for the contact.
• ENABLED_FLAG — Indicates whether the contact record is active and available for use.
• SR_INSTANCE_ID — Identifies the source system instance from which the record originated, supporting multi-instance data collection in ASCP.
• REFRESH_NUMBER — Tracks the collection refresh cycle under which the record was populated.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the request and program that inserted or updated the record.

The unique index MSC_PARTNER_CONTACTS_U1 spans SR_INSTANCE_ID, PARTNER_TYPE, PARTNER_ID, and PARTNER_SITE_ID, establishing these as the documented business-key candidates. No separate surrogate primary key column is enumerated in the documented column list beyond the composite uniqueness expressed by this index.

Common Use Cases and Queries

Typical usage centers on retrieving contact details for a trading partner or site, filtering enabled contacts, and joining to partner master data for reporting. A representative query is:

• SELECT c.name, c.display_name, c.email, c.fax FROM msc_partner_contacts c WHERE c.partner_id = :partner_id AND c.enabled_flag = 'Y';
• Join contacts to partners: SELECT p.partner_name, c.name, c.email FROM msc_partner_contacts c, msc_trading_partners p WHERE c.partner_id = p.partner_id.
• Site-level lookup: SELECT c.name, c.email FROM msc_partner_contacts c WHERE c.partner_site_id = :site_id.
• Collection audit: SELECT sr_instance_id, refresh_number, COUNT(*) FROM msc_partner_contacts GROUP BY sr_instance_id, refresh_number.

These patterns support supplier collaboration notifications, contact roster reporting, and validation of collected ASCP partner data.

Related Objects

• MSC_TRADING_PARTNERS — Referenced via MSC_PARTNER_CONTACTS.PARTNER_ID; the parent partner master.
• MSC_TRADING_PARTNER_SITES — Referenced via MSC_PARTNER_CONTACTS.PARTNER_SITE_ID; the parent site master.
• MSC_PARTNER_CONTACTS_U1 — Composite unique index enforcing the business key.
• Related ASCP collection and planning objects that consume partner and contact data for collaboration, sourcing, and notification processing within the MSC schema.