Search Results admn_term




Overview
Explore in AI Chat

Overview

APPS.IGF_AP_RECORD_MATCH_V is a reporting and integration view in Oracle E-Business Suite that exposes the full column set of the IGF_AP_RECORD_MATCH base table. Within the Oracle Financial Aid (IGF) product family, "AP" denotes the Applicant/Applicant Processing context, and the underlying table stores record-matching configuration and result data used by the financial aid matching engine to identify duplicate or related applicant records. The view is defined as a straightforward SELECT projection over the single base table, exposing all twenty-nine columns without filtering, joining, or transformation.

In EBS 12.1.1 and 12.2.2, such views exist primarily to provide a stable, read-only interface for concurrent programs, self-service pages, and external integrations that must query match data without depending directly on base-table DDL. Because the view presents the base table's complete column list, it also serves as a convenient inspection point for developers validating match configuration.

Underlying Base Objects

The view is defined over exactly one object, documented as IGF_AP_RECORD_MATCH. No joins, unions, or referenced secondary objects appear in the ETRM view text. The complete definition is:

  • SELECT row_id, arm_id, ssn, given_name, surname, birth_dt, address, city, zip, min_score_auto_fa, min_score_rvw_fa, admn_term, created_by, creation_date, last_updated_by, last_update_date, last_update_login, match_code, match_desc, gender_num, email_num, enabled_flag, 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 FROM igf_ap_record_match

Because the view is a one-to-one projection, its row count, cardinality, and predicates are identical to those of IGF_AP_RECORD_MATCH. Users of the view inherit the base table's WHO audit columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) and its ROW_ID pseudo-key.

Key Columns

The view exposes identity, matching-configuration, and match-key attributes. Notable columns include:

Common Use Cases and Queries

Typical usage includes diagnosing why a given applicant pair did or did not match, auditing configured score thresholds, and extracting match results for reporting. A representative query locating a specific match transformation follows:

  • SELECT arm_id, given_name, given_name_mt_txt, surname, surname_mt_txt, match_code FROM apps.igf_ap_record_match_v WHERE given_name_mt_txt IS NOT NULL;

Because the view performs no filtering, callers must supply their own predicates on ARM_ID, MATCH_CODE, or ENABLED_FLAG to restrict results. Integration code should treat the view as read-only, as it carries no INSTEAD OF trigger.