Results for “per_first_name”

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

Overview

The PA_R_PROJECT_RESOURCES_IND_V view is an Oracle Projects (PA) reporting object owned by the APPS schema. It presents a denormalized, filter-ready projection of the resource pool that Oracle Projects can assign to project work — specifically employees and contingent workers. The view consolidates person, assignment, person type, job, and period-of-service information into a single row per qualifying assignment, exposing both human-readable attributes (name, employee number, email, phone, job title) and a fixed literal RESOURCE_TYPE = 'EMPLOYEE'.

Its role is to support resource validation, lookups, and integration logic where a downstream process needs a ready list of currently active project resources. Because the view applies the status, person-type, primary-assignment, and termination filters internally, callers do not have to replicate that business logic. In both EBS 12.1.1 and 12.2.2 it remains a VALID object; no structural divergence is documented between the two releases for this view.

Underlying Base Objects

The view is defined over the following documented base objects:

• PER_ALL_ASSIGNMENTS_F (ASGN) — the driving assignment record; supplies person, organization, location, supervisor, job, and assignment effective dates.
• PER_ALL_PEOPLE_F (PER) — the person record providing name, number, email, phone, and business group.
• PER_PERSON_TYPES (PTYPE) and PER_PERSON_TYPE_USAGES_F (PTU) — resolve the system and user person types; joined so that the assignment start date falls within the person-type usage range.
• PER_ASSIGNMENT_STATUS_TYPES (STATUS) — restricts to active assignment statuses.
• PER_JOBS (JOB) — supplies the job name and job group.
• PER_PERIODS_OF_SERVICE and PER_PERIODS_OF_PLACEMENT — unioned into an inline view (PO) to derive the termination date.
• PA_EXPENDITURES_UTILS — a package function GETORGTLNAME used to translate the business group into an organization name.

All PER_ objects are consumed via APPS synonyms, keeping the definition stable across releases.

Key Columns

• PERSON_ID — unique person identifier; the natural join key back to PER.
• NAME — full name truncated to 60 characters.
• ORGANIZATION_ID / LOCATION_ID — the assignment organization and location.
• ASSIGNMENT_START_DATE / ASSIGNMENT_END_DATE — assignment effective range; START_DATE is set to SYSDATE and TERMINATION_DATE to the actual termination date.
• P_TYPE / USER_TYPE — the system person type (EMP, CWK) and the business-facing USER_PERSON_TYPE. The USER_TYPE column is the field most commonly surfaced for searches such as "user_type".
• PER_EMP_NUMBER — employee number, or NPW number when the person is not a current employee.
• PER_EMAIL / PER_WORK_PHONE — contact attributes.
• JOB_NAME / JOB_GROUP_ID / JOB_ID — job details.
• SUPERVISOR_ID — assignment supervisor.
• ORG_NAME / RESOURCE_TYPE — business group name and the literal resource classification.

Common Use Cases and Queries

Typical uses include building resource-selection lists, validating that a person is an eligible project resource, and filtering by person type. For example, retrieving active contingent workers:

SELECT person_id, name, user_type, org_name
FROM apps.pa_r_project_resources_ind_v
WHERE user_type = 'Contingent Worker';

To search by name or view job and contact detail:

SELECT person_id, name, per_emp_number, job_name, per_email
FROM apps.pa_r_project_resources_ind_v
WHERE UPPER(name) LIKE 'SMITH%';

Because the view already restricts to active, primary assignments with valid person-type usage and non-terminated periods of service, queries remain concise and consistent with Oracle Projects' own resource eligibility rules.