Search Results hrfv_us_addresses




Overview
Explore in AI Chat

Overview

HRFV_US_ADDRESSES is a business view template owned by the APPS schema in Oracle E-Business Suite, delivered under the PER (Human Resources) product family. As its description states, it is a "business view template from which the flexfield view is generated" — meaning it serves as the definition layer for a generated descriptive flexfield (DFF) view rather than as an end-user-facing object in its own right. The view presents United States–style person addresses held in Oracle HRMS, joining address, person, person type, and business group information into a single reporting structure, and it is statused VALID in both 12.1.1 and 12.2.2.

Because it is a template, the underlying DFF reference _DF:PER:PER_ADDRESSES:ADDR appears in the projection, tying the generated view to the PER_ADDRESSES descriptive flexfield. Its principal role is to support Oracle Business Intelligence and HRMS reporting and integration scenarios in which US address data must be retrieved with decoded, user-meaningful values.

Underlying Base Objects

The documented referenced base objects reflect the view's join path. Data originates from the PER_ADDRESSES synonym (the address records), filtered to STYLE = 'US'. Person identity is supplied by the PER_PEOPLE_X view, while person types come from the PER_PERSON_TYPES_TL synonym. Organization/business group naming is resolved through HR_ALL_ORGANIZATION_UNITS_TL. Decoding of lookup values is performed by the HR_BIS package (via BIS_DECODE_LOOKUP), and security is applied through the HR_BIS security profile function and the related HR_SECURITY and HR_GENERAL packages. FND_TERRITORIES_TL, HRI_BPL_PERSON_TYPE, and HR_PERSON_NAME are also documented as dependencies supporting territory, person type, and name resolution.

Key Columns

Common Use Cases and Queries

Typical use is projecting current US addresses with decoded state names for reporting, extracts, or integrations. Note that the view already filters on the effective date and security profile:

SELECT person_name,
       employee_number,
       state_name,
       city,
       zip_code
  FROM apps.hrfv_us_addresses
 WHERE state_name = 'California';

Because STATE_NAME is decoded in the view, filtering on it avoids clients hard-coding the US_STATE lookup translation. A second scenario lists primary addresses per business group using the decoded primary flag:

SELECT business_group_name,
       person_name,
       address_line1,
       city,
       state_code,
       state_name
  FROM apps.hrfv_us_addresses
 WHERE primary_flag = 'Yes'
 ORDER BY business_group_name, person_name;

Finally, person type and applicant/employee status can be combined for HR extracts:

SELECT person_type,
       COUNT(*)
  FROM apps.hrfv_us_addresses
 WHERE current_employee_flag = 'Yes'
 GROUP BY person_type;

As a template-generated DFF view, HRFV_US_ADDRESSES should be treated as read-only (WITH READ ONLY) and referenced through the APPS synonym in custom SQL.