Results for “per_emp_number”

49 results




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

Overview

PA_R_PROJECT_RESOURCES_TERM_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, denormalized picture of project resources — specifically employees — by joining assignment, person, organization, job, and transaction attribute data. A defining characteristic of this view is that it surfaces actual termination dates through the TERMINATION_DATE column, which is aliased from ACTUAL_TERMINATION_DATE in the underlying HR periods-of-service and periods-of-placement tables.

The view is intended to support reporting and integration scenarios where resource availability, assignment spans, and end-of-employment information must be evaluated together. Because it merges human-resources data with project resource transaction attributes, it acts as a bridge between Oracle HRMS and Oracle Projects, allowing reports to identify whether a person is still an active resource, is scheduled to end an assignment, or has already been terminated.

Underlying Base Objects

The view is defined over thirteen documented base objects, all exposed to APPS through synonyms, plus one package:

Key Columns

Common Use Cases and Queries

Typical usage includes resource roster reporting, termination-driven availability checks, and integration feeds into scheduling or costing processes. A common requirement is to list active employees along with their termination status.

SELECT person_id,
       name,
       assignment_end_date,
       termination_date
FROM   apps.pa_r_project_resources_term_v
WHERE  termination_date IS NULL
   OR  termination_date > SYSDATE;

To identify resources terminated within a given period:

SELECT person_id,
       name,
       per_emp_number,
       termination_date
FROM   apps.pa_r_project_resources_term_v
WHERE  termination_date BETWEEN :from_date AND :to_date;

Because the view already resolves person, job, and organization names, it reduces the need to rejoin HRMS tables in downstream reports, making it convenient for both operational dashboards and data-extraction interfaces.