Search Results fa126_3102439_cs_dp2




Overview
Explore in AI Chat

Overview

APPS.IGF_SL_CL_SETUP_V is a reporting and integration view in the Oracle E-Business Suite Student Systems (Financial Aid) module, more specifically within the Oracle Loans / Student Loan (IGF) schema. It presents configuration (setup) data for student loan "collection" or "cl" setup definitions, joining calendar instance information and recipient detail into a single consumable projection. The view is primarily used by the ETRM (Electronic Technical Reference Manual) and dependent Oracle forms, reports, and OAF pages that need to render the loan setup information with decoded lookup meanings rather than raw codes.

Because it exposes descriptive columns translated through IGF_AW_GEN.LOOKUP_DESC, the view is well suited for read-only reporting, LOV (List of Values) population, and integration extracts where the consumer needs human-readable values for otherwise numeric or coded setup attributes.

Underlying Base Objects

The view is defined over three base objects through an inner join, meaning only setup rows that match both a calendar instance and a recipient are returned:

No additional base objects are documented in the ETRM metadata for this view.

Key Columns

Common Use Cases and Queries

The view is most commonly queried to validate setup and to display decoded hold-release values during loan processing or reconciliation. A typical query retrieving the hold-release meaning for a given setup would be:

SELECT clset_id,
       ci_cal_type,
       ci_sequence_number,
       hold_rel_ind
FROM   apps.igf_sl_cl_setup_v
WHERE  hold_rel_ind = 'Y';

To list all setups with their decoded attributes and recipient context:

SELECT clset_id,
       relationship_cd,
       relationship_cd_desc,
       lookup_desc
FROM   apps.igf_sl_cl_setup_v
WHERE  ci_cal_type = '&cal_type'
AND    ci_sequence_number = &sequence_number;

Because the view performs inner joins across setup, calendar instance, and recipient, queries should account for the fact that unmatched setup rows (for example, missing recipient or calendar instance) are excluded. Reports and integrations relying on this view should therefore treat it as a curated, joined projection rather than a complete extract of IGF_SL_CL_SETUP.