Search Results igs_pe_mtch_set_data_u1

Overview

IGS.IGS_PE_MTCH_SET_DATA_ALL is a transactional table in the Oracle E-Business Suite IGS (Intelligent Grants / Student Systems) schema that describes the data elements required for duplicate match set criteria. It stores the individual criteria rows that, when grouped under a match set, govern how Oracle detects potential duplicates — for example when comparing person, prospect, or organization records during HZ/IGS party matching. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, consistent with standard transaction data storage in EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the dependency metadata classifies this object as standalone (heuristic, mined from FK structure). In modeling terms, this suggests IGS_PE_MTCH_SET_DATA_ALL behaves less like a dependent satellite and more as a self-contained configuration detail table: it carries its own surrogate key, a foreign reference to the parent match set, and descriptive attributes describing match behavior. Where a strict Data Vault design is desired, MATCH_SET_DATA_ID can be treated as the hub key candidate and MATCH_SET_ID as the link to IGS_PE_MATCH_SETS_ALL.

Key Information Stored

The table is documented with 13 columns. The most significant are:

• MATCH_SET_DATA_ID — NUMBER(15), mandatory surrogate primary key (IGS_PE_MATCH_SET_DATA_PK) and the column backed by the unique index IGS_PE_MTCH_SET_DATA_U1. This is the true business-key candidate for row-level identification.
• MATCH_SET_ID — NUMBER(15), identifier of the duplicate match set criteria. This is the foreign key joining to IGS_PE_MATCH_SETS_ALL and is indexed by IGS_PE_MTCH_SET_DATA_ALL_N1.
• DATA_ELEMENT — VARCHAR2(30), the name of the data element being evaluated (e.g., a party attribute such as name, tax identifier, or address component).
• VALUE — VARCHAR2(30), the value of the data element used in the match comparison.
• EXACT_INCLUDE — VARCHAR2 flag indicating whether the data element participates in an exact match; indexed by IGS_PE_MTCH_SET_DATA_ALL_N2.
• PARTIAL_INCLUDE — VARCHAR2 flag indicating whether the data element participates in a partial (fuzzy) match; indexed by IGS_PE_MTCH_SET_DATA_ALL_N3.
• DROP_IF_NULL — VARCHAR2 flag indicating whether the data element should be dropped from the match when its value is null.
• ORG_ID — NUMBER(15), operating unit identifier, reinforcing multi-org (MOAC) separation.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — provide audit lineage required by EBS concurrent and audit frameworks.

Note that the surrogate key (MATCH_SET_DATA_ID) is distinct from the natural/business grouping represented by MATCH_SET_ID plus DATA_ELEMENT; only MATCH_SET_DATA_ID is documented as unique.

Common Use Cases and Queries

Typical scenarios include auditing duplicate-detection configuration, reporting which elements drive exact versus partial matching, and troubleshooting unexpected duplicate or non-duplicate outcomes during party or prospect import.

Listing all criteria for a given match set:

• SELECT d.MATCH_SET_DATA_ID, d.DATA_ELEMENT, d.VALUE, d.EXACT_INCLUDE, d.PARTIAL_INCLUDE, d.DROP_IF_NULL FROM IGS.IGS_PE_MTCH_SET_DATA_ALL d WHERE d.MATCH_SET_ID = :p_match_set_id AND d.ORG_ID = :p_org_id;

Isolating elements used in exact matching only:

• SELECT DATA_ELEMENT, VALUE FROM IGS.IGS_PE_MTCH_SET_DATA_ALL WHERE EXACT_INCLUDE = 'Y' AND PARTIAL_INCLUDE = 'N' AND ORG_ID = :p_org_id;

Joining to the parent match set for a full picture of the rule configuration uses MATCH_SET_ID. Because the indexed columns (MATCH_SET_ID, EXACT_INCLUDE, PARTIAL_INCLUDE) filter efficiently, reporting queries should always constrain on ORG_ID and MATCH_SET_ID to respect MOAC and leverage the N1/N2/N3 indexes.

Related Objects

The most significant related objects, grounded in the documented FK and index metadata, are:

• IGS.IGS_PE_MATCH_SETS_ALL — parent table referenced via MATCH_SET_ID; the primary join for reconstructing a complete match set definition.
• IGS_PE_MTCH_SET_DATA_U1 — unique index on MATCH_SET_DATA_ID (APPS_TS_TX_IDX); the enforcement point for the primary key.
• IGS_PE_MTCH_SET_DATA_ALL_N1 — non-unique index on MATCH_SET_ID; supports parent-child joins.
• IGS_PE_MTCH_SET_DATA_ALL_N2 — non-unique index on EXACT_INCLUDE; supports exact-match reporting filters.
• IGS_PE_MTCH_SET_DATA_ALL_N3 — non-unique index on PARTIAL_INCLUDE; supports partial-match reporting filters.
• IGS_PE_MATCH_SET_DATA_PK — the primary key constraint defining row uniqueness.
• Related IGS/HZ duplicate-detection and party-matching logic consumes these criteria rows indirectly through the match set framework rather than through direct DML, so customization of this table should be confined to controlled configuration interfaces.