Search Results igs_pe_mtch_set_data_all




Overview
Explore in AI Chat

Overview

IGS_PE_MTCH_SET_DATA_ALL is a configuration table within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to describe the data required for duplicate match set criteria. In operational terms, the table stores the individual data elements that participate in a duplicate-detection rule, together with the matching behaviour applied to each element. A "match set" defines how the institution identifies potential duplicate person records; each row in IGS_PE_MTCH_SET_DATA_ALL defines one attribute of that rule and how strictly it must agree.

The object carries an Oracle "Obsolete" product designation in the current release, and the ETRM implementation notes record that it is not implemented in the reference database. It should therefore be treated as a legacy or de-supported data structure in EBS 12.1.1 / 12.2.2 environments rather than an actively maintained table. Where it exists, it remains subject to the standard multi-org column ORG_ID and the standard WHO audit columns.

The ETRM metadata offers the heuristic Data Vault classification of "standalone." The natural modeling suggestion is that this table behaves as a satellite-like descriptor of the match set header, since it carries no downstream dependents of its own and its identifying information is supplied by its parent match set. This classification is inferred from FK structure only and should be validated against the actual implementation.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

Common Use Cases and Queries

Typical use is to inspect or report on the criteria that make up a given duplicate match set, and to audit how aggressively duplicate detection is configured.

  • List all data elements for a match set: SELECT data_element, value, exact_include, partial_include, drop_if_null FROM igs_pe_mtch_set_data_all WHERE match_set_id = :p_match_set_id ORDER BY match_set_data_id;
  • Identify match sets that rely on partial matching: SELECT match_set_id, data_element FROM igs_pe_mtch_set_data_all WHERE partial_include = 'Y' AND org_id = :p_org_id;
  • Detect potentially weak criteria where null values suppress the check: SELECT * FROM igs_pe_mtch_set_data_all WHERE drop_if_null = 'Y';
  • Join to the header to produce a readable rule listing: SELECT h.match_set_name, d.data_element, d.value FROM igs_pe_match_sets_all h, igs_pe_mtch_set_data_all d WHERE h.match_set_id = d.match_set_id;

These queries support configuration review, migration validation, and troubleshooting of duplicate-identification outcomes during student or person data conversion.

Related Objects

  • IGS_PE_MATCH_SETS_ALL — the parent table; joined on MATCH_SET_ID = MATCH_SET_ID, supplying the match set header and name.
  • IGS_PE_MATCH_SET_DATA_PK — the primary key constraint on MATCH_SET_DATA_ID.
  • IGS_PE_MTCH_SET_DATA_U1 — unique index enforcing MATCH_SET_DATA_ID uniqueness.
  • IGS_PE_PERSON / person-registry tables — the duplicate detection executed by these rules is applied against person records, making this table an input to person de-duplication rather than a dependent of it.
  • IGS_PE_* match and duplicate APIs — the runtime duplicate-matching processes that consume the criteria defined here.