Results for “pa_project_parties”

50+ results




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

Overview

PA_PROJECT_PARTIES is the Oracle Projects (PA) table that records the resources involved in a specified project. Each row represents a single party—an employee, an organization, a customer contact, or another defined resource—associated with a project through a particular project role. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the master registry of project team membership, providing the foundation on which project assignments, assignment history, subteam membership, and project-customer relationships are built. The table is owned by the PA schema and contains 18 documented columns.

From a Data Vault modeling perspective, the heuristic classification applied to this table is hub. It anchors the durable identity of a project party through the surrogate key PROJECT_PARTY_ID, with descriptive and relationship context distributed to satellites and link tables. This classification is a modeling suggestion derived from the foreign key topology rather than a physical characteristic of the table itself.

Key Information Stored

The surrogate primary key is PROJECT_PARTY_ID, enforced by the unique index PA_PROJECT_PARTIES_PK. A second unique index, PA_PROJECT_PARTIES_U1, duplicates this column as a business-key candidate; PA_PROJECT_PARTIES_U2 provides a broader composite business key spanning OBJECT_ID, OBJECT_TYPE, RESOURCE_TYPE_ID, RESOURCE_SOURCE_ID, PROJECT_ROLE_ID, and START_DATE_ACTIVE. The most significant columns include:

Common Use Cases and Queries

Typical reporting scenarios include listing all parties on a project, identifying a resource's project roles, and auditing active versus expired team memberships. A representative query joining the party to its project and resource is:

  • SELECT pp.project_party_id, pp.project_id, pp.resource_id, pp.project_role_id, pp.start_date_active, pp.end_date_active FROM pa_project_parties pp WHERE pp.project_id = :project_id AND SYSDATE BETWEEN pp.start_date_active AND NVL(pp.end_date_active, SYSDATE + 1);
  • Joining to PA_PROJECTS_ALL to resolve project names and to PA_RESOURCES for resource names.
  • Joining to PA_PROJECT_ASSIGNMENTS via PROJECT_PARTY_ID to retrieve assignment details for a party.
  • Reporting on project subteam membership through PA_PROJECT_SUBTEAM_PARTIES.OBJECT_ID.

Related Objects

PA_PROJECT_PARTIES sits at the center of a dense relationship cluster. The following are the most significant related objects and their join columns:

  • PA_PROJECTS_ALL — referenced via PA_PROJECT_PARTIES.PROJECT_ID.
  • PA_RESOURCES — referenced via PA_PROJECT_PARTIES.RESOURCE_ID.
  • PA_RESOURCE_TYPES — referenced via PA_PROJECT_PARTIES.RESOURCE_TYPE_ID.
  • PA_PROJECT_ROLE_TYPES — referenced via PA_PROJECT_PARTIES.PROJECT_ROLE_ID.
  • FND_GRANTS — referenced via PA_PROJECT_PARTIES.GRANT_ID.
  • PA_PROJECT_ASSIGNMENTS — references PA_PROJECT_PARTIES.PROJECT_PARTY_ID.
  • PA_ASSIGNMENTS_HISTORY — references PA_PROJECT_PARTIES.PROJECT_PARTY_ID.
  • PA_PROJECT_SUBTEAM_PARTIES — references PA_PROJECT_PARTIES.OBJECT_ID.
  • PA_PROJECT_CUSTOMERS — references PA_PROJECT_PARTIES.PROJECT_PARTY_ID.
  • PA_PROJECT_PARTIES_AR and PA_PROJECT_ASGMTS_AR — archival counterparts referencing the same key.