Search Results resource_source_name




Overview
Explore in AI Chat

Overview

APPS.PA_PROJ_PARTIES_PROG_EV_V is a valid, internal Oracle E-Business Suite view owned by the APPS schema in the Oracle Projects (PA) module. The suffix "PROG_EV" indicates that the view was constructed to support the Progress Report workflow, which is the sole consuming component documented for this object (referenced by PA_PROGRESS_REPORT_WORKFLOW). The view exposes project party assignments in a form suitable for workflow or concurrent processing logic that must resolve the parties attached to a project together with their roles and resource identities.

The view is flagged "Oracle Internal Use Only." Oracle Corporation does not support direct customer access to data through this object except via standard Oracle Applications programs. Developers and report authors in EBS 12.1.1 and 12.2.2 may still query it for diagnostic or extension purposes, but it should be treated as a non-public, subject-to-change interface.

Underlying Base Objects

The view is defined over a mix of Synonyms, Views, and PL/SQL Packages. Documented referenced base objects include: FND_COMPILED_MENU_FUNCTIONS (SYNONYM), FND_FORM_FUNCTIONS (SYNONYM), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), HZ_PARTIES (SYNONYM), PA_EMPLOYEES (VIEW), PA_PROJECT_PARTIES (SYNONYM), PA_PROJECT_ROLE_TYPES (VIEW), and PA_ROLE_JOB_BG_UTILS (PACKAGE).

Functionally, PA_PROJECT_PARTIES supplies the core rows — one record per party assigned to a project. HZ_PARTIES supplies the trading-community party identity, HR_PERSON_NAME resolves the display name of person-based resources, HR_SECURITY enforces organization/security filtering, and PA_PROJECT_ROLE_TYPES and PA_ROLE_JOB_BG_UTILS provide role and job-based lookup logic used to derive role names and role types. The FND function references suggest the view also joins an application function context used by the progress report workflow to validate entry points.

Key Columns

  • PROJECT_PARTY_ID (NUMBER 15) — Primary identifier for the party-to-project assignment row.
  • PROJECT_ID (NUMBER 15) — The project to which the party is assigned.
  • RESOURCE_ID (NUMBER 15) — Identifier of the assigned resource (person, organization, or other party).
  • RESOURCE_TYPE_ID — Type discriminator for the resource (e.g., person vs. organization).
  • RESOURCE_SOURCE_ID (NUMBER 15) — Identifier of the source system or source table that originated the resource.
  • RESOURCE_SOURCE_NAME (VARCHAR2 360) — Descriptive name of the resource source; this is the column most commonly searched by users and is the key attribute for identifying where a resource originated.
  • PROJECT_ROLE_ID — Identifier of the project role assigned to the party.
  • PROJECT_ROLE_TYPE (VARCHAR2 20) — Classifies the role (e.g., role versus job-based).
  • PROJECT_ROLE_NAME (VARCHAR2 80) — Display name of the project role.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Date-effective range for the party assignment, supporting historical and current-state reporting.

Common Use Cases and Queries

Typical scenarios include auditing which parties are active on a project, identifying the human resource behind a role assignment, and resolving the resource source for integration or data-cleansing exercises. Date-effective filtering is essential because the view exposes start and end dates rather than pre-filtering to current rows.

Sample query listing current parties for a project:

SELECT project_party_id, project_id, resource_id, resource_source_name, project_role_name, start_date_active, end_date_active FROM apps.pa_proj_parties_prog_ev_v WHERE project_id = :p_project_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Sample query searching by resource source name:

SELECT project_id, resource_id, resource_source_name, project_role_name FROM apps.pa_proj_parties_prog_ev_v WHERE resource_source_name = :p_source_name;

Because support is limited to Oracle Applications programs, custom code should preferably reproduce the underlying PA_PROJECT_PARTIES and PA_PROJECT_ROLE_TYPES logic rather than depending on this internal view.