Search Results inside_profile




Overview
Explore in AI Chat

Overview

HR_SUP_BASE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, residing within the PER (Human Resources) product family. The view is documented in ETRM for both 12.1.1 and 12.2.2 with a status of VALID and is explicitly described as being "used to support user interface." It exposes a simplified, security-filtered projection of current employee records drawn from the PER_ALL_PEOPLE_F table, primarily to drive Oracle Forms-based HR user interface components, LOVs, and inquiry screens rather than to serve as a general-purpose reporting entity.

The view is not a transactional object; it carries no inserts or updates and exists purely to consolidate display attributes (names, identifiers, and effective dates) for persons flagged as current employees. Because Oracle ETRM annotates it as UI-supporting, it should be treated as an internal implementation view. Its presence in the database does not imply a supported public API, and direct dependencies are not recommended for custom development.

Underlying Base Objects

The documented dependencies of HR_SUP_BASE_V are:

  • PER_ALL_PEOPLE_F (SYNONYM) — the DateTrack-enabled base table holding person and employee records. The view's WHERE clause restricts rows to CURRENT_EMPLOYEE_FLAG = 'Y'.
  • HR_SECURITY (PACKAGE) — invoked in the SELECT list to enforce row-level security through HR_SECURITY.VIEW_ALL and HR_SECURITY.SHOW_RECORD, which resolve to a boolean expression against PER_ALL_PEOPLE_F key attributes.
  • FND_PROFILE (PACKAGE) — the profile-option facility underpinning security and session context used during evaluation of the security predicates.

Because the view joins to HR_SECURITY logic at runtime, its result set is user-dependent: two sessions querying the same view may see different row counts based on security profile configuration.

Key Columns

  • FULL_NAME — concatenated formatted display name for the person.
  • LAST_NAME and FIRST_NAME — individual name components retained for sorting and search.
  • ORDER_NAME — the alternate name ordering used for alphabetical list presentation. This is the object most frequently correlated with the user search term "order_name" and is commonly referenced in HR person-search LOV queries.
  • PERSON_ID — the primary person identifier, exposed as a TO_CHAR string rather than a number.
  • BUSINESS_GROUP_ID — the operating unit / business group context, also cast to character.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — DateTrack effective dating of the underlying PER_ALL_PEOPLE_F row.
  • INSIDE_PROFILE — a derived security flag returning 'TRUE' when the querying user may access the record, or the result of HR_SECURITY.SHOW_RECORD otherwise.

Common Use Cases and Queries

Typical usage is limited to name-lookup helpers within HR forms. A representative query retrieves current employees visible to the session:

  • SELECT person_id, full_name, order_name FROM apps.hr_sup_base_v WHERE UPPER(order_name) LIKE 'SMITH%';
  • SELECT full_name, business_group_id FROM apps.hr_sup_base_v WHERE inside_profile = 'TRUE' ORDER BY order_name;

Because PERSON_ID and BUSINESS_GROUP_ID are returned as character strings, numeric comparisons must be cast explicitly. For production reporting, Oracle recommends querying PER_ALL_PEOPLE_F directly with the appropriate HR security policies applied, since HR_SUP_BASE_V is documented solely as a UI-support view and inherits the performance and security behaviour of its underlying packages.