Search Results hr_treat_cwk_as_emp




Overview
Explore in AI Chat

Overview

APPS.HR_SUP_BASE_V is a security-enabled Oracle E-Business Suite view that exposes a filtered, person-centric list of employees and non-payroll workers drawn from the PER_ALL_PEOPLE_F table. It is delivered as part of the Oracle HRMS (Human Resources Management System) schema and is primarily used by Oracle's Supervisor and self-service reporting components to present a selectable population of workers to end users. The view's principal design objective is to enforce row-level security while simultaneously honoring the HR_TREAT_CWK_AS_EMP profile option, which controls whether contingent workers (sometimes referred to as contractors or non-payroll workers) are treated as employees for reporting and supervisory purposes.

The view projects a small, stable set of descriptive attributes — full name, last name, first name, ordering name, person identifier, business group identifier, effective dates, and an internal security indicator. Because the view is defined in the APPS schema, it inherits the standard EBS security model and is typically referenced by Oracle Forms, OAF pages, and custom reports that need a secured name-lookup list of workers.

Underlying Base Objects

According to documented ETRM metadata, HR_SUP_BASE_V is defined over the following referenced objects:

  • PER_ALL_PEOPLE_F (synonym) — the primary base table holding person records, including employee and applicant data, with date-tracked (effective-dated) rows.
  • HR_SECURITY (package) — supplies the VIEW_ALL flag and the SHOW_RECORD function used to evaluate whether the current user may see a given person record.
  • FND_PROFILE (package) — provides FND_PROFILE.VALUE, used here to read the HR_TREAT_CWK_AS_EMP profile option at runtime.

The WHERE clause restricts rows to persons where CURRENT_EMPLOYEE_FLAG = 'Y' or, when the HR_TREAT_CWK_AS_EMP profile is set to 'Y', where CURRENT_NPW_FLAG = 'Y'. Note the operator precedence in the original text: because AND binds tighter than OR, the non-payroll-worker branch is only evaluated in conjunction with the profile check, so contingent workers appear only when the profile explicitly enables them.

Key Columns

  • FULL_NAME, LAST_NAME, FIRST_NAME, ORDER_NAME — formatted name attributes used for display and alphabetical sorting.
  • PERSON_ID — the unique identifier for the person, exposed as a character string via TO_CHAR.
  • BUSINESS_GROUP_ID — the business group to which the person belongs, also cast to character.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity range of the underlying person record.
  • INSIDE_PROFILE — a derived security flag. It returns 'TRUE' when HR_SECURITY.VIEW_ALL = 'Y'; otherwise it is the result of HR_SECURITY.SHOW_RECORD, which determines whether the current user is authorized to view that person.

Common Use Cases and Queries

The view is most frequently used to populate supervisor-based selection lists and to drive reports that must respect HR security. A typical retrieval of secured workers resembles the following:

  • SELECT person_id, full_name FROM apps.hr_sup_base_v WHERE inside_profile = 'TRUE' ORDER BY order_name;
  • SELECT person_id, last_name, first_name, effective_start_date FROM apps.hr_sup_base_v WHERE business_group_id = :p_bg_id;
  • SELECT COUNT(*) FROM apps.hr_sup_base_v; — often used to validate the population visible to the current user.

Because the view depends on HR_TREAT_CWK_AS_EMP, administrators who search for "hr_treat_cwk_as_emp" typically do so to diagnose why contingent workers do or do not appear in supervisor lookups. Setting the profile to 'Y' causes current non-payroll workers to be included; leaving it at the default 'N' excludes them. The view does not expose person_type_id, employee_number, or applicant_number directly, though these are passed to SHOW_RECORD for security evaluation.