Results for “match_set_name”

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

Overview

IGS_PE_MATCH_SETS_ALL is a configuration table within the Oracle E-Business Suite student system (IGS) product family, historically associated with the Oracle Student System and its person-matching / address-matching engine. The table stores the match set criteria configured by users, i.e. the reusable rule definitions that govern how records are compared, scored, and resolved during matching operations. Although the product is documented as obsolete in later releases, the table remains catalogued in the ETRM reference for EBS 12.1.1 and 12.2.2, and the physical schema is documented with fourteen columns in the IGS schema.

From a Data Vault modeling perspective, the FK relationships mined from the schema classify this object as hub-leaning: MATCH_SET_ID is a stable, unique business identifier that is referenced by dependent tables such as IGS_AD_INTERFACE_CTL and IGS_AD_IMP_NEAR_MTCH_ALL. This classification is a heuristic modeling suggestion rather than an Oracle-imposed constraint; functionally, the table behaves as the master definition of a match set, with dependent transaction and control tables pointing back to it.

The table is listed as "Not implemented in this database" in the documentation, meaning it may not exist or may be empty in a given EBS instance. This status must be verified per environment before any dependency is built on it.

Key Information Stored

The most significant columns documented for the table are:

• MATCH_SET_ID – surrogate primary key (IGS_PE_MATCH_SETS_PK) and the value propagated to all dependent tables via foreign keys.
• MATCH_SET_NAME – unique business key candidate, enforced by unique index IGS_PE_MATCH_SETS_U2; the user-recognizable name of the match set.
• DESCRIPTION – free-text explanation of the match set's purpose.
• SOURCE_TYPE_ID – identifies the source of the records being matched, distinguishing match sets by origin or category.
• CLOSED_IND – flags whether the match set is closed to further use.
• PARTIAL_IF_NULL – controls matching behaviour when comparison data is missing, allowing a partial match result.
• PRIMARY_ADDR_FLAG – indicates whether the primary address is considered during matching.
• EXCLUDE_INACTIVE_IND – excludes inactive records from the match evaluation.
• ORG_ID – multi-org operating unit context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit columns.

A second unique index, IGS_PE_MATCH_SETS_U1, enforces uniqueness on MATCH_SET_ID itself. Together, the surrogate key and the business-key name uniquely identify each configured match set.

Common Use Cases and Queries

Typical usage involves identifying the active match sets available to a control or import process, and joining the match set definition to the records it governs. A representative query retrieves the match sets referenced by the address interface control table:

• SELECT m.match_set_id, m.match_set_name, m.description FROM igs_pe_match_sets_all m WHERE m.closed_ind = 'N';
• SELECT c.match_set_id, m.match_set_name FROM igs_ad_interface_ctl c, igs_pe_match_sets_all m WHERE c.match_set_id = m.match_set_id;
• SELECT n.match_set_id, m.match_set_name, COUNT(*) FROM igs_ad_imp_near_mtch_all n, igs_pe_match_sets_all m WHERE n.match_set_id = m.match_set_id GROUP BY n.match_set_id, m.match_set_name;

Reporting scenarios include auditing which match sets are closed, reviewing the partial-match and exclusion flags configured for each set, and tracing near-match import results back to the rule definition that produced them.

Related Objects

The documented foreign key relationships establish the principal dependencies:

• IGS_AD_INTERFACE_CTL – references IGS_PE_MATCH_SETS_ALL through MATCH_SET_ID, linking control records to the match set in force.
• IGS_AD_IMP_NEAR_MTCH_ALL – references IGS_PE_MATCH_SETS_ALL through MATCH_SET_ID, holding near-match results generated under the configured criteria.
• IGS_PE_MATCH_SETS_PK – primary key constraint on MATCH_SET_ID.
• IGS_PE_MATCH_SETS_UK / IGS_PE_MATCH_SETS_U1 / IGS_PE_MATCH_SETS_U2 – unique constraints and indexes governing MATCH_SET_ID and MATCH_SET_NAME.

Because the surrounding IGS matching tables (interface control and near-match storage) are the only documented dependents, impact analysis for changes to this table should focus on the address interface and import matching processes that consume MATCH_SET_ID.