Results for “igf_ap_person_match”

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

Overview

IGF_AP_PERSON_MATCH is an APPS-owned, VALID database view within the Oracle E-Business Suite Financial Aid (IGF) product family. Its documented purpose is to retrieve the list of ISIR or Profile records that produced a partial match against a person record already present in the system. In the financial aid lifecycle, incoming federal ISIR data and institutional Profile data are compared against existing person records during the matching process; where an exact match cannot be established, the system preserves the candidate record as a partial match for subsequent review. This view exposes those partial-match candidates.

Because it is a view and not a table, IGF_AP_PERSON_MATCH does not store data of its own. It functions as a reporting and inquiry layer over the underlying match table, presenting only those rows that satisfy the current operating unit context. This makes it suitable for concurrent-program extracts, diagnostics, and integration queries where a filtered, session-aware read of partial-match results is required in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view text identifies a single underlying base object: IGF_AP_PERSON_MATCH_ALL, aliased as APM. The view selects the full column list from that table and applies a row-level security predicate. No other referenced base objects are documented in the ETRM metadata.

The predicate is the standard multi-org filter used throughout EBS:

• NVL(APM.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) equals the same expression evaluated for the current session.
• This resolves the operating unit from the CLIENT_INFO session value and compares it to the record's ORG_ID, with -99 used as the fallback when no value is available.

Consequently, the view returns only records belonging to the operating unit of the connected session, while records with a null or unmatched ORG_ID are handled through the nested NVL fallback logic.

Key Columns

• ROW_ID (ROWID): The physical row identifier of the underlying table row, allowing the view result to be related back to the base record.
• APM_ID: Primary identifier of the person-match record; the key linking to related financial aid processing.
• CSS_ID: Identifier associated with the College Scholarship Service (Profile) record in the match.
• SI_ID: Identifier associated with the student/ISIR record involved in the partial match.
• RECORD_TYPE: Indicates whether the matched record originated as an ISIR or a Profile record.
• DATE_RUN: The date the match process was executed, supporting chronological analysis of matching activity.
• CI_CAL_TYPE / CI_SEQUENCE_NUMBER: The calendar type and sequence identifying the academic period/cycle context of the record.
• RECORD_STATUS: The current disposition of the partial-match record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: Standard EBS audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

Typical uses include reviewing partial matches awaiting resolution, auditing match runs by date or cycle, and feeding downstream reconciliation reports. A basic listing is:

• SELECT apm_id, css_id, si_id, record_type, date_run, record_status FROM igf_ap_person_match;
• Filtering by match type: SELECT * FROM igf_ap_person_match WHERE record_type = 'ISIR' ;
• Filtering by processing date: SELECT apm_id, record_status FROM igf_ap_person_match WHERE date_run = :run_date;
• Joining on calendar context: SELECT a.apm_id, a.ci_cal_type, a.ci_sequence_number FROM igf_ap_person_match a WHERE a.ci_cal_type = :cal_type;

All queries automatically inherit the operating-unit security filter, so results are limited to the session's org context.