Search Results peo_last_update_date




Overview
Explore in AI Chat

Overview

APPS.HRFV_CONTACTS is a read-only Oracle E-Business Suite view that presents contact relationship information for persons (employees and other defined people) within a business group. The "HRFV" prefix denotes a Human Resources Foundation View, and its role is to expose a denormalized, security-filtered, and lookup-decoded projection of the PER_CONTACT_RELATIONSHIPS table joined to person and organization data. It is intended primarily for reporting, extracts, and integration scenarios where contact details must be presented with human-readable values rather than raw codes. The object is defined with WITH READ ONLY, so it cannot be used to modify underlying data; all DML must be directed to the base tables.

Underlying Base Objects

The view is defined over the following documented base objects: PER_CONTACT_RELATIONSHIPS (SYNONYM), which supplies the core contact relationship rows; PER_ALL_PEOPLE_F (SYNONYM), which supplies the contact person's current effective record; PER_PEOPLE_X (VIEW), which supplies the primary person's details; and HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM), which supplies the business group name in the user's session language. It also depends on PL/SQL APIs HR_BIS, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. The join criteria require matching person_id between PER_PEOPLE_X and PER_CONTACT_RELATIONSHIPS, matching contact_person_id between PER_ALL_PEOPLE_F and PER_CONTACT_RELATIONSHIPS, and a business group match to the organization unit. Row filtering includes the current language via userenv('LANG'), the security profile business group via hr_bis.get_sec_profile_bg_id, and an effective date restriction (TRUNC(sysdate) BETWEEN cper.effective_start_date AND cper.effective_end_date) on the contact person's record. This date predicate is why the view returns only currently effective contact person rows.

Key Columns

The view exposes descriptive identifiers and several decoded flags. Key columns include:

  • business_group_name – Name of the business group organization unit, resolved in the session language.
  • person_name – Full name of the primary person from PER_PEOPLE_X.
  • contact_person_name – Full name of the associated contact person.
  • primary_contact, contact_type, dependent_flag, third_party_pay, beneficiary, bond_holder – Lookup-decoded values produced by hr_bis.bis_decode_lookup against YES_NO and CONTACT lookup types.
  • employee_number – The primary person's employee number.
  • business_group_id, contact_person_id, person_id – Identifiers supporting joins back to base tables.
  • peo_last_update_date, cper_last_update_date, con_last_update_date – Last update timestamps for PER_PEOPLE_X, PER_ALL_PEOPLE_F, and PER_CONTACT_RELATIONSHIPS records respectively. The alias peo_last_update_date corresponds directly to peo.last_update_date, which is frequently used for incremental/delta extraction queries.

Common Use Cases and Queries

Typical scenarios include extracting contact relationships for a business group, validating decoded contact attributes for reporting, and performing incremental extracts keyed on update timestamps. A simple retrieval by person is shown below:

SELECT person_id, person_name, contact_person_name,
       contact_type, primary_contact, dependent_flag
FROM   apps.hrfv_contacts
WHERE  employee_number = :p_emp_num;

For incremental extracts, the update timestamps (including peo_last_update_date) support delta identification:

SELECT person_id, contact_person_id, con_last_update_date
FROM   apps.hrfv_contacts
WHERE  peo_last_update_date >= :p_since
   OR  con_last_update_date >= :p_since;

Because the view enforces business group security and current effective dating, consumers need not replicate these predicates. However, note that only presently effective contact person records are returned, so historical contact assignments require querying the base tables directly.