Results for “igf_ap_person_match_all”

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

Overview

The IGF_AP_PERSON_MATCH_ALL table is a core data object within the Oracle E-Business Suite Financial Aid (IGF) module. It resides in the IGF schema and stores the master list of all ISIR (Institutional Student Information Record) or Profile records that registered a partial match against a person record already present in the system. In the financial aid lifecycle, incoming federal and institutional application data must be matched to existing student or applicant person records before awards, verification, and disbursement processing can proceed. This table captures the outcomes of that matching process specifically for partial matches, providing a staging and audit layer between raw application import and confirmed person linkage.

Based on the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a hub-leaning entity. The classification is a modeling suggestion rather than a documented design assertion: the table holds a stable, uniquely identified business key (APM_ID) that other tables reference, which is the characteristic signature of a hub. Its downstream dependency — IGF_AP_MATCH_DETAILS referencing APM_ID — supports this interpretation, with the detail table behaving as a dependent satellite-like structure that enriches the match header with granular matching attributes.

The table is present and valid in both Oracle EBS 12.1.1 and 12.2.2, and the documented physical schema includes 14 columns.

Key Information Stored

The table is anchored by a surrogate primary key and several business-key candidates exposed through unique indexes. The most significant columns are:

• APM_ID — The surrogate primary key (constraint IGF_AP_PERSON_MATCH_PK) and also the target of unique index IGF_AP_PERSON_MATCH_U1. It uniquely identifies each partial-match record and is the join column referenced by IGF_AP_MATCH_DETAILS.
• SI_ID — A business-key candidate backed by unique index IGF_AP_PERSON_MATCH_U2, typically tying the record to the source application or student identifier.
• CSS_ID — A business-key candidate backed by unique index IGF_AP_PERSON_MATCH_U3, associated with the College Scholarship Service identifier for Profile records.
• ORG_ID — The operating unit or organization that owns the record, enabling multi-org data segregation and reporting.
• RECORD_TYPE — Distinguishes the nature of the incoming record, such as ISIR versus Profile.
• DATE_RUN — The date the person-matching process executed, critical for audit and reprocessing.
• CI_CAL_TYPE and CI_SEQUENCE_NUMBER — Identify the calendar type and sequence associated with the aid cycle or processing period.
• RECORD_STATUS — The current disposition of the partial-match record within the workflow.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO-column audit attributes capturing record provenance and change history.

Common Use Cases and Queries

Financial aid administrators and technical teams rely on this table to review unresolved partial matches, drive manual person-linkage resolution, and report on matching volumes per processing run. A typical query joins the header to its details to inspect the reasons and candidates surfaced during matching:

• Partial-match worklist: SELECT m.APM_ID, m.RECORD_TYPE, m.DATE_RUN, m.RECORD_STATUS FROM IGF_AP_PERSON_MATCH_ALL m WHERE m.ORG_ID = :org AND m.RECORD_STATUS = :status ORDER BY m.DATE_RUN;
• Header-to-detail drill-down: SELECT d.* FROM IGF_AP_MATCH_DETAILS d, IGF_AP_PERSON_MATCH_ALL m WHERE d.APM_ID = m.APM_ID AND m.APM_ID = :apm_id;
• Volume trending by run date: aggregate COUNT of APM_ID grouped by DATE_RUN, RECORD_TYPE, and ORG_ID to monitor matching throughput.

Because the table preserves ORG_ID and audit columns, it is also well suited to multi-organization reporting and reconciliation against the originating ISIR or Profile import batches.

Related Objects

The relationship data documents one explicit foreign key relationship, which is the principal dependency for this object:

• IGF_AP_MATCH_DETAILS — References this table through the column IGF_AP_MATCH_DETAILS.APM_ID, forming the primary parent-child relationship. Each match header in IGF_AP_PERSON_MATCH_ALL can have one or more detail rows recording the specifics of the partial match.

The unique indexes IGF_AP_PERSON_MATCH_U1 (APM_ID), IGF_AP_PERSON_MATCH_U2 (SI_ID), and IGF_AP_PERSON_MATCH_U3 (CSS_ID) define the business-key candidates that downstream matching and reconciliation processes use to resolve records against person data. Together with the detail table, these constraints make IGF_AP_PERSON_MATCH_ALL the central hub for partial person-match tracking in Financial Aid.