Results for “res_exists”

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

Overview

PA_R_PROJECT_RESOURCES_V is an Oracle Applications (APPS) view in the Projects (PA) module, defined over Human Resources and Projects base objects. It presents a consolidated roster of project resources — primarily employees — by joining assignment, person, organization, job, and resource transaction attribute data. In Oracle EBS 12.1.1 and 12.2.2 the view serves as a reporting and integration surface for identifying who is available as, or assigned to, a project resource, along with organizational defaults, calendar, and person-type classification.

The object is VALID in the APPS schema. Its name and column set indicate it is used to resolve personnel into PA resource records, supplying the effective dating and status logic that the Projects resource model requires without forcing callers to reconstruct the multi-table join themselves.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all consumed through APPS synonyms: PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_PERSON_TYPES, PER_PERSON_TYPE_USAGES_F, PER_ASSIGNMENT_STATUS_TYPES, PER_JOBS, PER_JOB_EXTRA_INFO, PER_PERIODS_OF_SERVICE, PER_PERIODS_OF_PLACEMENT, HR_ORGANIZATION_INFORMATION, PA_ALL_ORGANIZATIONS, PA_RESOURCE_TXN_ATTRIBUTES, and the PA_EXPENDITURES_UTILS package.

The view text joins PER_ALL_ASSIGNMENTS_F to PER_ALL_PEOPLE_F on PERSON_ID, restricting assignments to system statuses 'ACTIVE_ASSIGN' and 'ACTIVE_CWK' via PER_ASSIGNMENT_STATUS_TYPES. Person type usage is resolved through PER_PERSON_TYPE_USAGES_F and PER_PERSON_TYPES. Organization context is supplied by HR_ORGANIZATION_INFORMATION, twice — once for the default operating unit (ORG_INFORMATION1) and once for the calendar. Termination dates come from a UNION ALL of PER_PERIODS_OF_SERVICE and PER_PERIODS_OF_PLACEMENT. Job description is enriched by PER_JOBS and PER_JOB_EXTRA_INFO. The PA_EXPENDITURES_UTILS.GETORGTLNAME function returns the business group name.

Key Columns

• PERSON_ID / NAME — the resource identifier and the truncated (60-character) full name.
• ORGANIZATION_ID, DEFAULT_OU, CALENDAR_ID — assignment organization and derived operating unit and calendar identifiers.
• RES_EXISTS — a DECODE returning 'EXISTS' or 'NOT EXISTS' based on whether the person appears in PA_RESOURCE_TXN_ATTRIBUTES; this is the column most closely tied to the "res_exists" search.
• RESOURCE_TYPE — hard-coded as 'EMPLOYEE' in this view.
• ASSIGNMENT_START_DATE / ASSIGNMENT_END_DATE / START_DATE / TERMINATION_DATE — effective dating for the assignment and the person's period of service or placement.
• P_TYPE / USER_TYPE — system and user person type classification.
• PER_EMP_NUMBER, PER_EMAIL, PER_WORK_PHONE, JOB_NAME, SUPERVISOR_ID, ORG_NAME — descriptive person and job attributes.

Common Use Cases and Queries

Typical uses include validating whether a person exists as a PA resource, extracting an employee resource list for a project organization, and feeding downstream resource or utilization reporting.

• Find persons who are recognised PA resources:

SELECT person_id, name, res_exists, job_name
FROM   apps.pa_r_project_resources_v
WHERE  res_exists = 'EXISTS';

• List active employee resources by organization:

SELECT organization_id, person_id, name, default_ou, calendar_id
FROM   apps.pa_r_project_resources_v
WHERE  resource_type = 'EMPLOYEE'
ORDER  BY organization_id, name;

• Identify persons not yet registered as resources:

SELECT person_id, name, per_email
FROM   apps.pa_r_project_resources_v
WHERE  res_exists = 'NOT EXISTS';

Because the view embeds effective-dating and status logic, ad-hoc queries should not add redundant date predicates against the underlying _F tables; filtering on RES_EXISTS and ORGANIZATION_ID is the intended usage pattern.