Search Results hr_employees_current_v




Overview
Explore in AI Chat

Overview

HR_EMPLOYEES_CURRENT_V is an APPS-owned database view in Oracle E-Business Suite, classified under the Purchasing (PO) product module. Its stated purpose is to expose a "current employees" data set — that is, the set of people who at the current system date hold an active, primary assignment classified as an employee (or a contingent worker treated as an employee). Rather than requiring callers to reconstruct effective-date logic, business group filtering, and primary-assignment selection, the view delivers a pre-joined, status-filtered projection of person, assignment, and business group attributes.

The view is intended for reporting and integration consumption: purchasing-side functionality and downstream queries use it to resolve buyer, requester, and approver identities without querying the PER_* date-tracked tables directly. Because it consolidates HR person and assignment data into a single denormalized row per person, it simplifies joins against PO tables and other modules that store a PERSON_ID or EMPLOYEE_ID reference. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

Underlying Base Objects

The documented view text selects from three base objects: PER_PEOPLE_F (aliased P), PER_ASSIGNMENTS_F (aliased A), and PER_BUSINESS_GROUPS_PERF (aliased PBG). The documented metadata additionally lists FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY as referenced objects; HR_SECURITY in particular supplies the row-level security predicate that restricts results to the operating user's business group and people-access scope.

  • PER_PEOPLE_F — date-tracked person records providing name, employee/NPW number, e-mail, telephone, and descriptive attributes.
  • PER_ASSIGNMENTS_F — date-tracked assignment records providing organization, location, supervisor, set of books, and default code combination.
  • PER_BUSINESS_GROUPS_PERF — supplies the business group name (PBG_NAME).
  • FND_PROFILE — evaluated in the WHERE clause via FND_PROFILE.VALUE('HR_TREAT_CWK_AS_EMP') to decide whether contingent workers ('C') are included alongside employees ('E').

Joins are driven on PERSON_ID and BUSINESS_GROUP_ID, with the constraint that the person's business group must exist in FINANCIALS_SYSTEM_PARAMETERS.

Key Columns

The view exposes identity, organizational, and descriptive columns. Principal columns include BUSINESS_GROUP_ID, ORGANIZATION_ID, PERSON_ID (documented as EMPLOYEE_ID in the column listing), ASSIGNMENT_ID, EMPLOYEE_NUM (the NVL of EMPLOYEE_NUMBER and NPW_NUMBER), FULL_NAME, FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX, TITLE, LOCATION_ID, SUPERVISOR_ID, SET_OF_BOOKS_ID, DEFAULT_CODE_COMBINATION_ID, EMAIL_ADDRESS, WORK_TELEPHONE, EXPENSE_CHECK_ADDRESS_FLAG, and PBG_NAME. Five generic ATTRIBUTE columns plus ATTRIBUTE_CATEGORY carry descriptive flexfield content, and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) support auditing.

Common Use Cases and Queries

Typical uses include populating LOVs for buyer or requester selection, validating person references in interfaces, and generating employee rosters filtered by business group, supervisor, or organization.

  • Resolve a person by name or number for downstream lookups.
  • List all current employees reporting to a given supervisor.
  • Feed integration extracts with e-mail and telephone contact data.
  • Restrict results by organization or location for reporting hierarchies.

A representative query follows:

SELECT person_id, employee_num, full_name, organization_id, supervisor_id, email_address
FROM apps.hr_employees_current_v
WHERE business_group_id = :p_business_group_id
AND supervisor_id = :p_supervisor_id
ORDER BY full_name;