Search Results given_names




Overview
Explore in AI Chat

Overview

IGS_PE_DUP_MATCHES_PP_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS (Student System) product family. Its documented purpose is to expose duplicate person information held against the person and party model, allowing student administration users and integration components to identify and review potential duplicate records for the same individual. In the Oracle EBS 12.1.1 and 12.2.2 releases, the view is registered in ETRM with a status of VALID, confirming that the underlying definition resolves successfully against the standard schema objects shipped with those releases.

The view serves both reporting and data-cleansing functions. Reporting consumers use it to enumerate person records alongside the alternate identifiers and demographic attributes that are typically used in duplicate-detection logic, while integration components use it as a pre-built projection of the person model so that callers do not have to reproduce the joins against the base tables themselves. Because the view normalises the TCA person attributes into Student System naming conventions, it is particularly useful where downstream logic expects IGS-style column names rather than the raw HZ_PARTIES column names.

Underlying Base Objects

The view is defined over four documented base objects: HZ_PARTIES, HZ_PERSON_PROFILES, IGS_PE_ALT_PERS_ID, and IGS_PE_PERSON_ID_TYPE_V. HZ_PARTIES is the primary driver, supplying party identity, party number, and the person name attributes. HZ_PERSON_PROFILES is joined on PARTY_ID and is date-filtered so that only the currently effective profile row is returned, using SYSDATE between EFFECTIVE_START_DATE and NVL(EFFECTIVE_END_DATE, SYSDATE).

IGS_PE_ALT_PERS_ID and IGS_PE_PERSON_ID_TYPE_V are both outer-joined, as indicated by the (+) operators in the view text. The most recent alternate person identifier is surfaced through IGS_PE_PERSON_ID_TYPE_V, which supplies PREF_ALTERNATE_ID; this outer join ensures that persons without a preferred alternate identifier are still returned. IGS_PE_ALT_PERS_ID is outer-joined on PE_PERSON_ID and supplies the alternate person identifier rows, their identifier types, and their effective date ranges.

Key Columns

  • PERSON_ID / PERSON_NUMBER — mapped from HZ_PARTIES.PARTY_ID and PARTY_NUMBER, providing the primary party identity and human-readable party number.
  • SURNAME / GIVEN_NAMES — derived from PERSON_LAST_NAME and PERSON_FIRST_NAME. GIVEN_NAMES is the column most directly associated with the "given_names" search term, and it is accompanied by GIVEN_NAME_1_CHAR, which exposes the first character of the given name for phonetic or initial-based matching.
  • SURNAME_5_CHAR — defined as NULL in the view text, indicating the column is retained for interface compatibility but not populated.
  • SEX / BIRTH_DT — sourced from HZ_PERSON_PROFILES.GENDER and DATE_OF_BIRTH, both commonly used as matching criteria in duplicate detection.
  • PREF_ALTERNATE_ID — from IGS_PE_PERSON_ID_TYPE_V.API_PERSON_ID, the preferred alternate identifier for the person.
  • API_PERSON_ID / PERSON_ID_TYPE / API_START_DATE / API_END_DATE — the alternate person identifier value, its classification, and the period during which it is effective.
  • ETHNIC_ORIGIN_ID — from DECLARED_ETHNICITY; the documented column list labels this position ETHNIC_ORIGIN, while the view text labels it ETHNIC_ORIGIN_ID.
  • STATUS — the party status value from HZ_PARTIES.

Common Use Cases and Queries

The view is typically queried to produce candidate duplicate sets for review, to reconcile alternate identifiers against party records, or to feed name-matching routines that rely on surname and given name combinations.

A basic lookup on given name and surname:

  • SELECT person_id, person_number, surname, given_names, birth_dt FROM apps.igs_pe_dup_matches_pp_v WHERE UPPER(given_names) = UPPER(:given_name) AND UPPER(surname) = UPPER(:surname);

An initial-based candidate scan using the one-character column:

  • SELECT person_id, person_number, surname, given_names, given_name_1_char, birth_dt FROM apps.igs_pe_dup_matches_pp_v WHERE given_name_1_char = :initial AND birth_dt = :dob;

Retrieving preferred alternate identifiers for a known party:

  • SELECT person_id, person_number, pref_alternate_id, api_person_id, person_id_type FROM apps.igs_pe_dup_matches_pp_v WHERE person_id = :party_id;