Search Results city_match




Overview
Explore in AI Chat

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

Overview

The view IGF_AP_PERSON_MATCH_V belongs to the IGF — Financial Aid product family within Oracle E-Business Suite, a module documented as obsolete in release 12.2.2. Despite its obsolete status, the view is still catalogued in the ETRM repository, which confirms the historical role it played in the Financial Aid person-matching subsystem. Its purpose was to present a consolidated, review-oriented result set combining prospective applicant person matches with the detail-level match attributes generated by Oracle's person-matching logic.

The view is not a base table but a denormalized join construct, intended primarily for reporting and downstream integration. It exposes identity match outcomes (SSN, name, date of birth, address, city, and ZIP) alongside record status, allowing functional users and technical developers to identify person records requiring manual review. The object documentation explicitly states that the view was not implemented in the reference database, and no base objects are formally documented in the ETRM metadata, meaning its definition must be read directly from the embedded view text.

Underlying Base Objects

The view is defined over three referenced base objects, as shown in its view text:

The join condition is strictly on APM.APM_ID = AMD.APM_ID and PE.PARTY_ID = AMD.PERSON_ID, with an added filter restricting output to records where APM.RECORD_STATUS = 'REVIEW'. This means only match runs awaiting human adjudication are returned by the view.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing person-match runs by date, prioritising high-confidence duplicates, and exporting review queues to downstream systems. A representative query filtering on the searched attribute DATE_RUN would be:

SELECT person_id, person_number, name, match_score, date_run
FROM igf_ap_person_match_v
WHERE TRUNC(date_run) = TRUNC(SYSDATE);

Additional scenarios include sorting by MATCH_SCORE descending to surface the strongest candidates, or filtering on individual match flags (for example, WHERE ssn_match = 'Y') to isolate specific duplicate patterns. Because the view is filtered to RECORD_STATUS = 'REVIEW', it is unsuitable for historical or closed match reporting.