Search Results igf_ap_match_details




Overview
Explore in AI Chat

Overview

The IGF_AP_MATCH_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Financial Aid module (product code IGF). It resides in the IGF schema and holds the granular match details produced when a student record only partially matches an incoming ISIR (Institutional Student Information Record) or Profile record. Rather than storing a binary matched/unmatched flag, the table captures the outcome of individual comparison attributes—Social Security Number, given name, surname, date of birth, address, city, ZIP, gender, and email—so that financial aid administrators can evaluate why an automatic match succeeded or failed. This granular detail supports exception handling, manual review, and reconciliation between federal or institutional data feeds and the institution's person records.

From a dimensional modeling perspective, the ETRM metadata's heuristic Data Vault classification for this object is satellite-leaning. This suggests the table behaves as a descriptive satellite attached to a parent hub or link, in this case anchored through its foreign key to IGF_AP_PERSON_MATCH_ALL. The classification is a modeling suggestion based on the mined foreign-key structure rather than a definitive architectural mandate.

Key Information Stored

The table is defined with 28 documented columns. The most significant are summarized below.

Common Use Cases and Queries

Typical use cases center on diagnosing partial ISIR/Profile matches and reporting on match quality. A frequent pattern joins detail rows to the parent match record to retrieve the full matching context:

  • Retrieving all partial-match details for a given person or parent match: SELECT * FROM IGF.IGF_AP_MATCH_DETAILS WHERE APM_ID = :apm_id;
  • Identifying low-confidence matches for manual review: SELECT AMD_ID, PERSON_ID, MATCH_SCORE FROM IGF.IGF_AP_MATCH_DETAILS WHERE MATCH_SCORE < :threshold;
  • Profiling which attributes most often fail to match (for example, counting SSN_MATCH or DOB_MATCH flags) to assess data quality in upstream feeds.
  • Joining to IGF_AP_PERSON_MATCH_ALL on APM_ID to combine match summaries with their attribute-level breakdown.
  • Operational reporting on match volumes over time using CREATION_DATE and RECORD_STATUS.

Related Objects

The most significant relationships are the parent and person-level tables referenced or implied by the documented key structure:

  • IGF_AP_PERSON_MATCH_ALL — The parent table referenced by the APM_ID foreign key; it provides the overarching person-match record to which each detail row belongs.
  • IGF_AP_MATCH_DETAILS_PK — The primary key constraint on AMD_ID that guarantees uniqueness of each detail row.
  • Person-level IGF tables — Objects keyed on PERSON_ID that supply the underlying student or applicant identity for the match evaluation.
  • ISIR / Profile feed tables — Source objects from which incoming federal and institutional records are compared, generating the match flags and text values captured here.

Together these relationships position IGF_AP_MATCH_DETAILS as the detailed satellite supporting person-match reconciliation within the Financial Aid module.