Search Results ni_multiple_assignments




Overview
Explore in AI Chat

Overview

HRFV_GB_PERSONAL_DETAILS is a business view template maintained in the APPS schema under the PER (Human Resources) product family. It is a flexfield-derived view, meaning it is generated from a business view template rather than serving as a base transactional object. Its defining characteristic is the restriction of output to the United Kingdom legislative context: the WHERE clause filters records on BGR.LEGISLATION_CODE = 'GB', so only personal details belonging to GB business groups are exposed.

The view presents a flattened, denormalized projection of person-level descriptive and legislative attributes. Because it joins the business group definition to the person record, it provides report authors and integrators with a single object that combines organizational context (business group name) with individual demographics, statutory identifiers, and GB-specific flexfield attributes. It is read-only (defined WITH READ ONLY) and is typically consumed by Oracle Discoverer workbooks, BI Publisher reports, and inbound/outbound interfaces that must present GB statutory personal data without navigating the underlying PER schema directly. The _DF:PER:PER_PEOPLE:PEO column signals that the view is a flexfield view generated for the PER_PEOPLE entity, used by the flexfield view machinery to identify the source entity.

Underlying Base Objects

ETRM 12.2.2 documents the following referenced base objects: HR_BIS (package), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PER_BUSINESS_GROUPS (view), and PER_PEOPLE_X (view).

The principal FROM-clause sources are PER_BUSINESS_GROUPS (aliased BGR) and PER_PEOPLE_X (aliased PEO), joined on PEO.BUSINESS_GROUP_ID = BGR.ORGANIZATION_ID. PER_PEOPLE_X is the effective-dated, date-tracked view of the PER_PEOPLE table, which is why the view exposes current person attributes without the caller managing date-tracked joins.

  • HR_BIS — supplies BIS_DECODE_LOOKUP (used to decode ETH_TYPE and YES_NO lookups) and GET_SEC_PROFILE_BG_ID (used for business group security filtering).
  • HR_SECURITY — underpins the security profile restriction applied through the NVL predicate on business group ID.
  • HR_GENERAL and HR_PERSON_NAME — provide supporting person-name and general HR utilities referenced by the generated view template.

Key Columns

The view exposes twenty-one columns. The most significant include:

Common Use Cases and Queries

Typical scenarios include GB statutory reporting, pension administration extracts, and person-name validation. A query retrieving middle names for GB employees:

SELECT PERSON_ID,
       PERSON_NAME,
       FIRST_NAME,
       MIDDLE_NAMES,
       LAST_NAME,
       NI_NUMBER
FROM   APPS.HRFV_GB_PERSONAL_DETAILS
WHERE  UPPER(MIDDLE_NAMES) LIKE UPPER(:p_search || '%');

A pension extract joining additional pensionable service:

SELECT BUSINESS_GROUP_NAME,
       PERSON_NAME,
       NI_NUMBER,
       ADDL_PENSIONABLE_YEARS,
       ADDL_PENSIONABLE_MONTHS,
       ADDL_PENSIONABLE_DAYS,
       PENSIONER
FROM   APPS.HRFV_GB_PERSONAL_DETAILS
WHERE  BUSINESS_GROUP_ID = :p_bg_id;

Because the view is read-only and secured through HR_BIS.GET_SEC_PROFILE_BG_ID, queries execute within the caller's business group security profile, ensuring that only authorized GB business groups are returned. Report developers should join on PERSON_ID to PER_ALL_PEOPLE_F or PER_PERSON_NAMES_F when effective-date history is required, since the view reflects the current effective record.