Results for “supervisor_id”

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

Overview

PA_NOMINATE_RESOURCE_LOV_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered with the Projects (PA) product family. In EBS 12.1.1 and 12.2.2 it carries a VALID status and serves the Project Super User responsibility by providing a filtered list of values (LOV) of employees and contingent workers who are eligible to be nominated as project resources. The view consolidates person, assignment, organization, and lookup data into a single denormalized row per candidate, exposing both the resource identity and the assignment context required for nomination.

The view does not store data of its own; it is a query-only construct. Its principal role in EBS reporting and integration is to present a validated, security-consistent candidate pool. Because the underlying logic restricts candidates to people with a primary, active assignment in an expenditure-enabled organization, it prevents nomination of inactive, terminated, or non-project-eligible personnel. The same view text is shipped in both the 12.1.1 and 12.2.2 releases, and it remains stable across the upgrade path.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists the referenced base objects as: HR_ALL_ORGANIZATION_UNITS (synonym), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PA_ALL_ORGANIZATIONS (synonym), PA_LOOKUPS (view), PER_ASSIGNMENTS_F (view), PER_ASSIGNMENT_STATUS_TYPES (synonym), PER_JOB_EXTRA_INFO (synonym), and PER_PEOPLE_F (view).

The view joins PER_PEOPLE_F to PER_ASSIGNMENTS_F on PERSON_ID to obtain the current person record and the primary assignment. PER_ASSIGNMENT_STATUS_TYPES supplies the assignment status, which is restricted to ACTIVE_ASSIGN and ACTIVE_CWK. PER_JOB_EXTRA_INFO is joined on JOB_ID with an INFORMATION_TYPE of 'JOB CATEGORY' and JEI_INFORMATION6 set to 'Y', ensuring the job is flagged for resource nomination. PA_LOOKUPS (LOOKUP_TYPE = 'PA_PERSON_TYPE') resolves the person type of EMP or CWK and drives the CASE on CURRENT_EMPLOYEE_FLAG. HR_ALL_ORGANIZATION_UNITS provides the organization name. PA_ALL_ORGANIZATIONS filters the assignment organization to those with PA_ORG_USE_TYPE = 'EXPENDITURES' and no inactive date. The HR_SECURITY package supplies the security predicate that constrains visible rows to the Project Super User's authorization.

Key Columns

• RESOURCE_SOURCE_ID — The PERSON_ID of the candidate, used as the LOV return value and the nomination source key.
• RESOURCE_NAME — FULL_NAME from PER_PEOPLE_F, the display name shown in the LOV.
• RESOURCE_NUMBER — EMPLOYEE_NUMBER of the candidate.
• RESOURCE_ORGANIZATION_ID — ORGANIZATION_ID of the candidate's primary assignment.
• RESOURCE_ORGANIZATION_NAME — Name of the organization from HR_ALL_ORGANIZATION_UNITS.
• ASSIGNMENT_START_DATE / ASSIGNMENT_END_DATE — Effective start and end dates of the assignment; SYSDATE must fall on or before the end date.
• SUPERVISOR_ID — The supervisor attached to the assignment.
• PERSON_TYPE — Lookup meaning from PA_LOOKUPS, typically Employee or Contingent Worker.

Common Use Cases and Queries

Typical scenarios include populating custom nomination LOVs, validating candidate eligibility before insert into a nomination staging table, and feeding resource-planning reports that need an active, expenditure-enabled workforce list.

A straightforward query retrieves all eligible candidates:

SELECT resource_source_id,
       resource_name,
       resource_number,
       resource_organization_name,
       person_type
  FROM apps.pa_nominate_resource_lov_v
 ORDER BY resource_name;

To restrict candidates to a single organization, filter on the organization name or ID:

SELECT resource_source_id, resource_name
  FROM apps.pa_nominate_resource_lov_v
 WHERE resource_organization_id = :p_org_id;

To exclude contingent workers and show only employees:

SELECT resource_source_id, resource_name
  FROM apps.pa_nominate_resource_lov_v
 WHERE person_type = 'Employee';

Because the view is secured by HR_SECURITY and PA_ALL_ORGANIZATIONS, results are automatically limited to records the querying user is authorized to see, which makes it suitable for direct use in forms, OAF LOVs, and ad hoc reports without additional filtering logic.