Results for “oke_employees_v”

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

Overview

OKE_EMPLOYEES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE — Project Contracts product family. It presents a consolidated, currently-effective employee list drawn from Oracle HRMS person records, joined to the business group organization definition. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and its definition is unchanged across those releases.

Its principal role is to supply Project Contracts and adjacent modules with a lightweight employee lookup that exposes both HR identity attributes and the payroll/expense-related attribute EXPENSE_CHECK_SEND_TO_ADDRESS, which is the column referenced in the user's search term. Because the view filters to currently effective records and to persons holding an employee number, it is suited to operational reporting and to LOV-style integration queries rather than to full historical HR analysis.

Underlying Base Objects

The documented ETRM metadata lists the following referenced objects:

• PER_PEOPLE_F (VIEW) — the primary source of person rows, providing PERSON_ID, name elements, employee number, effective dates, vendor reference, and the expense check address.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — supplies the translated business group name, joined on ORGANIZATION_ID = BUSINESS_GROUP_ID and restricted to the session language.
• HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE) — HRMS security and name-formatting packages that govern row-level access and name derivation within the HR foundation layer.

The view text joins PER_PEOPLE_F to HR_ALL_ORGANIZATION_UNITS_TL with an equality on business group, applies TRUNC(SYSDATE) BETWEEN TRUNC(EFFECTIVE_START_DATE) AND TRUNC(EFFECTIVE_END_DATE) to isolate the current effective row per person, requires EMPLOYEE_NUMBER IS NOT NULL to exclude applicants and other non-employees, and constrains the organization name to USERENV('LANG').

Key Columns

• PERSON_ID — primary identifier of the employee; the join key to most other HR and OKE entities.
• FULL_NAME, LAST_NAME, FIRST_NAME, MIDDLE_NAMES — name components as held on the person record.
• EMPLOYEE_NUMBER — the assigned employee number; non-null by view definition.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — the date range of the effective person record evaluated against the current system date.
• EXPENSE_CHECK_SEND_TO_ADDRESS — the address to which expense reimbursement checks are directed. This is a descriptive text attribute carried from PER_PEOPLE_F and is exposed here for expense and reimbursement reporting.
• BUSINESS_GROUP_ID and BUSINESS_GROUP_NAME — the business group identifier and its translated name.
• VENDOR_ID — the supplier record associated with the person, where one exists.
• CURRENT_EMPLOYEE_FLAG — indicates whether the person is a current employee.

Common Use Cases and Queries

Typical uses include employee validation in Project Contracts integrations, populating expense reimbursement extracts, and driving address verification for check disbursement. Because the view already resolves the current effective row and the business group name, it removes the need for callers to reproduce HRMS effective-dating and language logic.

Sample query returning employees and their expense check addresses:

• SELECT person_id, employee_number, full_name, expense_check_send_to_address FROM apps.oke_employees_v WHERE business_group_id = :p_business_group_id ORDER BY full_name;

Sample query resolving a single employee by number:

• SELECT person_id, full_name, vendor_id FROM apps.oke_employees_v WHERE employee_number = :p_employee_number;

Sample query listing employees lacking a populated expense check address:

• SELECT person_id, full_name FROM apps.oke_employees_v WHERE expense_check_send_to_address IS NULL AND current_employee_flag = 'Y';

Queries should be executed with an APPS or appropriately secured responsibility, as row visibility is influenced by HR_SECURITY. Note also that the view returns only records currently inside their effective date range; terminated employees whose effective end date has passed are excluded.