Results for “loan_type_num”

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

Overview

IGF_SL_LOANS_V is a reporting view in the Oracle E-Business Suite (EBS) IGF — Financial Aid module, a component of the Oracle Student System / Financial Aid product line. The view consolidates student loan award and disbursement data by joining loan records to their parent awards, funds, fund categories, academic calendar instances, person base records, and party (person) records. Its purpose is to present a denormalized, human-readable slice of loan information—combining identifiers, fund attributes, loan amounts, status codes, and student identity—so that reporting, extracts, and downstream integration processes can consume loan data without navigating the full normalized schema.

The ETRM documentation classifies the IGF Financial Aid module as Obsolete, and the provided metadata explicitly notes "Not implemented in this database." This indicates that in the specific database instance documented, the view is not deployed. The view text nevertheless remains available as reference material for installations that did implement it, and for historical analysis of upstream Financial Aid implementations (12.1.1 and 12.2.2). Because the module is obsolete, this view should be treated as legacy; new development should target supported replacements.

Underlying Base Objects

The view is defined over the following base tables and supporting objects:

• IGF_SL_LOANS (alias LAR) — the primary loan record table, supplying LOAN_ID, SEQ_NUM, LOAN_NUMBER, loan period dates, status, and audit columns.
• IGF_AW_AWARD (alias AWDV) — award header, supplying BASE_ID, AWARD_ID, FUND_ID, OFFERED_AMT, and ACCEPTED_AMT.
• IGF_AW_FUND_MAST (alias FMAST) — fund master, supplying FUND_CODE and calendar instance keys.
• IGF_AW_FUND_CAT (alias FCAT) — fund category, supplying FUND_SOURCE, FUND_TYPE, SYS_FUND_TYPE, and FED_FUND_CODE.
• IGS_CA_INST (alias CI) — calendar instance, supplying START_DT, END_DT, and ALTERNATE_CODE.
• IGF_AP_FA_BASE_REC (alias BASE) — the financial aid base record linking to PERSON_ID and calendar instance.
• HZ_PARTIES (alias P) — trading community party, supplying PARTY_NUMBER and PARTY_NAME.
• IGS_PE_ALT_PERS_ID / IGS_PE_PERSON_ID_TYP — an inline subquery (alias PIT) that resolves the student's SSN-type alternate person identifier.

The joins are inner joins on AWARD_ID, FUND_ID, BASE_ID, calendar type/sequence, and FUND_CODE, with an outer join (BASE.PERSON_ID = PIT.PE_PERSON_ID (+)) to the SSN subquery so that loans without an SSN identifier are still returned. A scalar function, IGF_AW_GEN.LOOKUP_DESC, is invoked twice to translate status codes into descriptions.

Key Columns

• LOAN_ID / SEQ_NUM / LOAN_NUMBER — unique loan identity and per-award sequence.
• BASE_ID / AWARD_ID / FUND_ID — keys linking the loan back to its originating award and fund.
• STUDENT_ID / PERSON_NUMBER / FULL_NAME / S_SSN — student identity derived from the base record, party, and SSN subquery.
• OFFERED_AMT / ACCEPTED_AMT — the amounts offered versus accepted on the award.
• LOAN_PER_BEGIN_DATE / LOAN_PER_END_DATE — the loan period.
• LOAN_STATUS / LOAN_CHG_STATUS — raw status codes, paired with their LOOKUP_DESC-resolved descriptions.
• CI_CAL_TYPE / CI_SEQUENCE_NUMBER / CI_START_DT / CI_END_DT — the academic calendar instance covering the award.
• FUND_CODE / FUND_SOURCE / FUND_TYPE / FED_FUND_CODE — funding source classification, including federal aid codes.
• EXTERNAL_LOAN_ID_TXT / LEGACY_RECORD_FLAG — external system reference and legacy indicator.

Common Use Cases and Queries

Typical uses include federal loan reporting, reconciliation of offered versus accepted loan amounts, and student-level aid extracts. The following sample selects active loans for a calendar instance:

SELECT LOAN_ID, STUDENT_ID, FULL_NAME, LOAN_TYPE,
       OFFERED_AMT, ACCEPTED_AMT, LOAN_STATUS
FROM   IGF_SL_LOANS_V
WHERE  CI_ALTERNATE_CODE = :calendar_code
AND    ACTIVE = 'Y';

Because the module is documented as obsolete and not implemented in the reference database, administrators should confirm view availability before relying on it, and migrate any dependent reports to supported objects.