Results for “hr_current_people_lov_v”

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

Overview

The APPS.HR_CURRENT_PEOPLE_LOV_V view is a Human Resources (PER) product database object that is used to support the Oracle E-Business Suite user interface. Specifically, it delivers the data set behind the "current people" list of values (LOV) that is presented to end users in many self-service and professional forms and pages. The view is defined over the effective-dated HR person model and restricts its output to assignments that are primary, current (as of the query date), and of type E (employee), so that only active employees are returned to the LOV.

For reporting and integration purposes, the view offers a denormalized, ready-to-consume projection of an employee's identity and organizational placement. It simultaneously joins the person record, the primary assignment, the assignment organization, the location, the position, the job, the business group, and the period of service. This makes it convenient for external interfaces and custom reports that need the current workforce roster without reconstructing the multi-table DateTrack joins manually. Any interface reliant on an LOV-style people selection — for example, approval routing, delegation, or assignment of a person to a business object — can source its candidate population from this view.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through public synonyms in the APPS schema: PER_ALL_PEOPLE_F (PPF), PER_ALL_ASSIGNMENTS_F (PAF), HR_ALL_ORGANIZATION_UNITS_TL (HO and HO2), HR_LOCATIONS_ALL_TL (HL), HR_ALL_POSITIONS_F (HP), HR_ALL_POSITIONS_F_TL (HPT), PER_JOBS_TL (PJT), and PER_PERIODS_OF_SERVICE (PPOS).

PER_ALL_PEOPLE_F is the driving person table and supplies the name, person identifier, business group, person type, employee number, e-mail address, office number, current employee flag, and its own effective dates. PER_ALL_ASSIGNMENTS_F supplies the primary assignment and links the person to the organization, location, position, and job. The _TL (translated) organization, location, position, and job tables restrict output to the session language via USERENV('LANG'), so users see localized names. HR_ALL_POSITIONS_F provides position effective dating, and PER_PERIODS_OF_SERVICE establishes that the person has an open period of service, i.e. an active employee relationship.

The joins are deliberately constructed around TRUNC(SYSDATE) so that only records current at the moment of execution are returned; outer joins ((+)) are applied to location, position, position translation, and job translation, allowing employees to appear even where those attributes are not defined.

Key Columns

• FULL_NAME – the person's formatted full name from PER_ALL_PEOPLE_F, used as the display value in the LOV.
• PERSON_ID – the unique surrogate key for the person; the value typically returned to the calling form.
• BUSINESS_GROUP_ID – the identifier of the HR business group the person belongs to.
• PERSON_TYPE_ID and CURRENT_EMPLOYEE_FLAG – person type and an indicator of whether the person is a current employee.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – the DateTrack effective range of the person record returned.
• ORGANIZATION and BUSINESS_GROUP_NAME – the translated name of the assignment organization and of the business group organization unit.
• LOCATION – the location code of the assignment location.
• POSITION and JOB_TITLE – translated position name and job name.
• EMPLOYEE_NUMBER – the assigned employee number.
• EMAIL_ADDRESS – the person's e-mail address.
• OFFICE_NUMBER – the office number attribute carried on PER_ALL_PEOPLE_F; this is the column users frequently search for when they need an employee's internal office location or extension reference.

Common Use Cases and Queries

The view is most often used to populate LOVs and pickers for selecting a current employee, and to seed ad hoc reporting on the active workforce. A typical lookup by name or office number is shown below.

• Retrieve all current employees with contact details:
  SELECT person_id, full_name, employee_number, email_address, office_number FROM apps.hr_current_people_lov_v ORDER BY full_name;
• Find a person by office number or name:
  SELECT person_id, full_name, office_number, organization, job_title FROM apps.hr_current_people_lov_v WHERE office_number = :p_office_number;
SELECT person_id, full_name FROM apps.hr_current_people_lov_v WHERE UPPER(full_name) LIKE UPPER(:p_name) || '%';
• List active employees by organization and position:
  SELECT organization, position, full_name, employee_number FROM apps.hr_current_people_lov_v WHERE organization = :p_org ORDER BY organization, position, full_name;
• Produce a current roster with location and job title:
  SELECT full_name, employee_number, job_title, location, email_address FROM apps.hr_current_people_lov_v ORDER BY location, full_name;

Because the view filters on TRUNC(SYSDATE) at execution time, its contents are inherently date-sensitive; any process that caches the results should refresh them rather than relying on a stored snapshot. Queries returning very large populations benefit from filters on BUSINESS_GROUP_ID or ORGANIZATION to reduce the row set.