Search Results secondary_efc




Overview
Explore in AI Chat

Overview

APPS.IGF_AP_ISIR_INFO_V is a supplementary Oracle E-Business Suite view owned by the APPS schema, registered under FND Design Data as IGF.IGF_AP_ISIR_INFO_V. It belongs to the Oracle Financial Aid (IGF) product family, specifically the ISIR (Institutional Student Information Record) processing area used by higher-education institutions running Oracle Student System and Financial Aid modules. The view presents ISIR transaction information — including the Expected Family Contribution (EFC) figures reported by the federal processor — in a flattened, form-friendly structure that simplifies coding of Oracle Forms-based maintenance screens.

Oracle classifies this as a supplementary view intended to simplify forms coding. The ETRM documentation carries an explicit warning that Oracle does not recommend querying or altering data through this view, because its definition may change dramatically in subsequent minor or major releases. Despite that caveat, the view is widely used as a read-only reporting and integration surface for ISIR and EFC data, because it joins the base record to its matched ISIR transaction without requiring the caller to reconstruct the join logic.

Underlying Base Objects

The view resolves to two documented base objects in the APPS schema:

  • IGF_AP_FA_BASE_REC — the financial aid base record table holding the applicant-level record identity (BASE_ID) and associated linkage data.
  • IGF_AP_ISIR_MATCHED — the matched ISIR transaction table holding the transaction-level details received from the federal ISIR processor and matched to the base record.

The view joins these objects to present ISIR transaction attributes against the underlying applicant base record. The ETRM metadata notes that IGF_AP_ISIR_INFO_V is not referenced by any other database object, meaning it is a terminal, leaf-level object in the dependency tree — nothing else in the schema depends on it.

Key Columns

  • ISIR_ID (NUMBER 15) — surrogate identifier for the ISIR record surfaced by the view.
  • BASE_ID (NUMBER 15) — foreign key to the financial aid base record; the primary linkage between applicant and ISIR transaction.
  • SSN_NAME_CHANGE, ORIGINAL_SSN, ORIG_NAME_ID — flags and original values for Social Security Number and name changes reported on the ISIR.
  • TRANSACTION_NUM, TRANSACTION_ID — the federal ISIR transaction sequence number and transaction identifier.
  • VERIFICATION_FLAG — indicates whether the ISIR was selected for verification.
  • ISIR_CORR_STATUS (VARCHAR2 30) — correction status of the ISIR record.
  • PRIMARY_EFC (NUMBER 12) and SECONDARY_EFC (NUMBER 12) — the primary and secondary Expected Family Contribution values reported by the federal processor. SECONDARY_EFC is the column users most frequently search for; it is populated when a secondary EFC is computed for the applicant, typically for independent students or in specific dependency/need scenarios.
  • PAYMENT_ISIR — flag relating to payment ISIR handling.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • SYSTEM_RECORD_TYPE (VARCHAR2 30) — classifies the originating record type.

Common Use Cases and Queries

Typical uses include reconciliation of ISIR transaction data with federal output, verification review, and reporting on EFC values for need analysis. Because the view flattens the base-to-transaction join, queries are straightforward.

Retrieve ISIR transactions with both EFC figures:

  • SELECT BASE_ID, TRANSACTION_NUM, PRIMARY_EFC, SECONDARY_EFC, ISIR_CORR_STATUS FROM APPS.IGF_AP_ISIR_INFO_V WHERE SECONDARY_EFC IS NOT NULL;

Locate records flagged for verification:

  • SELECT BASE_ID, TRANSACTION_NUM, VERIFICATION_FLAG, PRIMARY_EFC FROM APPS.IGF_AP_ISIR_INFO_V WHERE VERIFICATION_FLAG = 'Y';

Join to the base record for applicant-level reporting:

  • SELECT v.BASE_ID, v.TRANSACTION_ID, v.PRIMARY_EFC, v.SECONDARY_EFC FROM APPS.IGF_AP_ISIR_INFO_V v, APPS.IGF_AP_FA_BASE_REC b WHERE v.BASE_ID = b.BASE_ID;

Given the documented caution, consumers should treat the view as read-only and validate its definition against the current patch level whenever upgrading between EBS 12.1.1 and 12.2.2.