Results for “igs_en_merge_id_rows”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_EN_MERGE_ID_ROWS is a table owned by the IGS schema within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to contain the rows of tables involved in the Merge Id process — the operation through which records associated with one person identifier are consolidated into another person identifier during student, enrollment, or person-data maintenance. Each row in this table captures the linkage between an obsolete person identity and the current (surviving) person identity, together with enough row-level locator information to trace or re-process the affected records.

The table resides in the IGS schema and is reported as VALID in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2. Its primary key is IGS_EN_MERGE_ID_ROWS_PK, defined on the SMIR_ID column, and a unique index IGS_EN_MERGE_ID_ROWS_U1 also exists on SMIR_ID, making SMIR_ID both the surrogate primary key and the sole documented business-key candidate. From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table carries descriptive and transactional attributes describing the merge event rather than functioning as a pure hub or link.

Key Information Stored

The table exposes 15 documented columns. The most significant are:

• SMIR_ID — the surrogate primary key and unique business-key candidate; identifies a single merge-id row record and is referenced by dependent tables.
• TABLE_ALIAS — identifies which source table the affected row belongs to, allowing the merge process to resolve rows across multiple IGS and HZ tables.
• OBSOLETE_PERSON_ID — foreign key to HZ_PARTIES, holding the person identifier being retired by the merge.
• CURRENT_PERSON_ID — foreign key to HZ_PARTIES, holding the surviving person identifier to which data is consolidated.
• OBSOLETE_ID_ROW_INFO — descriptive information about the obsolete-side row involved in the merge.
• OBSOLETE_ID_ROWID — the physical ROWID of the obsolete-side record, enabling direct row access and re-processing.
• OBSOLETE_UPDATE_ON — timestamp recording when the obsolete-side row was updated by the merge.
• CURRENT_ID_ROW_INFO — descriptive information about the current-side row involved in the merge.
• CURRENT_ID_ROWID — the physical ROWID of the current-side record.
• CURRENT_UPDATE_ON — timestamp recording when the current-side row was updated by the merge.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO-column audit attributes capturing user, timestamp, and login context.

Common Use Cases and Queries

The primary operational use is auditing and troubleshooting merge-id executions: identifying which rows in which tables were touched, and when. A typical audit query joins to HZ_PARTIES on both person identifiers:

• Audit a specific merge: SELECT m.SMIR_ID, m.TABLE_ALIAS, m.OBSOLETE_PERSON_ID, m.CURRENT_PERSON_ID, m.CURRENT_UPDATE_ON FROM IGS.IGS_EN_MERGE_ID_ROWS m WHERE m.OBSOLETE_PERSON_ID = :p_obsolete_id;
• Resolve party names for both sides of the merge: join OBSOLETE_PERSON_ID and CURRENT_PERSON_ID to HZ_PARTIES.PARTY_ID to produce readable audit reports.
• Re-process or roll back affected records by using OBSOLETE_ID_ROWID and CURRENT_ID_ROWID to locate the exact physical rows.
• Reporting on merge volume by TABLE_ALIAS or by CREATION_DATE range to monitor data-quality remediation activity.

Related Objects

The documented foreign keys and referencing relationships identify the following significant objects:

• HZ_PARTIES — referenced twice, via IGS_EN_MERGE_ID_ROWS.OBSOLETE_PERSON_ID and IGS_EN_MERGE_ID_ROWS.CURRENT_PERSON_ID.
• IGS_EN_MRG_ID_ACT_CH — child table referencing this table through its SMIR_ID column, holding merge-id activity change details.
• IGS_EN_MERGE_ID_ROWS_PK and IGS_EN_MERGE_ID_ROWS_U1 — the primary key constraint and unique index on SMIR_ID.