Results for “igf_ap_fa_con_v”

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

Overview

IGF_AP_FA_CON_V is a database view belonging to the IGF – Financial Aid product family within Oracle E-Business Suite. Its documented purpose is to expose "financial aid context details" — that is, the bundle of attributes that describe a financial aid applicant's identity, institutional context, and processing state at a given point in the packaging lifecycle. The view is classified as obsolete in the ETRM metadata, and it is explicitly noted as "not implemented in this database," which indicates that the underlying object may not exist in every 12.1.1 or 12.2.2 instance. Where present, it would have served as a reporting and integration surface for downstream financial aid processes, allowing external systems and Oracle Reports to read a flattened, denormalized snapshot of applicant context without joining numerous base tables directly.

Underlying Base Objects

The ETRM metadata for this view does not enumerate referenced base objects, and no documented dependencies are recorded. Inspection of the view text reveals that it is constructed over several financial aid tables, the most prominent being FA (the primary financial aid applicant/record table, aliased FA), which supplies ROWID as ROW_ID, BASE_ID, PERSON_ID, and the calendar instance keys CI_CAL_TYPE and CI_SEQUENCE_NUMBER. Person attributes are drawn from PE (person) and PIT (person identification), while calendar attributes come from CA (calendar). A separate PI alias supplies ISIR-related fields such as ORIGINAL_SSN, ORIG_NAME_ID, TRANSACTION_NUM, and DEPENDENCY_STATUS, and HZP supplies the deceased indicator. The view also invokes the PL/SQL function IGS_EN_GEN_003.ENRP_GET_ENCMBRD_IND to derive the ENCUMBERED_IND flag, reflecting a dependency on the IGF enrollment/encumbrance API rather than a base table alone.

Key Columns

The view exposes a broad column set organized around applicant identity, processing status, and packaging context.

• Identity and person: ROW_ID, BASE_ID, PERSON_ID, SSN, PERSON_LAST_NAME, PERSON_FIRST_NAME, FULL_NAME, PERSON_NUMBER, and HZP.DECEASED_IND.
• Calendar context: CI_CAL_TYPE, CI_SEQUENCE_NUMBER, CI_ALTERNATE_CODE, START_DT, and END_DT.
• Need analysis and verification: COA_F, COA_I, COA_FIXED, COA_PELL, COA_CODE_F, COA_CODE_I, COA_PENDING, PROF_JUDGEMENT_FLG, and NSLDS_DATA_OVERRIDE_FLG. The user's search term "coa_i" maps directly to the COA_I column, the institutional cost-of-attendance component.
• ISIR and verification status: ISIR_STATUS, ISIR_STATUS_DATE, ISIR_CORR_STATUS, ISIR_CORR_STATUS_DATE, EDE_CORRECTION_BATCH_ID, FED_VERIF_STATUS, INST_VERIF_STATUS, and ACTIVE_ISIR.
• Packaging and notification: PACKAGING_STATUS, PACKAGING_HOLD, NOTIFICATION_STATUS, TOTAL_PACKAGE_OFFERED, and TOTAL_PACKAGE_ACCEPTED.
• Structured segments: ADMSTRUCT_ID with ADMSEGMENT_1 through ADMSEGMENT_20, and PACKSTRUCT_ID with PACKSEGMENT_1 through PACKSEGMENT_16, providing extensible attribute slots.

Common Use Cases and Queries

Because the view is marked obsolete and not implemented, practical usage is largely historical or migration-oriented. Typical scenarios include reconstructing applicant context for reporting, auditing cost-of-attendance values such as COA_I, and extracting verification and packaging status for reconciliation. A representative query follows:

SELECT base_id, person_id, full_name, coa_f, coa_i, coa_pell, isir_status, packaging_status FROM igf_ap_fa_con_v WHERE org_id = :p_org_id AND packaging_status IS NOT NULL ORDER BY full_name;

Analysts migrating off the view should map each column to its current 12.1.1 or 12.2.2 replacement table, since direct dependencies are undocumented and the object may be absent from the schema entirely.