Search Results pa_project_contacts_u1

Overview

PA.PA_PROJECT_CONTACTS is a transactional table in the Oracle E-Business Suite Projects (PA) schema that stores the customer representatives associated with a project. Each row binds a contact person to a specific project and customer, qualified by a contact type, so that Oracle Projects can identify the individuals acting on behalf of the customer during the project lifecycle. In release 12.1.1 and 12.2.2 the table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and is registered in FND Design Data as PA.PA_PROJECT_CONTACTS with a VALID status.

The table functions as the storage point for customer-side personnel data referenced by project delivery, billing and communication workflows. From a dimensional modeling perspective, the metadata's Data Vault classification heuristic suggests treating this object as a link: it resolves many-to-many business relationships among projects, customers and contacts rather than holding a single descriptive entity. This is a modeling observation, not a statement of physical design.

Key Information Stored

The documented physical schema contains eleven columns, of which the following are the most significant:

• PROJECT_ID (NUMBER 15) — identifier of the project for which the contact is entered; a mandatory business-key component and foreign key to PA_PROJECTS_ALL.
• CUSTOMER_ID (NUMBER 15) — identifier of the project customer; foreign key to RA_CUSTOMERS and HZ_CUST_ACCOUNTS.
• CONTACT_ID (NUMBER 15) — identifier of the customer representative; the FK metadata points to HZ_CUST_ACCOUNT_ROLES.
• PROJECT_CONTACT_TYPE_CODE (VARCHAR2 30) — classifies the contact (for example, the role the person plays for the project); a mandatory business-key component.
• BILL_SHIP_CUSTOMER_ID (NUMBER 15) — stores the bill-to or ship-to customer identifier associated with the contact record.
• RECORD_VERSION_NUMBER (NUMBER 15) — locking sequence number used for optimistic concurrency control during DML.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns that record audit and session context for every row.

The surrogate primary key is PA_PROJECT_CONTACTS_PK, defined on the composite of PROJECT_ID, CUSTOMER_ID, CONTACT_ID and PROJECT_CONTACT_TYPE_CODE. The unique index PA_PROJECT_CONTACTS_U1 in APPS_TS_TX_IDX carries the same four columns, confirming this combination as the business-key candidate that guarantees a contact is recorded once per project, customer and contact type.

Common Use Cases and Queries

The table is commonly queried to list customer contacts for a project, to drive project correspondence, and to enrich project billing or status reporting. A representative query follows the documented template:

• Retrieve all contacts for a given project: SELECT PROJECT_ID, CUSTOMER_ID, CONTACT_ID, PROJECT_CONTACT_TYPE_CODE FROM PA.PA_PROJECT_CONTACTS WHERE PROJECT_ID = :project_id;
• Join to PA_PROJECTS_ALL on PROJECT_ID to return the project name and number alongside the contact roles.
• Join to RA_CUSTOMERS or HZ_CUST_ACCOUNTS on CUSTOMER_ID to resolve the customer name, and to HZ_CUST_ACCOUNT_ROLES on CONTACT_ID to obtain the contact's role details.
• Filter on PROJECT_CONTACT_TYPE_CODE to isolate a specific contact function for correspondence or approval routing.
• Use LAST_UPDATE_DATE and RECORD_VERSION_NUMBER in incremental extraction and reconciliation logic.

Because the table stores the contact-to-project association directly, it is frequently used as a bridge in operational reports that must answer which customer representative is responsible for a given project.

Related Objects

• PA.PA_PROJECTS_ALL — referenced via PROJECT_ID; supplies project definition attributes.
• RA_CUSTOMERS — referenced via CUSTOMER_ID; supplies the customer entity behind the contact association.
• HZ_CUST_ACCOUNTS — referenced via CUSTOMER_ID; TCA customer account records.
• HZ_CUST_ACCOUNT_ROLES — referenced via CONTACT_ID; resolves the contact person and their role.

The metadata records no outgoing dependencies beyond these references and identifies PA_PROJECT_CONTACTS as referenced by the APPS synonym of the same name, indicating that reporting and inquiry access is typically routed through the APPS layer rather than the PA schema directly.