Search Results hrfv_phones




Overview
Explore in AI Chat

Overview

HRFV_PHONES is a business view template owned by the APPS schema within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the ETRM metadata, its documented purpose is to serve as the "business view template from which the flexfield view is generated." This places HRFV_PHONES within Oracle's Flexfield View (FV) framework, where a business view template defines the denormalized, business-friendly projection of person-related data that is subsequently used to generate the runtime flexfield view consumed by Oracle HRMS and related modules. The view has a status of VALID and exposes attributes from the person phone entity joined to person, person type, and business group context, enabling reporting and integration consumers to query phone information with human-readable descriptions rather than raw lookup codes.

Underlying Base Objects

The view text references several base objects. The primary transactional table is PER_PHONES (accessed via synonym), aliased PHO, filtered by PARENT_TABLE = 'PER_ALL_PEOPLE_F'. Person data is drawn from PER_PEOPLE_X (a view) aliased PEO. Person type classification comes from PER_PERSON_TYPES and PER_PERSON_TYPES_TL (both synonyms) joined through PERSON_TYPE_ID, with the translated name restricted to USERENV('LANG'). Business group names are resolved from HR_ALL_ORGANIZATION_UNITS_TL. Lookup decoding is performed by the HR_BIS package, specifically HR_BIS.BIS_DECODE_LOOKUP, for PHONE_TYPE and YES_NO values, and HR_BIS.GET_SEC_PROFILE_BG_ID is used to enforce business group security. The documented metadata also lists HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and the HRI_BPL_PERSON_TYPE package as referenced objects, reflecting the view's dependence on the standard HR security and name-formatting infrastructure. The view is created WITH READ ONLY.

Key Columns

Common Use Cases and Queries

Typical scenarios include HR self-service reporting, directory extracts, and integration feeds where phone contact data must be presented with security enforcement and decoded lookups. The view is appropriate for business-group-secured queries because the WHERE clause restricts BUSINESS_GROUP_ID to the security profile result.

A representative query lists active phones for current employees:

  • SELECT person_name, employee_number, phone_type, phone_number FROM apps.hrfv_phones WHERE current_employee_flag = 'Yes' ORDER BY person_name;

Filtering by business group uses the exposed key:

  • SELECT person_name, phone_number FROM apps.hrfv_phones WHERE business_group_id = :p_bg_id AND person_type = :p_person_type;

Because the view is READ ONLY and enforces language via USERENV('LANG'), queries automatically return session-language translations for person types and business group names. The presence of PERSON_ID supports downstream joins to other person-centric views, making HRFV_PHONES a reliable template for BUILD Flexfield View processing in Oracle HRMS.