Search Results phn_last_update_date

Overview

APPS.HRFV_PHONES is a Business Intelligence System (BIS) view in Oracle E-Business Suite, owned by the APPS schema and registered under FND Design Data PER.HRFV_PHONES. It presents telephone details for persons recorded in the enterprise, combining phone records with person, person-type, and business-group attributes to support cross-functional reporting. Because it is a BIS view rather than a base table, it is intended for read-only consumption by reports, extracts, and integration layers that require phone numbers enriched with person identity and employment context.

The view is documented as VALID and is delivered identically in 12.1.1 and 12.2.2. Its naming prefix HRFV (Human Resources Forms View) indicates it is a seed view commonly used by Oracle HRMS forms and by custom BI Publisher or Discoverer solutions. It does not store data; all content is derived at runtime from the underlying PER_PHONES and PER_PEOPLE_X objects.

Underlying Base Objects

HRFV_PHONES is defined over the following documented objects: HRI_BPL_PERSON_TYPE (package), HR_ALL_ORGANIZATION_UNITS_TL (synonym), HR_BIS (package), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PER_PEOPLE_X (view), PER_PERSON_TYPES (synonym), PER_PERSON_TYPES_TL (synonym), and PER_PHONES (synonym).

PER_PHONES supplies the phone number, phone type, and date range columns, along with the PHN_LAST_UPDATE_DATE WHO column. PER_PEOPLE_X supplies the effective-dated person record and contributes PEO_LAST_UPDATE_DATE. HR_PERSON_NAME and HR_GENERAL resolve the formatted PERSON_NAME, while HR_SECURITY enforces row-level access for the querying session. Person-type classification is resolved through HRI_BPL_PERSON_TYPE and PER_PERSON_TYPES_TL, and business group labels are resolved through HR_ALL_ORGANIZATION_UNITS_TL. HR_BIS provides additional business intelligence helper logic. Note that the dependency list references synonyms layered over the underlying PER base tables, so the view inherits any business-group and security filtering defined in those objects. Ordinary direct table privileges on PER_PHONES are not sufficient for querying HRFV_PHONES; the runtime security packages must execute with the appropriate context.

Key Columns

The view exposes identity, classification, and effective-dating columns relevant to phone reporting:

• PERSON_ID / PERSON_TYPE_ID / BUSINESS_GROUP_ID — primary keys used for joins to person and organization data.
• PERSON_NAME / BUSINESS_GROUP_NAME / EMPLOYEE_NUMBER — descriptive attributes used to label results.
• PHONE_TYPE / PHONE_TYPE_CODE / PHONE_NUMBER — the phone attribute itself; PHONE_TYPE is the display value, PHONE_TYPE_CODE the reference code.
• PERSON_TYPE / SYSTEM_PERSON_TYPE_CODE / EMPLOYEE_PERSON_TYPE / APPLICANT_PERSON_TYPE / USER_CONCAT_PERSON_TYPE — person-type classifications. The USER_CONCAT_PERSON_TYPE column, the specific subject of the user's search, concatenates eligible person-type values into a single delimited string for reporting convenience.
• CURRENT_EMPLOYEE_FLAG / CURRENT_APPLICANT_FLAG / CURRENT_*_FLAG_CODE — indicate whether the person currently holds employee or applicant status.
• DATE_FROM / DATE_TO / DATE_TO_NN — effective dates. DATE_TO_NN defaults null DATE_TO to 31-DEC-4712 to support date-from/date-to joins.
• _DF — standard descriptive flexfield discriminator.
• PHN_LAST_UPDATE_DATE / PEO_LAST_UPDATE_DATE — audit columns from PER_PHONES and PER_PEOPLE_X.

Common Use Cases and Queries

Typical scenarios include producing enterprise phone directories, feeding downstream HR extracts, and reporting headcount alongside contact details. Because the view respects HR security, results are restricted to records visible to the session's security profile.

Example — all phone numbers for current employees in a business group:

• SELECT PERSON_NAME, EMPLOYEE_NUMBER, PHONE_TYPE, PHONE_NUMBER, USER_CONCAT_PERSON_TYPE
• FROM APPS.HRFV_PHONES
• WHERE CURRENT_EMPLOYEE_FLAG_CODE = 'Y'
• AND BUSINESS_GROUP_ID = :p_business_group_id
• AND TRUNC(SYSDATE) BETWEEN DATE_FROM AND DATE_TO_NN;

Example — phone numbers by concatenated person type:

• SELECT USER_CONCAT_PERSON_TYPE, COUNT(DISTINCT PERSON_ID) PERSON_CT
• FROM APPS.HRFV_PHONES
• WHERE TRUNC(SYSDATE) BETWEEN DATE_FROM AND DATE_TO_NN
• GROUP BY USER_CONCAT_PERSON_TYPE;

Always apply an effective-date predicate using DATE_FROM and DATE_TO_NN, and join on PERSON_ID where links to other HR views are required.