Results for “national_identifier”

50+ results




Overview
Explore in AI Chat

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

Overview

GHR_PEOPLE_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GHR - US Federal Human Resources product. The view is documented in ETRM for both 12.1.1 and 12.2.2, where it carries a VALID status. Its purpose is narrow and specific: it exposes a de-duplicated list of person records that are current (latest effective-dated row) and that are associated with at least one record in the GHR_PA_REQUESTS table. This makes GHR_PEOPLE_V a filtered convenience view rather than a general-purpose people repository.

Because the view is defined on PER_PEOPLE_F, it inherits the DateTrack (effective-dating) semantics of the Oracle HRMS person model. The DISTINCT keyword and the correlated subquery on MAX(EFFECTIVE_START_DATE) ensure that only the most recent effective record for each person is returned, eliminating historical versions. The EXISTS clause against GHR_PA_REQUESTS further restricts output to persons who have personnel action requests, which is the core business object in US Federal HR processing.

Underlying Base Objects

The documented base objects referenced by GHR_PEOPLE_V are:

  • PER_PEOPLE_F (VIEW) — the primary source, supplying person identifiers, effective-dated attributes, and the row-versioning logic.
  • GHR_PA_REQUESTS (SYNONYM) — used in the EXISTS predicate to qualify persons with personnel action requests.
  • HR_GENERAL (PACKAGE) — typically used for DateTrack and session context handling.
  • HR_PERSON_NAME (PACKAGE) — supports retrieval of formatted person names, including the FULL_NAME value.
  • HR_SECURITY (PACKAGE) — applies security profile filtering so that only persons visible to the current responsibility are returned.

The relationship to PER_PEOPLE_F is the defining characteristic of this view. PER_PEOPLE_F is itself a view in Oracle HRMS over the PER_ALL_PEOPLE_F table, and it applies security and DateTrack logic. GHR_PEOPLE_V layers an additional MAX(EFFECTIVE_START_DATE) restriction and a PA request filter on top of that foundation.

Key Columns

The view projects four columns:

  • PERSON_ID — the unique numeric identifier for the person, and the primary join key to other HRMS tables such as PER_ALL_ASSIGNMENTS_F, PER_ADDRESSES_F, and contact tables.
  • FULL_NAME — the person's complete display name, derived via the HR_PERSON_NAME package logic and formatted according to the business group name format.
  • NATIONAL_IDENTIFIER — the person's national identifier value (for example, Social Security Number in a US Federal context), useful for identification and matching.
  • NATIONALITY — the person's nationality, exposed as a lookup reference value.

Common Use Cases and Queries

This view is most useful when a report or interface needs the distinct set of persons who currently have personnel action requests filed against them, without returning historical DateTrack rows. A typical query returns the current name and identifier for such persons:

  • Federal HR reporting on active personnel action request populations.
  • Data extraction or integration feeds that require a clean, de-duplicated person list tied to PA requests.
  • Validation queries confirming that a person appears in the PA request workflow before downstream processing.
  • Ad hoc queries joining PERSON_ID to assignment or position tables to obtain current job context.

Sample SQL:

  • SELECT person_id, full_name, national_identifier FROM apps.ghr_people_v ORDER BY full_name;
  • SELECT g.person_id, g.full_name, a.position_id, a.supervisor_id FROM apps.ghr_people_v g, apps.per_all_assignments_f a WHERE a.person_id = g.person_id AND TRUNC(SYSDATE) BETWEEN a.effective_start_date AND a.effective_end_date;
  • SELECT COUNT(*) FROM apps.ghr_people_v;

Because the view relies on HR_SECURITY and GHR_PA_REQUESTS, results are governed by the calling session's security profile and by the existence of personnel action request rows. Consumers should therefore avoid treating GHR_PEOPLE_V as a complete employee roster; for a full population, query PER_PEOPLE_F directly.