Search Results hrfv_contacts




Overview

HRFV_CONTACTS is a business view template owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. In both 12.1.1 and 12.2.2, this object is documented as a "business view template from which the flexfield view is generated." It exposes person-to-contact relationships — the dependents, beneficiaries, emergency contacts, and other designated contacts associated with an employee — in a denormalized, business-friendly form suitable for reporting and integration.

The view joins contact relationship records to the naming and descriptive attributes of both the primary person and the contact person, and decodes the underlying lookup-coded flags (contact type, primary contact, dependent, third-party pay, beneficiary, and bondholder) into their meaningful display values via HR_BIS.BIS_DECODE_LOOKUP. It also enforces business group security using the session's security profile and active-date logic on the contact person record. The view is defined WITH READ ONLY, confirming it is strictly a query object, not a DML target.

Because the "_DF" column is embedded in the view text, HRFV_CONTACTS functions as the flexfield view template underpinning the descriptive flexfield (DFF) enabled reporting layer for PER_CONTACT_RELATIONSHIPS. The "_DF" token typically identifies the descriptive flexfield context and segment aliasing used by the flexfield view generator.

Underlying Base Objects

The ETRM metadata documents the view as defined over the following objects:

Key Columns

  • BUSINESS_GROUP_NAME — translated name of the business group owning the person record.
  • PERSON_NAME — full name of the primary person (the employee).
  • CONTACT_PERSON_NAME — full name of the related contact person.
  • PRIMARY_CONTACT — decoded Yes/No indicator of primary contact status.
  • CONTACT_TYPE — decoded contact category (for example, dependent, emergency, beneficiary).
  • DEPENDENT_FLAG, THIRD_PARTY_PAY, BENEFICIARY, BOND_HOLDER — decoded Yes/No business flags describing the relationship.
  • EMPLOYEE_NUMBER — the primary person's employee number.
  • BUSINESS_GROUP_ID, CONTACT_PERSON_ID, PERSON_ID — key identifiers for joins and filtering.

Common Use Cases and Queries

HRFV_CONTACTS is commonly used to produce dependent and beneficiary listings, benefits and contact-relations extracts, and to power custom concurrent programs or OBIEE/XML Publisher reports that need human-readable contact data without decoding lookups manually.

SELECT business_group_name,
       employee_number,
       person_name,
       contact_person_name,
       contact_type,
       primary_contact,
       beneficiary
FROM   apps.hrfv_contacts
WHERE  contact_type = 'Dependent'
ORDER  BY person_name, contact_person_name;

To locate all contacts for a specific employee, filter by PERSON_ID. To identify only primary contacts, filter on PRIMARY_CONTACT = 'Yes'. Because the view enforces business group security through GET_SEC_PROFILE_BG_ID, results are automatically restricted to the business groups visible to the session's security profile, and effective-dated name logic ensures only current contact names are returned.