Search Results project_end_date

Overview

PA_PROJECT_PARTIES_V is a predefined Oracle EBS view owned by the APPS schema and defined over the Project Parties entity in the Oracle Projects (PA) module. It consolidates data from the PA_PROJECT_PARTIES table, project role definitions, HR person and assignment records, project assignments, and FND_USER into a single denormalized result set describing every party associated with a project. In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as the principal reporting and integration interface for project team membership, role assignments, and party contact information.

The view text is a UNION ALL query. The first branch restricts to employees by filtering PPP.RESOURCE_TYPE_ID = 101 and joining PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_JOBS, and HR_ALL_ORGANIZATION_UNITS to resolve the person's current primary assignment, job, organization, work phone, and email. The remaining branches address non-employee party resource types (for example, organizations or contacts sourced from HZ_PARTIES and HZ_RELATIONSHIPS). Because the view applies date-effectivity predicates such as TRUNC(SYSDATE) BETWEEN TRUNC(PE.EFFECTIVE_START_DATE) AND TRUNC(PE.EFFECTIVE_END_DATE), it always returns current, valid party records.

Underlying Base Objects

The documented base objects referenced by the view include:

• PA_PROJECT_PARTIES — the driving table holding project party records, role identifiers, and active date ranges.
• PA_PROJECTS_ALL — supplies project-level attributes such as START_DATE and COMPLETION_DATE via OBJECT_ID.
• PA_PROJECT_ROLE_TYPES and PA_PROJECT_ROLE_TYPES_VL — provide role type, meaning, and role party class.
• PA_PROJECT_ASSIGNMENTS — links parties to assignment records and exposes PA.ASSIGNMENT_ID and ASSIGNMENT_NAME.
• PER_ALL_PEOPLE_F — resolves the person's full name, party ID, phone, and email.
• PER_ALL_ASSIGNMENTS_F, PER_JOBS, and HR_ALL_ORGANIZATION_UNITS — resolve the primary assignment, job name, and organization name.
• FND_USER — supplies the associated application user name and user ID.
• Packages HR_GENERAL, PA_ASGMT_WFSTD, PA_PROJECT_PARTIES_UTILS, and PA_ROLE_JOB_BG_UTILS — invoked inline for phone lookup, approval-pending status, and active-date evaluation.
• HZ_PARTIES and HZ_RELATIONSHIPS — used by the non-employee branches of the union.

Key Columns

• PROJECT_PARTY_ID, PROJECT_ID, OBJECT_ID, OBJECT_TYPE — keys linking the party to its project; OBJECT_TYPE is typically 'PA_PROJECTS'.
• RESOURCE_ID, RESOURCE_TYPE_ID, RESOURCE_SOURCE_ID — identify the party's underlying resource; RESOURCE_TYPE_ID = 101 denotes an employee.
• PARTY_NAME — the person's full name from PER_ALL_PEOPLE_F.
• PROJECT_ROLE_ID, PROJECT_ROLE_TYPE — the role assigned within the project and its descriptive meaning, or the assignment name when an assignment exists.
• ROLE_PARTY_CLASS — classification of the party for the given role.
• START_DATE_ACTIVE, END_DATE_ACTIVE, ACTIVE — party active date range and the computed ACTIVE flag returned by PA_PROJECT_PARTIES_UTILS.ACTIVE_PARTY.
• SCHEDULED_FLAG, RECORD_VERSION_NUMBER — scheduling indicator and optimistic locking version.
• GRANT_ID, ASSIGNMENT_ID — links to grant and project assignment records where applicable.
• ORGANIZATION_ID, NAME (HAOU) — the party's primary HR organization.
• Work phone, EMAIL_ADDRESS, USER_NAME, USER_ID, PARTY_ID — contact and application user details.

Common Use Cases and Queries

The view is widely used in project team reports, role-based security checks, workflow notifications, and third-party integrations that require the current roster of project parties.

List all active employee parties for a project:

• SELECT party_name, project_role_type, start_date_active, end_date_active FROM pa_project_parties_v WHERE project_id = :p_project_id AND active = 'Y';

Identify parties with pending assignment approval:

• SELECT project_id, party_name, assignment_id FROM pa_project_parties_v WHERE assignment_id IS NOT NULL AND pa_asgmt_wfstd.is_approval_pending(assignment_id) = 'Y';

Resolve a specific person's roles across projects:

• SELECT project_id, project_role_type, start_date_active FROM pa_project_parties_v WHERE resource_source_id = :p_person_id ORDER BY project_id;

Because the view enforces SYSDATE-based effectivity and primary-assignment filters, queries return only currently valid records. For historical reporting, the underlying PA_PROJECT_PARTIES table should be queried instead.