Results for “igf_aw_fund_type_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGF_AW_FUND_TYPE_ALL is a seed data table in the Oracle E-Business Suite Financial Aid (IGF) module. It stores the canonical list of fund types used throughout the financial aid awarding and disbursement process. Each row represents a distinct category of aid funding — for example, federal grants, institutional scholarships, or loan programs — that can later be associated with fund categories, awards, and disbursement records.

The table resides in the IGF schema and is classified as seed data, meaning it is typically populated at implementation time and maintained as reference rather than transactional data. It is registered under both release 12.1.1 and 12.2.2 with a VALID status. In Data Vault terms, the heuristic classification of this object is hub-leaning: the table anchors a stable, uniquely identified business concept (the fund type) and is referenced by downstream tables, which matches the role of a hub. This classification should be treated as a modeling suggestion only; the object is physically implemented as a conventional EBS table with standard audit columns.

Key Information Stored

The documented physical schema exposes ten columns. The most significant are:

• FT_ID — The surrogate primary key, enforced by the IGF_AW_FUND_TYPE_ALL_PK constraint and also uniquely indexed by IGF_AW_FUND_TYPE_ALL_U1. This is the internal identifier used for referential joins within the application.
• FUND_TYPE — The business-facing fund type code. Together with ORG_ID it forms a business-key candidate (unique index IGF_AW_FUND_TYPE_ALL_U2) and is the value that external tables such as IGF_AW_FUND_CAT_ALL actually store as their foreign key.
• DESCRIPTION — A descriptive name for the fund type presented to users in list-of-values and reporting contexts.
• ACTIVE — A flag indicating whether the fund type is currently enabled for use in new awards and transactions.
• ORG_ID — The operating unit (multi-org) identifier, which partitions fund types by organization and prevents cross-organization visibility. Its inclusion in the unique index means the same FUND_TYPE code may exist independently for different operating units.

The remaining columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are the standard EBS who-column audit trail, recording who created and last modified each row and when. These are maintained automatically by the application and are rarely queried directly, though they are useful for data lineage and auditing exercises.

Common Use Cases and Queries

Because this is seed data, most access is read-only lookup and validation work. Typical scenarios include validating award records against an active fund type, generating pick lists for setup forms, and reconciling fund type definitions across operating units during multi-org implementations.

A basic lookup of active fund types for a given operating unit:

• SELECT fund_type, description FROM igf.igf_aw_fund_type_all WHERE active = 'Y' AND org_id = :org_id ORDER BY fund_type;

Resolving a fund type awarded to a fund category (joining back from the dependent table) requires matching on both FUND_TYPE and ORG_ID, since the foreign key is composite:

• SELECT t.fund_type, t.description, c.fund_cat_code FROM igf.igf_aw_fund_type_all t, igf.igf_aw_fund_cat_all c WHERE c.fund_type = t.fund_type AND c.org_id = t.org_id;

Reporting use cases include auditing unused fund types (rows with no corresponding fund category or award), verifying that descriptions conform to institutional naming standards, and producing a cross-operating-unit inventory of active versus inactive codes.

Related Objects

The most significant related object is IGF_AW_FUND_CAT_ALL, which carries a foreign key on (FUND_TYPE, ORG_ID) pointing back to this table. This confirms that fund categories are a subordinate, dependent concept — each category must reference an existing fund type in the same operating unit. Because FUND_TYPE and ORG_ID together form the business key rather than FT_ID alone, join logic should generally use the composite columns.

Other objects that logically depend on this table include the award and disbursement tables within the IGF module that consume fund types during the packaging and disbursement lifecycles, the fund type setup form and associated list-of-values definitions used in the Financial Aid administrative responsibility, and any concurrent programs or reports that enumerate fund types for a given operating unit. The primary key constraint IGF_AW_FUND_TYPE_ALL_PK and the unique indexes U1 and U2 provide the integrity guarantees that these dependent objects rely upon.