Search Results loan_status_desc




Overview
Explore in AI Chat

Overview

The view IGF_SL_LOANS_SUM_V (Loans Summary View) belongs to the IGF – Financial Aid product family, a module classified as Obsolete in the Oracle E-Business Suite 12.1.1 and 12.2.2 documentation set. The view consolidates student loan information for financial aid awards, joining loan-level detail from IGF_SL_LOANS with award data, loan origination records, financial aid base records, and person information sourced through IGS_PE_PERSON_BASE_V. Its stated purpose is to present a flattened, reporting-friendly summary of loan activity per award and per person, exposing both student (borrower) and payer/contributor person identifiers and names side by side.

Per the ETRM metadata, this object is not implemented in the database referenced by the documentation, and no base objects are formally documented as referenced. This indicates the view exists as historical metadata inherited from earlier releases (the IGS/IGF Financial Aid schema, later superseded by the Student Aid modules), and should be treated as informational rather than as a supported integration or reporting interface in current 12.1.1/12.2.2 environments.

Underlying Base Objects

Although the metadata lists no formally documented base objects, the embedded view text reveals the following join structure:

  • IGF_SL_LOANS — the primary loan detail table (alias LOANS).
  • IGF_SL_LOR — loan origination records (alias LOR), supplying the originating batch and the payer person.
  • IGF_AW_AWARD — award header data (alias AWD), providing accepted and paid amounts.
  • IGF_AP_FA_BASE_REC — the financial aid base record (alias FABASE), linking calendar type, sequence number, and student person.
  • IGS_PE_PERSON_BASE_V — the person base view, joined twice: once as S_PERSON (student, via FABASE.PERSON_ID) and once as P_PERSON (payer, outer-joined via LOR.P_PERSON_ID).

The outer join on the payer person means loans without an associated payer still return a row, with payer identifiers null. The user's search term, igs_pe_person_base_v, corresponds directly to this dual reference — the view depends on the person base view for both borrower and payer name resolution.

Key Columns

Common Use Cases and Queries

Typical usage would be loan summary reporting per student or per award, reconciliation of accepted versus paid amounts, or batch-level loan tracking. A representative query:

  • SELECT award_id, loan_number_txt, s_full_name, s_person_number, p_full_name, loan_status_desc, loan_accepted_amt, loan_paid_amt FROM igf_sl_loans_sum_v WHERE loan_status_code = 'A' ORDER BY s_full_name;
  • Summarization by student: SELECT s_person_number, s_full_name, SUM(loan_paid_amt) FROM igf_sl_loans_sum_v GROUP BY s_person_number, s_full_name;

Given the Obsolete classification and the absence of a documented implementation, these queries are illustrative of the legacy design and should be validated against any surviving custom schema before reliance in production reporting.