Search Results act_person_name

Overview

IGS_PE_DUP_PAIRS_V is a reporting and inquiry view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It exposes the contents of the duplicate person tracking structures in a denormalized, human-readable form, joining the duplicate pair records to the person records on both sides of the match and to the match set definition that produced the pairing. In both EBS 12.1.1 and 12.2.2 the object is delivered as a VALID view, meaning it is a supported, query-only database object and not a table that applications write to directly. Its role in EBS reporting and integration is to provide a single relational source for duplicate person detection output, supporting person data quality reconciliation, duplicate resolution workflows, and downstream extracts. Because the view resolves person identifiers into meaningful attributes such as person numbers and formatted names, it is suitable for use in concurrent program reports, Oracle BI Publisher data templates, and custom SQL-based inquiries without requiring the developer to reproduce the multi-table join logic.

Underlying Base Objects

The view is defined over four APPS tables. IGS_PE_DUP_PAIRS supplies the transaction-level duplicate pairing record, including the batch identifier, the identifiers of the two persons involved, the match category, the match set, and the current duplicate status. IGS_PE_PERSON is joined twice through aliases P1 and P2, once for the actual person and once for the duplicate person, to resolve PERSON_NUMBER and name attributes for each side of the pair. IGS_PE_MATCH_SETS supplies MATCH_SET_NAME, providing the descriptive name of the matching rule set under which the pair was identified. The join predicates equate DP.ACTUAL_PERSON_ID and DP.DUPLICATE_PERSON_ID to the respective PERSON_ID values, and DP.MATCH_SET_ID to the match set identifier. Although the ETRM metadata records no referenced base objects, the view text establishes these four tables as the definitive dependency set. The view text additionally derives a ROW_ID from the IGS_PE_DUP_PAIRS ROWID, which is exposed for row-level identification during interactive processing.

Key Columns

• ROW_ID, DUPLICATE_PAIR_ID, BATCH_ID — Row locator, primary pair identifier, and the batch in which the pairing was generated.
• ACTUAL_PERSON_ID / ACTUAL_PERSON_NUMBER — The surviving or reference person in the pair, with the resolved person number.
• DUPLICATE_PERSON_ID / DUPLICATE_PERSON_NUMBER — The suspected duplicate person and the resolved person number.
• OBSOLETE_ID — Legacy identifier retained for backward compatibility.
• MATCH_CATEGORY, MATCH_SET_ID, MATCH_SET_NAME — The category and named rule set that produced the match.
• DUP_STATUS — The disposition of the duplicate pair within the resolution cycle.
• ADDR_TYPE, LOCATION_ID, PERSON_ID_TYPE — Contextual attributes of the match, including address type, location, and the type of identification used.
• ACT_PERSON_NAME / DUP_PERSON_NAME — Concatenated display names in surname, title, given names format using INITCAP.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Standard EBS who-columns.

Common Use Cases and Queries

Typical usage includes listing open duplicate pairs for a review batch, identifying duplicate pairs awaiting resolution, and producing extracts of duplicate name candidates for data stewards. A representative query follows:

SELECT duplicate_pair_id, batch_id, actual_person_number, act_person_name, duplicate_person_number, dup_person_name, match_set_name, dup_status FROM apps.igs_pe_dup_pairs_v WHERE dup_status = 'OPEN' ORDER BY batch_id, duplicate_pair_id;

Additional patterns include filtering by MATCH_SET_NAME to evaluate rule effectiveness, joining DUPLICATE_PAIR_ID back to resolution tables, and summarizing counts by MATCH_CATEGORY for data quality dashboards. Because the view performs the person and match set joins internally, no additional joins are required for most reporting requirements.