Results for “pa_project_parties_ar”

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

Overview

PA_PROJECT_PARTIES_AR is a Projects (PA) module table that stores the resources involved in a specified project. It functions as the archival and purge-tracking counterpart to the operational PA_PROJECT_PARTIES table, capturing project party assignments alongside purge metadata that identifies the batch responsible for archiving the record. The table holds 21 columns under the PA schema and reaches a VALID status in both Oracle EBS 12.1.1 and 12.2.2.

From a data modeling perspective, the mined metadata classifies this object as standalone, indicating it does not sit at the center of a dense foreign-key network like a classic link table. A heuristic suggestion would therefore treat PA_PROJECT_PARTIES_AR as a satellite-style object whose grain is the individual project party record, keyed to its operational parent and enriched with purge and audit attributes, rather than as a hub or a link.

Key Information Stored

The most significant columns in this table include:

• PROJECT_PARTY_ID — The surrogate primary key and the foreign key back to PA_PROJECT_PARTIES, tying each archived row to its operational source record.
• PURGE_BATCH_ID — Foreign key to PA_PURGE_BATCHES_ALL, identifying the purge batch that archived the row.
• PURGE_RELEASE — The release or version context under which the purge was executed.
• PURGE_PROJECT_ID — The project identifier associated with the purge operation.
• PROJECT_ID — Business-key candidate identifying the project to which the party is assigned.
• RESOURCE_ID / RESOURCE_TYPE_ID / RESOURCE_SOURCE_ID — The resource (person, organization, or other party) involved and its classification; RESOURCE_TYPE_ID references PA_RESOURCE_TYPES.
• PROJECT_ROLE_ID — Foreign key to PA_PROJECT_ROLE_TYPES, defining the role the resource plays on the project.
• OBJECT_ID / OBJECT_TYPE — The owning object context for the party record.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range during which the party assignment is active.
• SCHEDULED_FLAG — Indicates whether the assignment is scheduled.
• RECORD_VERSION_NUMBER — Optimistic locking support for concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• GRANT_ID — Oracle Grants integration identifier.

The primary key is PROJECT_PARTY_ID; PROJECT_ID combined with RESOURCE_ID and PROJECT_ROLE_ID is a strong business-key candidate for uniqueness within a project.

Common Use Cases and Queries

This table is most commonly queried during purge reconciliation and audit of historical project staffing. Typical patterns include:

• Locating all archived parties for a project: SELECT * FROM PA.PA_PROJECT_PARTIES_AR WHERE PROJECT_ID = :project_id;
• Joining to the purge batch to report on archived resources: SELECT a.PROJECT_ID, a.RESOURCE_ID, b.PURGE_BATCH_ID FROM PA.PA_PROJECT_PARTIES_AR a, PA.PA_PURGE_BATCHES_ALL b WHERE a.PURGE_BATCH_ID = b.PURGE_BATCH_ID;
• Resolving roles and resource types: join PROJECT_ROLE_ID to PA_PROJECT_ROLE_TYPES and RESOURCE_TYPE_ID to PA_RESOURCE_TYPES.
• Historic staffing and role analysis for projects that have been archived out of PA_PROJECT_PARTIES.

Related Objects

• PA_PROJECT_PARTIES — Operational parent; joined on PROJECT_PARTY_ID.
• PA_PURGE_BATCHES_ALL — Purge batch header; joined on PURGE_BATCH_ID.
• PA_RESOURCE_TYPES — Resource classification lookup; joined on RESOURCE_TYPE_ID.
• PA_PROJECT_ROLE_TYPES — Role definition lookup; joined on PROJECT_ROLE_ID.
• PA_PROJECTS_ALL — Project master referenced via PROJECT_ID.
• PER_ALL_PEOPLE_F / HR_ALL_ORGANIZATION_UNITS — Resolve RESOURCE_ID to the person or organization.