Search Results fund_exp_da




Overview
Explore in AI Chat

Overview

IGFBV_FUNDS is a base view owned by the APPS schema within the IGF (Financial Aid) product module of Oracle E-Business Suite. It is defined over the FMAST base table (the fund master entity) and exposes the full set of details and properties associated with each financial aid fund. In EBS 12.1.1 and 12.2.2, this view functions as the presentation and integration layer for fund definitions, allowing reporting tools, concurrent programs, and custom extensions to query fund attributes through a stable, APPS-owned synonym-less object rather than accessing the underlying FMAST table directly. The view is documented as VALID in the ETRM repository.

A distinguishing characteristic of the view is its use of the "_LA:" (lookup attribute) convention. Rather than returning raw lookup codes, the view text maps enumerated columns such as DISCONTINUE_FUND, ENTITLEMENT, AUTO_PKG, SELF_HELP, and others through IGF_LOOKUPS_VIEW (using lookup types such as IGF_AP_YES_NO, IGF_AW_NEED_METHOD, IGF_AW_ROUND_OFF, and IGF_AWARD_STATUS) to their MEANING values. This means report builders obtain human-readable descriptions directly, without needing to join to the lookup views themselves.

Underlying Base Objects

The documented view text references a single base object, aliased FMAST, which is the fund master table (IGF_FM_FMAST or its equivalent in the IGF schema boundary). Every column projected by IGFBV_FUNDS originates from FMAST; the view performs no joins in the excerpt provided. The lookup decoding described above is embedded as correlated lookup expressions rather than explicit joins in the base definition.

The ETRM metadata for the 12.2.2 release lists no separately documented referenced base objects, so integrators should treat FMAST as the sole authoritative source. Because the view is a thin projection over FMAST, it inherits the table's validation state and any fund-level descriptive flexfield behavior is not included unless explicitly projected.

Key Columns

Common Use Cases and Queries

Typical usage includes fund setup validation, award-year reconciliation, and commitment-versus-disbursement analysis. Because the view already resolves lookup meanings, reports can be written without supplemental lookup joins.

To inspect committed amounts across funds:

SELECT fund_code,
       ci_cal_type,
       ci_sequence_number,
       committed_amt,
       total_committed,
       disbursed_amt,
       total_disbursed,
       accepted_amt,
       remaining_amt
FROM   apps.igfbv_funds
WHERE  committed_amt > 0
ORDER  BY fund_code;

To compare committed against offered and accepted balances per fund-year, replace the WHERE clause with a calendar filter on CI_CAL_TYPE and CI_SEQUENCE_NUMBER. To review control settings, select MIN_AWARD_AMT, MAX_AWARD_AMT, OVER_AWARD_AMT, OVER_AWARD_PERCT, REPLACE_FC, and ALLOW_OVERAWARD alongside FUND_CODE. For integration or interface extracts, the full column list supports a direct SELECT * into staging tables, though explicit column selection is recommended to insulate against future release changes. As with any APPS-owned database object, the view should be referenced with the APPS schema prefix in custom SQL.