Search Results resource_source_name




Overview
Explore in AI Chat

Overview

PA_PROJ_PARTIES_PROG_EDIT_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, programmatically consumable listing of project parties — the people and organizations assigned to roles on a project — restricted to those assignments that are currently active as of the system date. Its name indicates its purpose: it supports programmatic editing and validation of project party records through a form or API, exposing only rows where the party assignment is in effect today.

The view is a UNION ALL of two branches, each filtered by RESOURCE_TYPE_ID. The first branch selects employee parties (RESOURCE_TYPE_ID = 101) and joins to PA_EMPLOYEES to resolve the party's name. The second branch selects organization parties (RESOURCE_TYPE_ID = 112) and joins to HZ_PARTIES to resolve the name. Both branches filter on the active date range, using TRUNC(SYSDATE) against START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, SYSDATE). This design makes the view a reliable source for current-focus project team reporting and for integration logic that must not consider expired or future-dated role assignments.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following objects:

  • PA_PROJECT_PARTIES (synonym) — the primary transactional table storing project party assignments, including project, resource, role, source, and active date information.
  • PA_PROJECT_ROLE_TYPES (view) — supplies the project role type code and meaning for each assignment.
  • PA_EMPLOYEES (view) and HZ_PARTIES (synonym) — resolve the display name for employee and organization parties respectively.
  • HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (packages) — supporting HR infrastructure referenced for name formatting and security.
  • PA_ROLE_JOB_BG_UTILS (package) — a Projects utility package associated with role and job background logic.

The view text confirms the joins: PPP.PROJECT_ROLE_ID = PPRT.PROJECT_ROLE_ID, PPP.RESOURCE_SOURCE_ID = PE.PERSON_ID for the 101 branch, and PPP.RESOURCE_SOURCE_ID = HZP.PARTY_ID for the 112 branch. The employee branch additionally enforces PE.ACTIVE = '*'.

Key Columns

  • PROJECT_PARTY_ID — unique identifier of the project party assignment.
  • PROJECT_ID — the project to which the party is assigned.
  • RESOURCE_ID — the resource identifier for the assignment.
  • RESOURCE_TYPE_ID — literal 101 for employees, 112 for organizations, generated in each UNION branch.
  • RESOURCE_SOURCE_ID — the source key linking to PERSON_ID (employees) or PARTY_ID (organizations). This is the column users most often search alongside the term "resource_source_name."
  • RESOURCE_SOURCE_NAME — the resolved display name, taken from PE.FULL_NAME or HZP.PARTY_NAME.
  • PROJECT_ROLE_ID / PROJECT_ROLE_TYPE / PROJECT_ROLE_NAME — the role identifier, its type code, and its meaning from PA_PROJECT_ROLE_TYPES.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective window for the assignment.

Common Use Cases and Queries

The view is typically used for LOV queries, concurrent reporting, and integration extracts that require only current project team members with resolved names.

  • Listing all active parties for a project:
SELECT project_party_id, resource_source_name, project_role_name
FROM   pa_proj_parties_prog_edit_v
WHERE  project_id = :p_project_id;
  • Filtering by resource source name for integration matching:
SELECT project_id, resource_source_id, resource_source_name
FROM   pa_proj_parties_prog_edit_v
WHERE  UPPER(resource_source_name) LIKE UPPER('%' || :p_name || '%');

Because the view pre-filters on SYSDATE, no additional active-date predicate is required; however, callers needing historical or future-dated assignments must query PA_PROJECT_PARTIES directly.