Results for “fa_detail”

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

Overview

IGFFV_ISIR_CORRECTIONS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Oracle Student System / Financial Aid (IGF) product family. It exposes ISIR (Institutional Student Information Record) correction data alongside the identity of the financial aid applicant and the academic calendar instance to which each correction applies. The view functions as a reporting and integration surface for financial aid administrators who must audit, reconcile, or transmit corrections returned from the federal ISIR processing cycle against internally matched applicant records.

The view is created entirely in SQL as a join across five underlying tables, with no PL/SQL logic and no documented procedural dependencies. Its read-only constraint (WITH READ ONLY) prevents DML through the view, reinforcing its intended role as a query-only reporting object. It is commonly joined or referenced by concurrent programs, OBIEE/BI Publisher reports, and custom extracts that need a denormalized, human-readable presentation of correction transactions.

Underlying Base Objects

The view is defined over five base tables. Although the ETRM metadata lists no explicitly documented base objects, the view text names them precisely:

• IGF_AP_ISIR_CORR_ALL (ISIRC) — the driving table holding ISIR correction records, including the SAR field number, original value, corrected value, batch identifier, and correction status.
• IGF_AP_ISIR_MATCHED_ALL (ISIRM) — links a correction to the matched ISIR and, through BASE_ID, to the financial aid applicant base record.
• IGF_AP_FA_BASE_REC_ALL (FA_DETAIL) — the financial aid base record supplying PERSON_ID; this is the object most often associated with the "fa_detail" search term.
• HZ_PARTIES (HP) — the TCA party master providing PARTY_NAME and PARTY_NUMBER.
• IGS_CA_INST_ALL (CI) — the calendar instance supplying ALTERNATE_CODE and DESCRIPTION for the correction's academic period.

The join path is: corrections to matched ISIRs (ISIR_ID), matched ISIRs to the FA base record (BASE_ID), FA base record to HZ_PARTIES (PERSON_ID = PARTY_ID), and corrections to the calendar instance (CI_CAL_TYPE and CI_SEQUENCE_NUMBER).

Key Columns

• PARTY_NAME / PARTY_NUMBER — applicant identity from HZ_PARTIES.
• SAR_FIELD_NUMBER — the federal SAR field being corrected.
• CORRECTION_STATUS — exposed via a descriptive flexfield lookup expression against IGF_LOOKUPS_VIEW (IGF_ISIR_CORR_STATUS) returning the lookup MEANING.
• ORIGINAL_VALUE / CORRECTED_VALUE — the before/after values submitted for the field.
• BATCH_ID — grouping identifier for the correction submission batch.
• ISIRC_ID / ISIR_ID — primary and foreign keys linking to correction and ISIR records.
• CI_CAL_TYPE / CI_SEQUENCE_NUMBER, ALTERNATE_CODE, DESCRIPTION — the academic calendar context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns.
• PERSON_ID — the applicant's party identifier from the financial aid base record.

Common Use Cases and Queries

Typical uses include auditing pending and applied ISIR corrections per applicant, reconciling correction batches before federal transmission, and building student-facing correction histories.

Corrections for a specific applicant:

SELECT party_number, party_name, sar_field_number,
       original_value, corrected_value, correction_status
FROM   apps.igffv_isir_corrections
WHERE  person_id = :p_person_id;

Corrections within an academic period:

SELECT alternate_code, description, correction_status,
       COUNT(*) corr_count
FROM   apps.igffv_isir_corrections
GROUP  BY alternate_code, description, correction_status;

Pending corrections for a batch:

SELECT batch_id, isir_id, sar_field_number,
       original_value, corrected_value
FROM   apps.igffv_isir_corrections
WHERE  batch_id = :p_batch_id
AND    correction_status = 'PENDING';