Search Results igf_ap_record_match_v

Overview

IGF_AP_RECORD_MATCH_V is a database view in the Oracle E-Business Suite Financial Aid (IGF) module, which is documented as obsolete in release 12.1.1 and 12.2.2. The view exposes the set of person attributes used by the Financial Aid matching engine to compare a newly received ISIR (Institutional Student Information Record) or Profile record against an existing person record already held in the system. Its documented description is: "Retrieves the person attributes which are to be used for matching new ISIR or Profile record with existing person."

Functionally the view acts as a read-only projection over the matching configuration and person attribute data required by the record matching process. Rather than presenting transactional Financial Aid data, it presents the identity attributes (such as Social Security Number, name components, date of birth, address, city, ZIP, gender and email) that the matching algorithm evaluates when determining whether an incoming record corresponds to an existing person, or whether a new person should be created. Because it is a view, it deliberately abstracts the underlying storage and presents a stable, denormalized column set for reporting and integration consumers.

Underlying Base Objects

According to the ETRM documentation, the view is defined directly over a single base object, the table IGF_AP_RECORD_MATCH. The documented view text is a straightforward projection; no joins, unions, or aggregations are present:

• SELECT ... FROM IGF_AP_RECORD_MATCH

Every column listed in the view is selected directly from that table without transformation or aliasing, so the view is a one-to-one, row-preserving projection of the base table. The ETRM metadata lists the owner as blank and states "Referenced base objects: none documented," and the DBA data section records "Not implemented in this database." This indicates the view may not be instantiated in every environment, particularly where the obsolete IGF Financial Aid module has not been installed. Where the object does exist, its sole documented dependency is IGF_AP_RECORD_MATCH, which stores the matching configuration, scoring thresholds, and person attribute definitions.

Key Columns

The view exposes the full curated column list from the base table. The columns relevant to the "birth_dt" search term, and to matching generally, include:

• ROW_ID – identifier for the base row.
• ARM_ID – identifier linking the matching record to its owning entity or record set.
• SSN, GIVEN_NAME, SURNAME, BIRTH_DT – core person identity attributes used by the matching algorithm. BIRTH_DT carries the date of birth.
• ADDRESS, CITY, ZIP – address matching attributes.
• GENDER_NUM, EMAIL_NUM – coded gender and email attributes.
• MIN_SCORE_AUTO_FA, MIN_SCORE_RVW_FA – score thresholds governing automatic matching versus manual review for Financial Aid records.
• ADMN_TERM – admissions term associated with the match configuration.
• MATCH_CODE, MATCH_DESC – the match result/type code and its description.
• ENABLED_FLAG – indicates whether the matching row is active.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit (WHO) columns.
• 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 – parallel "match text" columns holding the normalized or phonetic forms used for comparison, corresponding to each primary attribute.

Common Use Cases and Queries

Typical uses are auditing the matching configuration, verifying which attributes (including birth date) participate in matching, and diagnosing score thresholds. A representative query listing the active match configuration and its date-of-birth attribute is:

• SELECT ARM_ID, SSN, GIVEN_NAME, SURNAME, BIRTH_DT, BIRTH_DT_MT_TXT, MIN_SCORE_AUTO_FA, MIN_SCORE_RVW_FA, ENABLED_FLAG, MATCH_CODE, MATCH_DESC FROM IGF_AP_RECORD_MATCH_V WHERE ENABLED_FLAG = 'Y';
• SELECT ARM_ID, BIRTH_DT, BIRTH_DT_MT_TXT, ADMN_TERM FROM IGF_AP_RECORD_MATCH_V WHERE BIRTH_DT IS NOT NULL ORDER BY ADMN_TERM;

Because the module is obsolete and the object is not implemented in all databases, confirm availability in the target instance before relying on it in a custom report or integration.