Results for “igs_en_merge_id_log”

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

Overview

The IGS_EN_MERGE_ID_LOG table belongs to the IGS (Student System) product family, a module that is now classified as obsolete within the Oracle E-Business Suite. Its purpose is to maintain an audit-style log of the rows from various tables that participate in the "Merge Id" process, together with a record of the actions that were applied to those rows. In practice, the table captures which person identifier was treated as the obsolete (source) record and which was treated as the current (surviving) target, along with a snapshot of the affected row and the specific operation performed during the merge.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This suggests that the table should be modeled as a link between the person records involved in a merge and the action definitions that govern those merges, rather than as a standalone hub or a descriptive satellite. The table effectively resolves a many-to-many relationship between parties undergoing a merge and the discrete merge actions executed against them.

Key Information Stored

The documented physical schema for the ETRM 12.1.1 release records an owner of IGS and thirteen columns. The most significant of these include:

• SMIL_ID — the surrogate primary key, backed by the unique index IGS_EN_MERGE_ID_LOG_U1 and the IGS_EN_MERGE_ID_LOG_PK constraint. This is the sole documented business-key candidate.
• CURRENT_PERSON_ID — the party identifier (referencing HZ_PARTIES) that survived the merge and now holds the consolidated data.
• OBSOLETE_PERSON_ID — the party identifier (also referencing HZ_PARTIES) that was retired or merged out of use.
• CURRENT_ID_ROW_INFO and OBSOLETE_ID_ROW_INFO — descriptive snapshots of the affected rows for the current and obsolete parties respectively.
• TABLE_ALIAS — identifies the source table involved in the merge, and also serves as a foreign key to IGS_EN_MRG_ID_ACTION.
• ACTION_ID — the action applied, joining to IGS_EN_MRG_ID_ACTION.ACTION_ID.
• PERFORM_ACTION_IND — an indicator of whether the action was actually performed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle Applications who-audit columns that record the user and timestamp of each insert or update.

Note that the metadata states the table is "Not implemented in this database," meaning the object may not exist in every environment, particularly those without the obsolete Student System module.

Common Use Cases and Queries

The primary use case is audit and reconciliation of the Merge Id process. Administrators and support analysts query this log to determine exactly which rows were touched during a person merge, which parties were current versus obsolete, and what actions were applied. A typical join between the log and the party table resembles:

• SELECT l.SMIL_ID, l.CURRENT_PERSON_ID, l.OBSOLETE_PERSON_ID, l.TABLE_ALIAS, l.ACTION_ID, l.PERFORM_ACTION_IND FROM IGS_EN_MERGE_ID_LOG l WHERE l.CURRENT_PERSON_ID = :person_id;
• Joining to HZ_PARTIES on both CURRENT_PERSON_ID and OBSOLETE_PERSON_ID to resolve party names for reporting.
• Joining to IGS_EN_MRG_ID_ACTION on TABLE_ALIAS and ACTION_ID to obtain a readable description of the merge action.

Reporting use cases include merge history reports, investigation of data anomalies following a merge, and verification that expected actions completed successfully by filtering on PERFORM_ACTION_IND.

Related Objects

The most significant related objects, per the documented foreign keys, are:

• HZ_PARTIES — referenced twice, via IGS_EN_MERGE_ID_LOG.CURRENT_PERSON_ID and IGS_EN_MERGE_ID_LOG.OBSOLETE_PERSON_ID, providing the party context for each log entry.
• IGS_EN_MRG_ID_ACTION — referenced via TABLE_ALIAS (and ACTION_ID), supplying the definition of the merge action applied.
• IGS_EN_MERGE_ID_LOG_PK — the primary key constraint on SMIL_ID.
• IGS_EN_MERGE_ID_LOG_U1 — the unique index on SMIL_ID that supports the primary key.

Because the module is obsolete, no further dependent views or public APIs are documented in the ETRM metadata beyond these relationships.