Search Results igf_ap_record_match_u2

Overview

IGF.IGF_AP_RECORD_MATCH_ALL is a configuration and scoring table within the Oracle E-Business Suite Financial Aid (IGF) module. It stores the person attributes — and their associated matching weights — that the system uses when attempting to match an incoming ISIR (Institutional Student Information Record) or Profile record against an existing person record in the database. In effect, the table defines the fuzzy-matching rule set that governs whether a new applicant record is reliably linked to an existing individual or treated as a new person.

Beyond storing the match attributes, the table also holds the threshold scores that control downstream automation, specifically the minimum score required for automatic creation of a Financial Aid (FA) base record and the minimum score required for manual review. Each row therefore represents a named match criterion configuration, scoped by organization and admission term.

Under the heuristic Data Vault classification mined from the documented FK structure, this object is standalone. In Data Vault modeling terms, it is best treated as a reference or configuration satellite rather than a hub or link, since it holds descriptive scoring rules rather than business entity keys or transactional relationships.

Key Information Stored

The table is defined with 30 columns. The surrogate primary key is ARM_ID, backed by the unique index IGF_AP_RECORD_MATCH_U1. The documented business-key candidate is MATCH_CODE, backed by the unique index IGF_AP_RECORD_MATCH_U2 — this is the index referenced by the search term "igf_ap_record_match_u2". The most significant columns are:

• ARM_ID — Surrogate primary key (sequence-generated).
• MATCH_CODE — Business identifier for the match criteria; unique.
• MATCH_DESC — Human-readable description of the match criteria.
• ORG_ID — Standard multi-org partitioning column.
• SSN, GIVEN_NAME, SURNAME, BIRTH_DT, ADDRESS, CITY, ZIP, GENDER_NUM, EMAIL_NUM — Numeric weights applied to each person attribute during scoring.
• GIVEN_NAME_MT_TXT, SURNAME_MT_TXT, BIRTH_DT_MT_TXT, ADDRESS_MT_TXT, CITY_MT_TXT, ZIP_MT_TXT, GENDER_MT_TXT, EMAIL_MT_TXT — Match type to apply per attribute.
• MIN_SCORE_AUTO_FA — Threshold for automatic FA base record creation.
• MIN_SCORE_RVW_FA — Threshold for manual review before FA base record creation.
• ADMN_TERM — Admission term to which the configuration applies.
• ENABLED_FLAG — Active indicator for the configuration row.

Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical usage centers on administrative review of matching thresholds and on tracing why a particular incoming record was auto-matched, held for review, or rejected. Common patterns include retrieving active configurations by organization and term, and auditing score weights per attribute.

• List active match configurations for a term: SELECT MATCH_CODE, MATCH_DESC, MIN_SCORE_AUTO_FA, MIN_SCORE_RVW_FA FROM IGF_AP_RECORD_MATCH_ALL WHERE ENABLED_FLAG = 'Y' AND ORG_ID = :org_id;
• Inspect per-attribute weights: SELECT MATCH_CODE, SSN, GIVEN_NAME, SURNAME, BIRTH_DT FROM IGF_AP_RECORD_MATCH_ALL WHERE MATCH_CODE = :match_code;
• Lookup by business key using the U2 index: SELECT * FROM IGF_AP_RECORD_MATCH_ALL WHERE MATCH_CODE = :match_code;

These queries support configuration reporting, tuning of match thresholds, and troubleshooting of Financial Aid record-creation decisions.

Related Objects

The documented relationship data classifies this object as standalone, with no FK dependencies mined. Significant related objects within the IGF application include:

• IGF_AP_RECORD_MATCH_ALL itself, joined on MATCH_CODE for business-key lookups and on ARM_ID for surrogate-key lookups.
• ISIR and Profile staging/processing tables in the IGF schema that reference match criteria by MATCH_CODE during record matching.
• Person and FA base record tables in the IGF schema that receive creation or review outcomes based on MIN_SCORE_AUTO_FA and MIN_SCORE_RVW_FA.
• Standard FND/lookup tables supplying valid values for ENABLED_FLAG and the *_MT_TXT match types.

Because the object is standalone, join relationships are largely application-enforced via MATCH_CODE rather than by database constraints.