Search Results base_id




Overview
Explore in AI Chat

Overview

IGF_SL_COD_LOANKEY_V is a database view in the Oracle E-Business Suite Financial Aid module (IGF), historically associated with the Student Loan (SL) processing functionality. The product area in which this object resides is flagged as obsolete in the ETRM 12.2.2 metadata, and the view is documented as "not implemented in this database." It is therefore a legacy or reference-only object that appears in documentation and metadata catalogs but should not be relied upon in a functioning 12.1.1 or 12.2.2 environment.

The view presents Loan Key level tags, meaning it consolidates attribute values that are associated with a specific loan key identifier used to track and group student loan records. In Oracle EBS reporting and integration terms, such a view would serve as a denormalized read layer over the loan origination data, exposing fields needed for downstream printing, disclosure generation, and federal reporting extracts rather than for transactional data entry.

Underlying Base Objects

According to the documented view text, IGF_SL_COD_LOANKEY_V is defined over a single base table or object named IGF_SL_LOR_LOC_ALL. The ETRM metadata for the view itself lists no referenced base objects, but the view SQL clearly selects from IGF_SL_LOR_LOC_ALL. The "LOR" and "LOC" segments suggest a Loan Origination Record or Letter of Credit-style source structure, and the "_ALL" suffix typically denotes an Oracle multi-org or business-group secured object.

The SELECT list is wrapped in a GROUP BY that repeats every selected expression except the TO_CHAR date conversions. This is a distinctive construction: because the underlying columns are already unique at the Loan Key level, the GROUP BY functions as a de-duplication mechanism, collapsing multiple rows into a single Loan Key level tag record. There are no joins to other tables in the documented definition, so the view is a projection and de-duplication of IGF_SL_LOR_LOC_ALL rather than a multi-table consolidation.

Key Columns

The view exposes fifteen columns. Several are text identifiers used as keys, and several are dates or numeric percentages.

Common Use Cases and Queries

Because the view is documented as not implemented, any practical use is limited to historical reference, migration analysis, or reverse-engineering for custom reporting. A typical query retrieves Loan Key level tags by base identifier, which is the pattern implied by the "base_id" search:

SELECT base_id, loan_key_num, document_id_txt, rep_entity_id_txt, atd_entity_id_txt, orig_fee_perct, grade_level_code FROM igf_sl_cod_loankey_v WHERE base_id = :p_base_id;

A second common pattern filters by loan period or academic year to assemble records for disclosure and promissory note generation, selecting the print indicators and rebate percentages alongside the identifying keys. Administrators evaluating whether the view still exists should query ALL_VIEWS and ALL_VIEW_COLUMNS for the object name and verify whether IGF_SL_LOR_LOC_ALL is present. If neither exists, the object has been fully retired and must not be referenced in new code, concurrent programs, or integration mappings.