Search Results current_employee_flag_code




Overview
Explore in AI Chat

Overview

APPS.HRFV_PERSONAL_DETAILS is a business view template within the Oracle E-Business Suite PER – Human Resources product. As documented in ETRM, its description is "Business view template from which the flexfield view is generated." In practice, this object exposes descriptive, largely non-flexfield person attributes in a flattened, report-friendly layout, and is typically referenced by Oracle HRMS's "Flexfield View Generator" (and by extension the Business Intelligence/HRMS reporting layer) as the starting point for building security-aware personal-detail views.

The view presents a single row per person record from PER_PEOPLE_F, enriched with a business group name, decoded lookup values (via HR_BIS.BIS_DECODE_LOOKUP), and additional person-type/service context. Because the queries are resolved through the APPS schema with synonym indirection (e.g., PER_PEOPLE_F, HR_ALL_ORGANIZATION_UNITS_TL, FND_LANGUAGES), the view remains compatible with the multi-org and multi-language model of release 12.1.1 and 12.2.2.

The user's search term student_status does not appear as an explicit column in the documented view text. It is most likely expected as a decoded person-type or person-type-classification attribute surfaced through PER_PERSON_TYPES/PER_PERSON_TYPES_TL joins, or via the flexfield view generated over this template.

Underlying Base Objects

ETRM documents the following referenced base objects for the 12.2.2 view:

  • PER_PEOPLE_F (VIEW) — the primary person source; supplies most projected attributes.
  • PER_PERIODS_OF_SERVICE — assignment/service context.
  • PER_PERSON_TYPES / PER_PERSON_TYPES_TL — person type codes and translated names; the probable source for a "student" classification.
  • PER_PHONES — telephone details.
  • HR_ALL_ORGANIZATION_UNITS_TL — business group (organization) name.
  • FND_LANGUAGES and FND_TERRITORIES_TL — language and territory labels.
  • HR_BIS, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (PACKAGES) — decoding, naming, and row-level security logic.
  • HRI_BPL_PERSON_TYPE (PACKAGE) — person-type business logic used by HRMS business intelligence.

Key Columns

The view text lists a broad set of person descriptors. Notable columns include:

Common Use Cases and Queries

Typical uses include HR person-detail reports, BI Publisher extracts, and downstream integrations needing decoded name, contact, and status data. A representative query:

  • SELECT person_name, employee_number, gender, nationality FROM apps.hrfv_personal_details WHERE employee_number = :emp_num;
  • To reconcile a "student status" requirement, join to person-type translations: SELECT p.person_name, p.employee_number, pt.user_person_type AS person_type FROM apps.hrfv_personal_details p, apps.per_person_types_tl pt WHERE p.person_id = pt.person_type_id AND pt.language = USERENV('LANG');

Note that student_status is not a native column; it is derived through person-type or lookup decoding rather than exposed directly by the template.