Results for “post_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HRFV_GB_ADDRESSES is an Oracle E-Business Suite business view owned by the APPS schema and delivered under the PER (Human Resources) product family. In the EBS 12.1.1 and 12.2.2 releases it serves as a business view template from which the descriptive flexfield (DFF) view for GB (United Kingdom) addresses is generated. The object is stored as a standard relational view (Status: VALID) and is queried read-only, as indicated by the WITH READ ONLY clause in its view text.

The view presents person-level address information for employees and applicants whose address style is 'GB', combined with business group, person, and person type descriptive attributes. It is not a transactional entity but a reporting and integration surface, intended to expose address data in a decoded, user-friendly form suitable for extracts, concurrent programs, and downstream interfaces. Because it filters on ADDR.STYLE = 'GB', only address records conforming to the United Kingdom style definition are returned.

Underlying Base Objects

The view is defined over four primary sources joined in its query text: PER_ADDRESSES (SYNONYM) supplies the address attributes; HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) supplies BUSINESS_GROUP_NAME; PER_PERSON_TYPES_TL (SYNONYM) supplies USER_PERSON_TYPE; and PER_PEOPLE_X (VIEW) supplies person-level attributes such as PERSON_NAME via the FULL_NAME column.

The documented referenced base objects extend beyond the FROM clause to include packages invoked during evaluation: HR_BIS (PACKAGE), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), and HRI_BPL_PERSON_TYPE (PACKAGE). These support lookup decoding (BIS_DECODE_LOOKUP), name formatting, and business group security. FND_TERRITORIES_TL (SYNONYM) supports territory-related decoding. The join conditions enforce effective-dating (TRUNC(SYSDATE) BETWEEN ADDR.DATE_FROM AND NVL(ADDR.DATE_TO, TRUNC(SYSDATE))) and language filtering via USERENV('LANG') on the translated organization and person type tables. The security predicate ADDR.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, ADDR.BUSINESS_GROUP_ID) restricts results according to the running user's security profile.

Key Columns

• BUSINESS_GROUP_NAME — Decoded name of the business group from HR_ALL_ORGANIZATION_UNITS_TL.
• PERSON_NAME — Full formatted person name from PER_PEOPLE_X.
• ADDRESS_STYLE / ADDRESS_TYPE / PRIMARY_FLAG — Style code ('GB'), decoded address type, and decoded Yes/No primary indicator.
• ADDR_DATE_FROM / ADDR_DATE_TO — Effective dates governing the returned address record.
• ADDRESS_LINE1, ADDRESS_LINE2, ADDRESS_LINE3, ADDR_COMMENTS — Free-text address lines and comments.
• COUNTRY, POST_CODE, COUNTY, TOWN — Geographic attributes; COUNTY is decoded via the GB_COUNTY lookup.
• TELEPHONE_NUMBER_1, TELEPHONE_NUMBER_2, TELEPHONE_NUMBER_3 — The three telephone slots on the address record, matching the user's search term.
• EMPLOYEE_NUMBER, CURRENT_EMPLOYEE_FLAG, CURRENT_APPLICANT_FLAG, PERSON_TYPE — Person identity, status, and decoded person type.
• BUSINESS_GROUP_ID, PERSON_ID, PERSON_TYPE_ID — Surrogate identifiers for joins and DFF context.

Common Use Cases and Queries

Typical uses include HR address extracts, verification of telephone contact data, and integration feeds requiring GB-formatted person addresses. The presence of the DFF token ('_DF:PER:PER_ADDRESSES:ADDR') means the view is designed to carry descriptive flexfield attribute context alongside the standard columns.

A basic query to retrieve telephone information for current employees is shown below. Note that TELEPHONE_NUMBER_2 is a direct column projection and requires no decoding.

• SELECT person_name, employee_number, telephone_number_1, telephone_number_2, telephone_number_3 FROM apps.hrfv_gb_addresses WHERE current_employee_flag = 'Yes';
• SELECT person_name, town, post_code, telephone_number_2 FROM apps.hrfv_gb_addresses WHERE post_code IS NOT NULL ORDER BY person_name;

Because the view applies date and security predicates internally, callers do not need to add effective-date logic; results are automatically limited to the active address per the system date and the user's business group security profile.