Search Results igs_pe_match_sets_all




Overview
Explore in AI Chat

Overview

The IGS_PE_MATCH_SETS_ALL table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS), specifically in versions 12.1.1 and 12.2.2. As indicated by its description, this table stores the definition of match set criteria configured by users. A match set is a collection of rules used to identify potential duplicate records, most commonly applied during data import or validation processes to prevent the creation of redundant person or student entities. Its role is to centralize the configuration of matching logic, such as comparing names, dates of birth, or addresses, which can then be referenced by various system interfaces and batch processes. It is important to note that the IGS module is marked as obsolete in the provided documentation, indicating this table is part of a legacy code path.

Key Information Stored

The table's primary purpose is to define and identify unique match sets. The key columns, as defined by its primary and unique keys, are MATCH_SET_ID and MATCH_SET_NAME. The MATCH_SET_ID serves as the system-generated, numeric primary identifier for the match set configuration. The MATCH_SET_NAME is a user-defined, unique textual identifier for the match set, allowing for easy reference in setup screens and process parameters. While the provided metadata does not detail all columns, a table of this nature would typically include descriptive columns, an active indicator, creation and last update dates, and potentially columns controlling the match algorithm's sensitivity or the weighting of different criteria.

Common Use Cases and Queries

The primary use case for this table is managing the configuration of duplicate checking rules within the Student System. Administrators would query this table to review or audit existing match sets. Common operational queries include listing all active match sets or finding the identifier for a specific set by name. For example, a support query to identify all configured match sets would use: SELECT match_set_id, match_set_name FROM igs_pe_match_sets_all WHERE NVL(end_date, SYSDATE) >= SYSDATE ORDER BY match_set_name;. During troubleshooting of data import errors related to duplicate checking, a developer might join this table to the interface control tables to verify which match set criteria were applied to a specific batch process.

Related Objects

Based on the documented foreign key relationships, the IGS_PE_MATCH_SETS_ALL table is referenced by at least two other tables in the Student System interface architecture. These relationships demonstrate how a defined match set is applied operationally:

  • IGS_AD_INTERFACE_CTL: This interface control table references IGS_PE_MATCH_SETS_ALL via the MATCH_SET_ID column. This links a specific data import batch or interface process to the duplicate checking rules it should employ.
  • IGS_AD_IMP_NEAR_MTCH_ALL: This table, likely storing records of near matches found during import, also references IGS_PE_MATCH_SETS_ALL via MATCH_SET_ID. This links individual potential duplicate records back to the specific set of criteria that identified them.
These relationships confirm the table's role as a master definition table for match criteria consumed by interface and import processing logic.