Results for “match_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGF_AP_RECORD_MATCH is a reporting view owned by the APPS schema within the IGF (Financial Aid) product module of Oracle E-Business Suite. Its documented purpose is to retrieve the person attributes that are used to match a new ISIR (Institutional Student Information Record) or Profile record against an existing person. In practice this view exposes the configuration and matching-score thresholds that the institution uses when processing incoming federal or institutional financial aid applicant data and attempting to resolve that data to a known person record.

The view is a secured (organization-filtered) projection over its base object. Rather than simply selecting all rows, it embeds a predicate based on the CLIENT_INFO environment setting, restricting rows to those matching the current organization context. This makes it a multi-org aware view suitable for use in forms, concurrent programs, and ad hoc queries executed within an authenticated EBS session. Because it is a view and is marked VALID, it depends entirely on its underlying real object for storage; it stores no data of its own.

Underlying Base Objects

The documented view text selects all listed columns from a single base table, IGF_AP_RECORD_MATCH_ALL, filtering on ORG_ID. The ETRM metadata notes that no base objects are separately documented, so the operative reference is the FROM clause within the view definition itself. IGF_AP_RECORD_MATCH_ALL is the multi-org enforcement table holding the persisted matching rules, and the public view IGF_AP_RECORD_MATCH is the filtered, presentation-layer wrapper of that table.

The ORG_ID filter is constructed using the standard EBS multi-org pattern: it extracts the first ten characters of USERENV('CLIENT_INFO') and compares that value to ORG_ID, defaulting to -99 when the client info slot is blank. This is the same mechanism used throughout Oracle Applications to scope rows to the operating unit or organization currently in session.

Key Columns

• ROW_ID — the physical ROWID of the underlying record, useful for row identification in update or drill-down logic.
• ARM_ID — the primary identifier of the record match definition.
• SSN, GIVEN_NAME, SURNAME, BIRTH_DT, ADDRESS, CITY, ZIP, GENDER_NUM, EMAIL_NUM — the person attribute values used as the matching criteria.
• MIN_SCORE_AUTO_FA and MIN_SCORE_RVW_FA — score thresholds governing automatic matching versus manual review for financial aid records.
• MATCH_CODE and MATCH_DESC — the coded value and its description that classify the match configuration.
• ADMN_TERM — the admission term to which the matching rule applies.
• ENABLED_FLAG — indicates whether the matching rule is active.
• The *_MT_TXT 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) — text representations of the match-type or matching tolerance applied per attribute.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

This view is typically queried during diagnostics of ISIR and Profile matching behavior, when validating that the correct thresholds and criteria are configured for the current organization. A representative query lists the active rules for an admission term:

• SELECT arm_id, match_code, match_desc, admn_term, min_score_auto_fa, min_score_rvw_fa, enabled_flag FROM igf_ap_record_match WHERE enabled_flag = 'Y' ORDER BY admn_term;
• SELECT arm_id, ssn, given_name, surname, birth_dt, zip, min_score_auto_fa FROM igf_ap_record_match WHERE admn_term = :term;

Because the view enforces the ORG_ID predicate automatically, queries return only the records for the organization in the current session context. Requests executed outside a properly initialized session may return no rows unless the CLIENT_INFO setting is established.