Results for “hrfv_personal_background_info”

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

Overview

HRFV_PERSONAL_BACKGROUND_INFO is an APPS-owned business view template in the PER (Human Resources) product family, delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. The object is classified as a Flexfield View (the "FV" prefix) — a read-only, business-facing projection that Oracle generates from a business view template so that descriptive and key flexfield data can be queried through a stable, denormalized interface rather than through the underlying transactional tables directly. Its documented description is "Business view template from which the flexfield view is generated," and its ETRM status is VALID.

The view presents personal background check information for a person, combined with the business group to which that person belongs. Because it flattens the join between the organization/unit translation table and the person record, it is well suited to operational reporting, Oracle Discoverer or BI Publisher data models, and lightweight integrations that need a person's name alongside their background verification status without navigating the full PER schema.

Underlying Base Objects

The documented base objects behind this view are HR_ALL_ORGANIZATION_UNITS_TL, HR_BIS, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and PER_PEOPLE_X. The view text shown in the ETRM excerpt reflects this dependency chain:

• HR_ALL_ORGANIZATION_UNITS_TL — the translated organization units table, aliased BGRT, supplying the business group name. The view restricts this table with BGRT.LANGUAGE = USERENV('LANG') so that only the session-language row is returned.
• PER_PEOPLE_X — the person secure view, aliased PEO, providing FULL_NAME, background check status/date, business group, and person identifiers. Person-level security is applied through this view rather than the base PER_ALL_PEOPLE_F table, which is why HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY appear as supporting package dependencies.
• HR_BIS — the business intelligence/security package. Two calls are used: HR_BIS.BIS_DECODE_LOOKUP('YES_NO', …) to translate the background check status into a Yes/No value, and HR_BIS.GET_SEC_PROFILE_BG_ID to restrict the query to the business group(s) allowed by the user's security profile.

Because the definition includes WITH READ ONLY, the view cannot be used as the target of DML.

Key Columns

• BUSINESS_GROUP_NAME — the translated name of the business group (organization unit).
• PERSON_NAME — the person's full name as returned by PER_PEOPLE_X. This is the column most commonly matched when users search for person_name.
• BACKGROUND_CHECKED — a Yes/No decoding of the background check status via HR_BIS.
• BACKGROUND_CHECK_DATE — the date the background check was performed.
• BUSINESS_GROUP_ID — the identifier of the business group, used to join back to organization or security tables.
• PERSON_ID — the unique person identifier, the primary join key to PER_PEOPLE_F and related person tables.

Common Use Cases and Queries

Typical usage includes headcount compliance reporting, background screening audits, and secure exports restricted by the caller's HR security profile.

SELECT business_group_name, person_name,
       background_checked, background_check_date
FROM   apps.hrfv_personal_background_info
WHERE  person_name LIKE :search_name
ORDER  BY person_name;

SELECT person_id, person_name, background_checked
FROM   apps.hrfv_personal_background_info
WHERE  business_group_id = :p_bg_id
AND    background_checked = 'Yes';

Because the view enforces language and security-profile predicates internally, it returns only rows the current session is authorized to see and should be preferred over direct queries against PER_PEOPLE_X for reporting purposes.