Search Results duplicate_person_id




Overview
Explore in AI Chat

Overview

APPS.IGS_PE_PAIR_DUP_PERSON_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as IGS.IGS_PE_PAIR_DUP_PERSON_V. Within the Oracle Student System / People Enterprise (IGS) product family, it is classified as a "supplementary view used to simplify forms coding." Oracle explicitly warns that this view should not be queried or altered directly, because its definition may change dramatically in subsequent minor or major releases. It is intended primarily to support Oracle Forms-based duplicate person review and resolution screens, not as a stable public interface for reporting or integration.

The view joins duplicate-person pair data with person demographic information, exposing fields that let a form display side-by-side demographic attributes for the actual person and the suspected duplicate, along with match metadata. Because the object is documented as a Forms-support view rather than a certified reporting interface, custom integrations should treat it as volatile.

Underlying Base Objects

ETRM documents the view as referencing the following objects:

  • IGS_PE_DUP_PAIRS — the base duplicate-person pair table, supplying pair, batch, match-set and status identifiers.
  • IGS_PE_PERSON_V — the person demographic view, supplying surname, given names, sex, birth date and alternate identifier data.
  • IGS_PE_STAT_V — a status view contributing status-related attributes.
  • IGS_EN_GEN_003 and IGS_EN_GEN_007 — generic code/validation objects referenced for descriptive or lookup purposes.

The view is not documented as being referenced by any other object, confirming its role as a terminal presentation layer for Forms rather than a shared dependency.

Key Columns

Common Use Cases and Queries

The principal use case is diagnosing why a person appears as a duplicate and inspecting the demographic pair data. Because direct querying is not recommended by Oracle, production use should normally be limited to support and troubleshooting.

  • Confirming which duplicate pairs reference a given person:

SELECT DUPLICATE_PAIR_ID, ACTUAL_PERSON_ID, DUPLICATE_PERSON_ID, DUP_STATUS, MATCH_CATEGORY FROM APPS.IGS_PE_PAIR_DUP_PERSON_V WHERE ACTUAL_PERSON_ID = :p_person_id OR DUPLICATE_PERSON_ID = :p_person_id;

  • Reviewing a match batch:

SELECT BATCH_ID, MATCH_SET_ID, COUNT(*) FROM APPS.IGS_PE_PAIR_DUP_PERSON_V GROUP BY BATCH_ID, MATCH_SET_ID;

Given the volatility warning and the presence of clearly obsolete columns, any requirement for persistent duplicate-person reporting should be redirected to the underlying tables IGS_PE_DUP_PAIRS and the person tables, or to an Oracle-certified reporting interface, rather than this Forms-only supplementary view.