Search Results igf_sl_pnote_print_ind

Overview

IGF_SL_DL_SETUP_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Financial Aid module, owned by the APPS schema. It consolidates the student loan delivery setup configuration, exposing a single denormalized record for each delivery-setup row defined in the underlying base table. The view joins the delivery setup data to the academic calendar instance to resolve relevant term dates and codes, and it decorates coded columns with descriptive text by calling the IGF_AW_GEN.LOOKUP_DESC function for several lookup types, including IGF_SL_PNOTE_PRINT_IND, IGF_SL_DISCLOSURE_PRINT_IND, IGF_SL_DL_VERSION, IGF_SL_RESP_OPTIONS, and IGF_SL_FUNDING_METHODS. Because these decode operations are performed within the view definition, consumers receive human-readable descriptions alongside the stored code values without needing to reconstruct the lookup joins themselves.

The view is particularly relevant to reporting on federal Direct Loan (DL) setups, where the DL_VERSION column and its companion DL_VERSION_DESC are frequently referenced. Users searching for "igf_sl_dl_version" are typically seeking the loan-version code assigned to a delivery setup or its decoded description; this view provides both. It is read-only and intended for SELECT access by reporting tools, concurrent programs, and integration interfaces rather than for direct transactional updates.

Underlying Base Objects

The view is defined over two documented base objects:

• IGF_SL_DL_SETUP — the primary base table (aliased as DLSET) that stores delivery-setup attributes, including DL version, funding method, note-print indicators, disclosure and interview requirements, and audit columns.
• IGS_CA_INST — the academic calendar instance table (aliased as CI) that supplies calendar type, sequence number, start date, end date, and alternate code.

The join is performed on CI_CAL_TYPE = CI.CAL_TYPE and CI_SEQUENCE_NUMBER = CI.SEQUENCE_NUMBER, tying each delivery setup to its corresponding calendar instance. This relationship allows term-level dates and identifiers to be reported together with DL setup rules. The view exposes ROW_ID and DLSET_ID as the primary identifiers from IGF_SL_DL_SETUP, and it also surfaces the standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Key Columns

• ROW_ID / DLSET_ID — surrogate and primary keys for the delivery setup record.
• CI_CAL_TYPE, CI_SEQUENCE_NUMBER, CI_START_DT, CI_END_DT, CI_ALTERNATE_CODE — calendar instance identifiers and term dates.
• DL_VERSION / DL_VERSION_DESC — the loan version code stored on the setup and its decoded description via the IGF_SL_DL_VERSION lookup.
• FUNDING_METHOD and its decoded description (IGF_SL_FUNDING_METHODS) — the funding method applied to the setup.
• ORIG_FEE_PERCT_STAFFORD, ORIG_FEE_PERCT_PLUS, INT_REBATE — origination fee percentages and interest rebate values.
• PNOTE_PRINT_IND / PNOTE_PRINT_IND_DESC, PNOTE_PRINT_COPIES — promissory note print indicator, its description, and copy count.
• DISCLOSURE_PRINT_IND / DISCLOSURE_PRINT_DESC, ACC_NOTE_FOR_DISB, AFFIRMATION_REQD, INTERVIEW_REQD — disclosure, note-for-disbursement, affirmation, and interview requirement flags.
• SPECIAL_SCHOOL, RESPONSE_OPTION_CODE — special school flag and the response option code (decoded via IGF_SL_RESP_OPTIONS).

Common Use Cases and Queries

Typical uses include auditing DL setup configurations, validating promissory note and disclosure print settings per term, and extracting setup data for downstream reporting or interfaces. A representative query filtering on the loan version is:

• SELECT dlset_id, dl_version, dl_version_desc, funding_method, ci_start_dt FROM apps.igf_sl_dl_setup_v WHERE dl_version = :p_version;
• SELECT dlset_id, ci_cal_type, ci_sequence_number, pnote_print_ind_desc, disclosure_print_desc FROM apps.igf_sl_dl_setup_v WHERE special_school = 'Y';
• SELECT dlset_id, orig_fee_perct_stafford, orig_fee_perct_plus, int_rebate FROM apps.igf_sl_dl_setup_v ORDER BY creation_date DESC;

All queries should reference the view through the APPS schema or an appropriate synonym and rely on the decoded columns to avoid reproducing lookup logic.