Search Results alt_loan_code_desc

Overview

The view IGF_AW_FUND_CAT_V belongs to the IGF — Financial Aid product family, a module now documented as obsolete in Oracle EBS Release 12.1.1 and 12.2.2. Its stated purpose is to present "the different funds" maintained within the financial aid fund catalog, resolving coded lookup values into human-readable descriptions so that the output can be consumed directly by reports, concurrent programs, and integration extracts.

The view is essentially a denormalized, presentation-layer representation of the fund catalog. Rather than exposing raw lookup codes, it joins the fund catalog to the fund type table and to multiple lookup views, returning alongside each code its decoded meaning. The user's search term igf_aw_fed_fund corresponds directly to one of the lookup types referenced in the view definition: the federal fund code is resolved against the lookup set IGF_AW_FED_FUND, producing the column FED_FUND_CODE_DESC. This makes IGF_AW_FUND_CAT_V the natural access point for any inquiry involving the federal fund classification of an award fund.

Because it is a view, no physical storage is allocated to it, and the ETRM metadata records that it is "not implemented in this database" — meaning it is a template definition carried in the data model documentation rather than an object physically deployed in the source instance.

Underlying Base Objects

The documented base objects are not individually registered in the ETRM metadata, but the view SQL itself identifies the complete set of referenced objects:

• IGF_AW_FUND_CAT FCAT — the driving table, containing the fund catalog rows (fund code, description, fund type, source, federal fund code, active flag, audit columns, and the FCAT_ID primary key).
• IGF_AW_FUND_TYPE FT — supplies the descriptive text for the internal fund type, joined on FCAT.FUND_TYPE = FT.FUND_TYPE.
• IGF_LOOKUPS_VIEW FNDS1 — resolves SYS_FUND_TYPE against lookup type IGF_AW_SYS_FUND_TYPE.
• IGF_LOOKUPS_VIEW FNDS2 — resolves FUND_SOURCE against lookup type IGF_AW_FUND_SOURCE.
• IGF_LOOKUPS_VIEW FNDS3 — resolves FED_FUND_CODE against lookup type IGF_AW_FED_FUND.

The IGF_LOOKUPS_VIEW is a shared lookup abstraction used throughout the IGF schema; each alias filters on a distinct LOOKUP_TYPE, so three independent joins are required to decode the three coded attributes. The function IGF_AW_GEN.LOOKUP_DESC is additionally invoked to decode the alternate loan code.

Key Columns

• ROW_ID, FCAT_ID — surrogate identifiers for the fund catalog record.
• FUND_CODE, DESCRIPTION — the operational fund identifier and its description.
• FUND_TYPE, FUND_TYPE_DESC — the internal fund type code and its description from IGF_AW_FUND_TYPE.
• SYS_FUND_TYPE, SYS_FUND_TYPE_DESC — system-level fund classification, decoded from IGF_AW_SYS_FUND_TYPE.
• FUND_SOURCE, FUND_SOURCE_DESC — the origin of the fund (federal, institutional, private, and similar), decoded from IGF_AW_FUND_SOURCE.
• FED_FUND_CODE, FED_FUND_CODE_DESC — the federal fund designation and its decoded meaning, resolved via the IGF_AW_FED_FUND lookup type.
• ACTIVE — indicates whether the fund is currently enabled for use.
• ALT_LOAN_CODE, ALT_REL_CODE, ALT_LOAN_CODE_DESC — alternate loan and release codes, with the loan code description returned by the IGF_AW_GEN.LOOKUP_DESC function.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried to populate fund selection lists, validate federal fund mappings, and drive federal reporting extracts. A representative listing of all active funds with decoded attributes follows:

SELECT fund_code, description, fund_type_desc, sys_fund_type_desc,
       fund_source_desc, fed_fund_code_desc
  FROM igf_aw_fund_cat_v
 WHERE active = 'Y'
 ORDER BY fund_code;

To isolate funds tied to a specific federal fund classification — the scenario implied by the igf_aw_fed_fund search — the view can be filtered on FED_FUND_CODE_DESC directly, avoiding a manual join to the lookup infrastructure.

Because the view already resolves lookup codes, it is well suited to integration extracts that must emit descriptive values rather than internal codes, and to reconciliation queries comparing the fund catalog against federal fund definitions. Callers should note that the object is documented as obsolete and not implemented in the reference database, so availability must be verified against the target instance before use.