Search Results loan_origination_status_date




Overview
Explore in AI Chat

Overview

IGFBV_PERKINS_LOANS is a Business Intelligence System (BIS) view owned by the APPS schema within the Oracle E-Business Suite Financial Aid module. It functions as the base view for the entity that holds Perkins Loans, exposing loan-level detail in a denormalized, reporting-friendly format. The view is registered under FND Design Data as IGF.IGFBV_PERKINS_LOANS and carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2.

Because it is a BIS view rather than a transactional table, IGFBV_PERKINS_LOANS is intended primarily for operational reporting, extract generation, and downstream integration. Third-party financial aid systems, data warehouses, and institutional reporting tools can consume its columns directly without reconstructing complex joins across the underlying award, fund, and base-record tables. The view preserves standard WHO audit columns, allowing change-tracking across load cycles.

Underlying Base Objects

The view is defined over, and depends on, the following APPS objects:

  • IGF_AP_FA_BASE_REC_ALL — the financial aid base record, supplying the student-level identity and record linkage (BASE_ID, PERSON_ID).
  • IGF_AW_AWARD_ALL — the award header, contributing award-level context such as calendar year sequencing.
  • IGF_AW_FUND_CAT_ — the fund category definition, providing classification for the loan funding source.

These dependencies indicate that IGFBV_PERKINS_LOANS consolidates award and fund information against the base financial aid record, projecting loan-specific attributes such as loan number, period, amount, and status. Users should treat the view as read-only and reference the base tables for any transactional correction.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing active Perkins Loans for a given award calendar type and year, reconciling accepted loan amounts against disbursements, and producing extracts for reporting or audit. Users searching for "award_calendar_type" will generally filter or group by AWARD_CALENDAR_TYPE alongside AWARD_YEAR_SEQUENCE_NUMBER.

Example query listing active loans by award calendar:

  • SELECT loan_number, award_calendar_type, award_year_sequence_number, loan_amount, loan_record_status FROM apps.igfbv_perkins_loans;

Example query restricting to a specific calendar type and person:

  • SELECT loan_number, loan_period_begin_date, loan_period_end_date, loan_amount FROM apps.igfbv_perkins_loans WHERE award_calendar_type = :p_calendar_type AND person_id = :p_person_id;

Because the view abstracts the joins across the award and fund tables, these queries resolve against the underlying base objects without exposing the user to their complexity.