Results for “pa_person_type”

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

Overview

APPS.PA_AGR_ADM_DET_V is an Oracle E-Business Suite view that returns the set of persons eligible to be treated as agreement administrators within Oracle Projects. It presents a distinct list of people, combining standard employees and contingent workers, and exposes three columns: FULL_NAME, PERSON_ID, and EMPLOYEE_NUMBER. The view is owned by the APPS schema and is defined over a union of two queries, each restricted by HR date-tracked effectivity so that only current, active records are returned.

The view is driven by the lookup type PA_PERSON_TYPE. In the first branch the lookup code EMP qualifies the record, which is why a search for "pa_person_type" surfaces this object. The view therefore acts as a filtered, presentation-ready source for Projects administrator assignment, LOV population, and reporting, rather than exposing the underlying HR tables directly.

Underlying Base Objects

The documented base objects referenced by this view are PER_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE, PER_PERIODS_OF_PLACEMENT, PA_LOOKUPS, plus the HR_GENERAL, HR_PERSON_NAME and HR_SECURITY packages. Both union branches join PER_PEOPLE_F to PER_ALL_ASSIGNMENTS_F on PERSON_ID with PRIMARY_FLAG = 'Y', ensuring only the primary assignment is considered. The first branch requires ASSIGNMENT_TYPE = 'E' (employee) and joins to PER_PERIODS_OF_SERVICE; the second requires ASSIGNMENT_TYPE = 'C' (contingent worker) and joins PER_PERIODS_OF_PLACEMENT. PA_LOOKUPS supplies the PA_PERSON_TYPE validation, and the HR packages provide name formatting and security context.

Key Columns

• FULL_NAME — formatted person name sourced from PER_PEOPLE_F, presented for display in lists of values and reports.
• PERSON_ID — the unique person identifier from PER_PEOPLE_F, used as the foreign key when assigning administrators to agreements or projects.
• EMPLOYEE_NUMBER — the employee number; in the employee branch it is derived from EMPLOYEE_NUMBER, while the contingent branch relies on the NPW number being present.

Rows are filtered so that the person's effective end date is on or after the current date, the assignment is effective, and the period of service or placement has not been terminated (actual termination date null or in the future). The result set is distinct, so each person appears once even where multiple effective rows satisfy the join.

Common Use Cases and Queries

Typical uses include populating administrator LOVs in Projects setup, validating proposed administrators, and building operational reports of eligible personnel. A simple query to list eligible administrators is:

SELECT person_id, full_name, employee_number
FROM   apps.pa_agr_adm_det_v
ORDER BY full_name;

A query to locate a specific person by employee number:

SELECT person_id, full_name
FROM   apps.pa_agr_adm_det_v
WHERE  employee_number = :employee_number;

Because the view already enforces current-employee, primary-assignment, and PA_PERSON_TYPE='EMP' logic, consumers should not re-apply those filters. Note that the view carries no organization or operating-unit column, so additional filtering by business group or responsibility must be handled externally. The view is read-only and intended for query access from the APPS schema.