Search Results duplicate_pair_id

Overview

IGS.IGS_PE_DUP_PAIRS_ALL is a transactional table within the IGS (Student System) product family of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its purpose, per the ETRM metadata, is to describe the duplicate pair of persons held in the system. Each row therefore represents a single candidate duplicate relationship between two person records identified by the Oracle Student System duplicate-identification and person-matching process, together with the status, matching category, and context under which that pairing was detected.

The object is delivered with 21 documented columns and is owned by the IGS schema. It has a single-column surrogate primary key, DUPLICATE_PAIR_ID, enforced by the constraint IGS_PE_DUPLICATE_PAIRS_PK. A unique index, IGS_PEDUP_PAIRS_U1, also exists on DUPLICATE_PAIR_ID. From a Data Vault modeling perspective — offered here strictly as a heuristic mined from the foreign key structure — the table behaves as a standalone structure, resolving to a link-style entity that associates two person participants plus an associated match set, rather than a pure hub or satellite.

Key Information Stored

The most significant columns in IGS_PE_DUP_PAIRS_ALL are:

• DUPLICATE_PAIR_ID — surrogate primary key uniquely identifying each duplicate pair record; also the unique index business-key candidate IGS_PEDUP_PAIRS_U1.
• ACTUAL_PERSON_ID — the person identifier treated as the surviving or reference person in the pairing.
• DUPLICATE_PERSON_ID — the person identifier identified as the potential duplicate of the actual person.
• MATCH_SET_ID — foreign key to IGS_PE_MATCH_SETS_ALL, linking the pair to the match set in which it was generated.
• BATCH_ID — the duplicate-identification batch that produced or processed the pair.
• MATCH_CATEGORY — classification of the match, distinguishing the nature or strength of the detected similarity.
• DUP_STATUS — workflow status of the pair (for example pending, confirmed, or rejected).
• OBSOLETE_ID — reference to the obsolete or superseded person record involved in the pairing.
• ADDRESS_TYPE and LOCATION_ID — the address context and location used or implicated during matching.
• PERSON_ID_TYPE — the person identifier type relevant to the pair.
• ORG_ID — the operating unit / organization partition for multi-org security.
• Standard WHO audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Concurrent-program context: REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses center on duplicate person resolution: reviewing open duplicates awaiting a decision, reporting the volume of duplicates produced per batch or match set, and auditing which pairs were confirmed or rejected. A representative query joins the pair to its match set and filters by status:

SELECT dp.duplicate_pair_id, dp.actual_person_id, dp.duplicate_person_id,
  dp.dup_status, dp.match_category, dp.batch_id
FROM igs.igs_pe_dup_pairs_all dp
WHERE dp.dup_status = 'PENDING';

To summarize duplicates generated by each batch, group by BATCH_ID and MATCH_SET_ID, joining MATCH_SET_ID to IGS_PE_MATCH_SETS_ALL. Because ORG_ID is present, multi-org reports should always predicate on the appropriate operating unit. Concurrent-program metadata (REQUEST_ID, PROGRAM_ID) supports tracing which process created a given pair.

Related Objects

• IGS_PE_MATCH_SETS_ALL — referenced by MATCH_SET_ID; the parent match set for the pair.
• Person / party tables referenced conceptually by ACTUAL_PERSON_ID and DUPLICATE_PERSON_ID, used to resolve person names and numbers.
• IGS_PE_DUP_PAIRS_ALL unique index IGS_PEDUP_PAIRS_U1 and constraint IGS_PE_DUPLICATE_PAIRS_PK for key access.
• Duplicate-identification batch and concurrent-program tables referenced by BATCH_ID, REQUEST_ID, and PROGRAM_ID.
• Multi-org / organization tables referenced by ORG_ID for operating-unit filtering.