Search Results expense_check_address_flag

Overview

APPS.HR_EMPLOYEES is a Purchasing (PO) module view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes a consolidated, date-effective roster of employees and contingent workers as defined by human resources data. The view is owned by the APPS schema and carries a VALID status in the ETRM repository. Its canonical purpose is to present person records that have a valid employee number (or an equivalent non-payrolled worker number) and at least one current primary assignment, filtered by assignment type. The view is a denormalized read-only projection: it does not itself store data, but resolves person, business group, and assignment records at query time so that purchasing-related components—buyer lookups, requisition and PO entry, approval routing, and reporting—can select from a single stable object rather than joining the PER tables directly.

Underlying Base Objects

The documented base objects for HR_EMPLOYEES include the views PER_PEOPLE_F, PER_BUSINESS_GROUPS_PERF, PER_ASSIGNMENTS_F, and the synonym PER_ASSIGNMENT_STATUS_TYPES, together with the packages FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY.

• PER_PEOPLE_F — the date-tracked person source (alias P), supplying person identifiers, names, employee/NPW numbers, email, and descriptive attributes.
• PER_BUSINESS_GROUPS_PERF — the business group source (alias PBG), joined on BUSINESS_GROUP_ID to supply the business group name.
• PER_ASSIGNMENTS_F and PER_ASSIGNMENT_STATUS_TYPES — the assignment and status sources used by the EXISTS subquery to constrain the result to persons with a current primary assignment of a supported system status.
• FND_PROFILE — read via FND_PROFILE.VALUE to determine the HR_TREAT_CWK_AS_EMP profile option, which controls whether contingent worker assignments (type 'C') are included alongside employee assignments (type 'E').
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — supporting packages referenced by the view definition for security and name resolution behavior.

The view does not add persistence; every predicate is evaluated against the current effective-dated rows of these underlying views.

Key Columns

• EMPLOYEE_ID / PERSON_ID — the person identifier returned from P.PERSON_ID; the column is exposed as EMPLOYEE_ID in the documented column list.
• EMPLOYEE_NUM — derived as NVL(P.EMPLOYEE_NUMBER, P.NPW_NUMBER), allowing non-payrolled workers to appear with an identifier.
• FULL_NAME, FIRST_NAME, MIDDLE_NAME, LAST_NAME — person name components; the documented column list also includes PREFIX.
• EMAIL_ADDRESS — work email used for notifications and approval routing.
• PBG.NAME — the business group name accompanying each row.
• ATTRIBUTE1 through ATTRIBUTE5 and ATTRIBUTE_CATEGORY — descriptive flexfield values carried through from the person record.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY.
• EXPENSE_CHECK_ADDRESS_FLAG — exposed per the documented column list, corresponding to the expense check send-to-address indicator.

Common Use Cases and Queries

Typical uses include validating an employee against Purchasing lookups, listing active personnel for a business group, and driving buyer or requester selection lists. Note that the view already restricts rows to persons with a current primary assignment and a recognized assignment status, so additional date filtering is often unnecessary.

A basic listing:

SELECT employee_id, employee_num, full_name, email_address
FROM   apps.hr_employees;

Restricting to a business group and searching by name:

SELECT employee_id, employee_num, full_name, name
FROM   apps.hr_employees
WHERE  name = :business_group_name
AND    UPPER(full_name) LIKE UPPER(:search_text || '%');

Because HR_TREAT_CWK_AS_EMP is read inside the view definition, contingent workers appear only when that profile option is set to Y at the site, application, or responsibility level. The view text also fixes the primary-flag requirement and the accepted statuses (ACTIVE_ASSIGN, ACTIVE_CWK, SUSP_ASSIGN, SUSP_CWK_ASG), and it enforces row-level HR security through the referenced HR_SECURITY package. When troubleshooting missing or unexpected employees, the profile option value and the assignment status of the underlying assignment are the first items to verify.