Results for “per_people_v4”

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

Overview

PER_PEOPLE_V4 is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered under the PER (Human Resources) product family. ETRM metadata classifies it as a VALID view whose stated purpose is to "support user interface" functionality. It is not a base table and stores no data of its own; instead, it presents a consolidated, query-ready projection that joins person, assignment, job, and payroll action information into a single result set. In this role it functions as a reporting and integration surface — typically surfaced through concurrent programs, Oracle Forms/HTML-based person and assignment inquiry screens, or third-party HR integrations that must enumerate people alongside their current assignment, job title, location, and payroll action context without directly navigating the full PER_ALL_ASSIGNMENTS_F/PER_PEOPLE_F date-effective model.

Underlying Base Objects

The documented view metadata lists the following referenced base objects: HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), PAY_ASSIGNMENT_ACTIONS (SYNONYM), PAY_ELEMENT_ENTRIES_F (SYNONYM), PAY_ELEMENT_ENTRY_VALUES_F (SYNONYM), PAY_PAYROLL_ACTIONS (SYNONYM), PER_ALL_ASSIGNMENTS_F (SYNONYM), PER_JOBS_TL (SYNONYM), PER_PAY_BASES (SYNONYM), and PER_PEOPLE_F (VIEW). Functionally, the view text joins PER_PEOPLE_F to PER_ALL_ASSIGNMENTS_F on PERSON_ID, links the assignment to its job via an outer join to PER_JOBS_TL (restricted by USERENV('LANG')), and joins to payroll action data through PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS. A NOT EXISTS subquery against PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_ENTRIES_F, and PER_PAY_BASES excludes assignments whose salary is already picked up in the union. The view is built as a UNION of two DISTINCT branches — one returning NULL SALARY/PAY_BASIS for non-salary-admin records and one returning EEV.SCREEN_ENTRY_VALUE as SALARY with INITCAP(PPB.PAY_BASIS) — which is why the row set can contain multiple rows per person. The HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages provide the security and naming/display logic underlying person visibility and format.

Key Columns

• ROW_ID / PERSON_ID — the internal row identifier and the person's unique identifier from PER_PEOPLE_F.
• FULL_NAME / NI_NUMBER — display name and national identifier for the person.
• SALARY / PAY_BASIS — populated from element entry screen values in the salary branch; NULL in the non-salary branch.
• JOB_TITLE — job name resolved from PER_JOBS_TL for the session language.
• ASSIGNMENT_ACTION_ID / ASSIGNMENT_ID / ASSIGNMENT_NUMBER — the payroll assignment action and assignment identifiers linking the person to their assignment.
• LOCATION_ID / INTERNAL_ADDRESS_LINE / EXPENSE_CHECK_SEND_TO_ADDRESS — assignment location and mailing/address fields.

Common Use Cases and Queries

Typical scenarios include person/assignment inquiries that need job title, location, and payroll action context, and integrations that must enumerate people with their current assignment details. Because the view applies HR security and language-dependent job names, callers should operate as a user with appropriate PER security profile access.

• List people with their job title and assignment number:
  SELECT person_id, full_name, job_title, assignment_number FROM apps.per_people_v4;
• Retrieve salary-admin rows with pay basis:
  SELECT person_id, full_name, salary, pay_basis FROM apps.per_people_v4 WHERE salary IS NOT NULL;
• Find a person by national identifier:
  SELECT person_id, full_name, assignment_id FROM apps.per_people_v4 WHERE ni_number = :p_ni;