Results for “gb_county”

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

Overview

APPS.HRFV_GB_ADDRESSES is a reporting view in Oracle E-Business Suite that presents person address information for employees and applicants within a business group, with formatting and decoding tailored to the United Kingdom (GB) localization. It belongs to the family of HRFV (Human Resources Flex/Format View) objects, which denormalize the underlying PER tables into human-readable, security-aware result sets intended for reporting, extracts, and integration interfaces. Rather than exposing raw code values, the view applies lookup decoding so that consumers see descriptive values for elements such as address type, primary flag, and county. This makes it particularly suited to HR reporting, statutory returns, and downstream interfaces that must not interpret internal code values.

The view is a point-in-time construct. Its driving predicate requires that TRUNC(SYSDATE) fall between each address record's effective start date and its open-ended end date, so only currently effective address rows are returned.

Underlying Base Objects

The view is defined over several documented objects. PER_ADDRESSES supplies the address rows themselves, contributing columns for address lines, postal code, region, telephone numbers, town, style, and date ranges. PER_PEOPLE_X supplies person-level attributes such as full name, employee number, and the current employee and applicant flags. PER_PERSON_TYPES_TL resolves the person type description. HR_ALL_ORGANIZATION_UNITS_TL provides the business group name. FND_TERRITORIES_TL is joined twice, once to return the address style territory and once to return the country territory, both referenced by bug fix 2649737. Helper packages are also invoked: HR_BIS provides BIS_DECODE_LOOKUP for decoding lookup types such as ADDRESS_TYPE, YES_NO, and GB_COUNTY; HRI_BPL_PERSON_TYPE derives employee, applicant, and concatenated user person types; and HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY are referenced for name formatting and security handling. Access is therefore subject to standard HR security profiles applied through PER_PEOPLE_X.

Key Columns

• business_group_name — the business group under which the person is recorded.
• person_name, employee_number — identification of the person to whom the address belongs.
• address_type, primary_flag — decoded values from the ADDRESS_TYPE and YES_NO lookups.
• county — decoded from the GB_COUNTY lookup applied to region_1; this is the column most commonly sought by users searching for "gb_county".
• region1_code — the underlying undecoded region_1 value.
• address_line1, address_line2, address_line3, town, post_code, country — the formatted address elements, with country resolved through FND_TERRITORIES_TL.
• telephone_number_1 through _3 — contact numbers held on the address record.
• addr_date_from, addr_date_to — the effective dates of the address.
• address_style, address_style_code, address_type_code, primary_flag_code — display and raw code variants of style and type attributes.
• person_type, employee_person_type, applicant_person_type, user_concat_person_type — person type classification at the effective start date.
• current_employee_flag, current_applicant_flag — decoded YES_NO indicators.
• business_group_id, person_id, person_type_id — surrogate identifiers for joins and interfaces.

Common Use Cases and Queries

The view is typically queried for UK address reporting, mailing extracts, and reconciliation of county values. A representative query returning current UK addresses for active employees is:

SELECT person_name, employee_number, address_line1, town,
       gb_county.county, post_code, country
FROM   apps.hrfv_gb_addresses
WHERE  current_employee_flag = 'Yes'
ORDER  BY person_name;

To list personnel by county, aggregate on the decoded county column:

SELECT county, COUNT(*) AS person_count
FROM   apps.hrfv_gb_addresses
GROUP  BY county
ORDER  BY person_count DESC;

Because HR security is enforced through the underlying PER_PEOPLE_X view, results are automatically restricted to the rows the querying responsibility is permitted to see. When the decoded county is required alongside its stored code, both county and region1_code should be selected.