Search Results given_names




Overview
Explore in AI Chat

Overview

IGS_PE_DUP_PAIRS_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivering a denormalized, human-readable projection of duplicate person pairs identified by the Person/Entity matching process within the Oracle Student System (formerly Student Systems / OSS, now part of the Higher Education data model). It is defined over the intersection of the duplicate-pair staging table and three reference tables, exposing surrogate identifiers alongside concatenated person names that are generated on the fly via string concatenation of surname, title, and given names. Because it joins the base tables internally, the view spares developers and report authors from repeatedly coding the multi-table join between IGS_PE_DUP_PAIRS, IGS_PE_PERSON (twice, aliased as P1 and P2), and IGS_PE_MATCH_SETS.

The view supports duplicate-management reporting and integration: it surfaces both the "actual" person (the surviving record) and the "duplicate" person (the record flagged for merge or review), along with the matching category and status. It is therefore useful in person data quality dashboards, duplicate review worklists, and data-cleansing extracts.

Underlying Base Objects

The ETRM metadata for this view documents no referenced base objects, but the supplied view text establishes the following physical base tables explicitly:

  • IGS_PE_DUP_PAIRS (alias DP) — the driving table holding one row per detected duplicate pair.
  • IGS_PE_PERSON (alias P1) — the person record referenced by DP.ACTUAL_PERSON_ID.
  • IGS_PE_PERSON (alias P2) — a second, self-join instance referenced by DP.DUPLICATE_PERSON_ID.
  • IGS_PE_MATCH_SETS (alias MS) — provides the descriptive match-set name.

The join predicates are DP.ACTUAL_PERSON_ID = P1.PERSON_ID, DP.DUPLICATE_PERSON_ID = P2.PERSON_ID, and DP.MATCH_SET_ID = MS.MATCH_SET_ID. The view is read-only in effect and exposes DP.ROWID as ROW_ID.

Key Columns

Common Use Cases and Queries

A typical use is listing open duplicate pairs with both names rendered, filtered by match set or status:

  • SELECT duplicate_pair_id, act_person_name, dup_person_name, match_category, dup_status FROM apps.igs_pe_dup_pairs_v WHERE dup_status = 'OPEN';
  • SELECT batch_id, COUNT(*) FROM apps.igs_pe_dup_pairs_v GROUP BY batch_id;
  • Searching by a person's given name (as implied by the "given_names" query): SELECT duplicate_pair_id, act_person_name, dup_person_name FROM apps.igs_pe_dup_pairs_v WHERE UPPER(act_person_name) LIKE '%' || UPPER(:given_names) || '%' OR UPPER(dup_person_name) LIKE '%' || UPPER(:given_names) || '%';

Because ACT_PERSON_NAME and DUP_PERSON_NAME are computed expressions, filtering on them prevents index use on GIVEN_NAMES; for performance, join IGS_PE_PERSON directly when searching large volumes.