Search Results pa_project_contacts_pk

Overview

PA_PROJECT_CONTACTS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the customer representatives associated with a given project. Each row links a project to a customer and to an individual contact within that customer organization, qualified by a contact type code. The table therefore acts as the authoritative record of who on the customer side is involved in a project, whether as a billing contact, a technical liaison, a sponsor, or another defined role. The object is owned by the PA schema and is classified as VALID in the ETRM dictionary.

The documented physical schema in 12.2.2 contains eleven columns, with a composite primary key, PA_PROJECT_CONTACTS_PK, comprising PROJECT_ID, CUSTOMER_ID, CONTACT_ID, and PROJECT_CONTACT_TYPE_CODE. From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link table rather than a hub or satellite: it resolves a many-to-many association between projects, customers, and customer contacts, with the contact type acting as an additional discriminator in the business key.

Key Information Stored

The most significant columns fall into three groups.

• PROJECT_ID — Identifies the project the contact is associated with. It is part of the primary key and is a foreign key to PA_PROJECTS_ALL.
• CUSTOMER_ID — Identifies the customer organization. Part of the primary key and a foreign key to both RA_CUSTOMERS and HZ_CUST_ACCOUNTS in the Trading Community Architecture model.
• CONTACT_ID — Identifies the specific individual within the customer organization. Part of the primary key and a foreign key to HZ_CUST_ACCOUNT_ROLES.
• PROJECT_CONTACT_TYPE_CODE — Classifies the contact's role or function on the project and completes the composite business key.
• BILL_SHIP_CUSTOMER_ID — Associates the contact with the bill-to or ship-to customer used for project billing and delivery purposes.
• RECORD_VERSION_NUMBER — Supports optimistic locking and concurrent update control.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN record who created and last modified the row, as is standard across EBS transactional tables.

The surrogate technical identity is the composite primary key PA_PROJECT_CONTACTS_PK. The unique index PA_PROJECT_CONTACTS_U1 mirrors the same four columns, confirming that PROJECT_ID, CUSTOMER_ID, CONTACT_ID, and PROJECT_CONTACT_TYPE_CODE together form the documented business-key candidate. There is no single-column surrogate key such as a sequence-generated ID.

Common Use Cases and Queries

The table is typically queried to surface customer contacts for a project, to drive contact-driven notifications, and to build project-customer relationship reports. A common pattern joins the table to PA_PROJECTS_ALL for project attributes and to the HZ customer model for names and contact details:

• Listing all contacts for a project: select PROJECT_ID, CUSTOMER_ID, CONTACT_ID, PROJECT_CONTACT_TYPE_CODE from PA_PROJECT_CONTACTS where PROJECT_ID = :project_id.
• Filtering contacts by role: add a predicate on PROJECT_CONTACT_TYPE_CODE to isolate billing or technical contacts.
• Resolving contact names: join CONTACT_ID to HZ_CUST_ACCOUNT_ROLES and onward to the party or person tables.
• Reconciling to project customers: join CUSTOMER_ID to HZ_CUST_ACCOUNTS to validate that contacts belong to the correct customer account.
• Audit and change tracking: order by LAST_UPDATE_DATE to identify recently modified contact assignments.

Related Objects

The most significant related objects follow directly from the documented foreign keys.

• PA_PROJECTS_ALL — The parent project table, joined on PROJECT_ID.
• RA_CUSTOMERS — Legacy receivables customer table, joined on CUSTOMER_ID.
• HZ_CUST_ACCOUNTS — TCA customer account table, joined on CUSTOMER_ID.
• HZ_CUST_ACCOUNT_ROLES — TCA contact role table, joined on CONTACT_ID.
• PA_PROJECT_CONTACTS_PK / PA_PROJECT_CONTACTS_U1 — The primary key and unique index that enforce the four-column business key.