Search Results second_passport_exists_code




Overview
Explore in AI Chat

Overview

APPS.HRFV_PERSONAL_DETAILS is a Business Intelligence System (BIS) view owned by the APPS schema and registered in the application design data under the form identifier PER.HRFV_PERSONAL_DETAILS. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status and presents generic personal information about the people recorded in an enterprise — employees and applicants alike. Its purpose is to provide a denormalized, reporting-friendly projection of person data that combines identifying attributes, demographic details, contact information, and employment status indicators into a single relational surface suitable for operational reporting, data extraction, and integration with external HR and payroll systems. Because it is a view rather than a base table, all values are derived at query time from the underlying Oracle Human Resources (PER) schema, which means any row returned reflects current application state and is automatically filtered by HR security rules embedded in the view logic. The view exposes 240-character descriptive fields in addition to coded equivalents, allowing report authors to work in either the user-facing value or the underlying lookup code. A notable attribute for users who search on secondary identification documents is the column SECOND_PASSPORT, together with its companion indicator SECOND_PASSPORT_EXISTS_CODE, which allow the presence and value of a second passport to be reported without querying the base person tables directly.

Underlying Base Objects

The documented dependencies show that HRFV_PERSONAL_DETAILS is not built from a single table. It is defined over a set of synonyms, packaged APIs, and one view. Person-level data originates from PER_PEOPLE_F, the effective-dated core person entity, which supplies name, date of birth, hire date, and identification attributes. Person types and their translated names come from PER_PERSON_TYPES and PER_PERSON_TYPES_TL, while business group and organization context is resolved through HR_ALL_ORGANIZATION_UNITS_TL. Contact and location data are drawn from PER_PHONES. Period-of-service and hire-related information is sourced from PER_PERIODS_OF_SERVICE. Translated lists of values, such as nationality and territory descriptions, come from FND_TERRITORIES_TL and FND_LANGUAGES. The view relies on server-side packages for its behavioral logic: HR_SECURITY enforces the security profile applied to the querying session, HR_GENERAL and HR_PERSON_NAME format and concatenate person names, HR_BIS supplies business-intelligence helper logic, and HRI_BPL_PERSON_TYPE supports person-type resolution. This composition explains why the view enforces row-level security and why results may differ between two users running identical SQL.

Key Columns

The view returns a broad column set. Identity and naming columns include BUSINESS_GROUP_NAME, PERSON_NAME, EMPLOYEE_NUMBER, APPLICANT_NUMBER, FIRST_NAME, LAST_NAME, MIDDLE_NAMES, PREFERRED_NAME, PREFIX, SUFFIX, TITLE, and PREVIOUS_LAST_NAME. Demographics include DATE_OF_BIRTH, AGE, GENDER, GENDER_CODE, MARITAL_STATUS, MARITAL_STATUS_CODE, NATIONALITY, NATIONALITY_CODE, NATIONAL_IDENTIFIER, REGISTERED_DISABLED, and the corresponding flag codes, along with TOWN_OF_BIRTH, REGION_OF_BIRTH, and COUNTRY_OF_BIRTH. Contact and assignment data cover EMAIL_ADDRESS, OFFICE_NUMBER, INTERNAL_LOCATION, MAILSTOP, MAIL_DESTINATION, WORK_SCHEDULE, and FTE_CAPACITY. Employment and status columns include HIRE_DATE, ORIGINAL_DATE_OF_HIRE, PROJECTED_START_DATE, DATE_OF_DEATH, DATE_EMPLOYEE_DATA_VERIFIED, HOLD_APPLICATION_UNTIL, ON_MILITARY_SERVICE, FAST_PATH_EMPLOYEE, STUDENT_STATUS, HONORS, CURRENT_EMPLOYEE_FLAG_CODE, and CURRENT_APPLICANT_FLAG_CODE. The second passport attributes are exposed as SECOND_PASSPORT (the recorded document value) and SECOND_PASSPORT_EXISTS_CODE (the coded indicator), allowing both the value and a simple existence test to be reported.

Common Use Cases and Queries

Typical uses include headcount and demographic reporting, HR data extracts for third-party systems, applicant tracking summaries, and compliance or audit reporting on identity documents. Because HR_SECURITY is applied, queries return only the people the session is authorized to see; report owners should therefore validate results under the expected security profile. A straightforward query listing people who have a second passport recorded is:

  • SELECT person_name, employee_number, applicant_number, second_passport, second_passport_exists_code FROM apps.hrfv_personal_details WHERE second_passport IS NOT NULL;
  • SELECT person_name, nationality, date_of_birth, hire_date FROM apps.hrfv_personal_details WHERE current_employee_flag_code = 'Y' ORDER BY person_name;
  • SELECT business_group_name, gender, COUNT(*) FROM apps.hrfv_personal_details GROUP BY business_group_name, gender;

For 12.1.1 and 12.2.2 the object definition and column list are consistent, so the same SQL can be used across both releases. Direct SQL against the view is supported for read-only reporting, but changes to person data must always be performed through the Oracle HRMS forms or the supported PER APIs, never against the view.