Search Results fee_1




Overview
Explore in AI Chat

Overview

The view IGF_SL_AWD_DISB_LOC belongs to the IGF – Financial Aid product family within Oracle E-Business Suite. In the ETRM metadata, IGF is flagged as Obsolete, and the object itself is documented as not implemented in this database. This designation is significant: the view exists in the historical data model and appears in reference documentation, but it is not deployed as a runtime database object in the environments covered by the ETRM repository. Consequently, the view should be understood as a legacy artifact rather than an active reporting or integration surface.

Conceptually, the view exposes award disbursement records at the location level. It is the location-aware counterpart to the base disbursement table, presenting one row per disbursement (identified by award and disbursement number) with the associated amounts, fees, dates, and audit columns. Its likely historical role was to support institution- and location-scoped querying of student financial aid disbursements — the kind of reporting consumed by financial aid administrators and downstream integrations. The _LOC suffix and the presence of ORG_ID indicate the view was intended to filter records based on the operating unit (multi-org) context in effect for the session.

Underlying Base Objects

The view is defined over a single base object: IGF_SL_AWD_DISB_LOC_ALL. The documented view text selects explicitly named columns from this table and does not introduce any joins, unions, or derived subqueries. The projection is therefore a straight column mapping, with one computed exception: ROW_ID is populated from AWDL.ROWID, exposing the physical row identifier of the underlying record.

The only transformation applied is a multi-org security predicate in the WHERE clause. The view compares the ORG_ID column to the operating unit value derived from USERENV('CLIENT_INFO'). The expression extracts the first ten characters of the client information string, converting it to a number, and handles the case where the string begins with a space by returning NULL. Both sides of the comparison are wrapped in NVL(..., -99), so records lacking an operating unit (NULL) are matched against a session context that also lacks one. This is a standard Oracle multi-org pattern and confirms that the view was designed to enforce operating unit isolation for location-based disbursement data.

Key Columns

Common Use Cases and Queries

Because the object is documented as obsolete and not implemented, any query should be treated as reference or migration-oriented rather than as production reporting code. A typical reconstruction of a gross-versus-net disbursement report would resemble the following, executed within an operating unit session so that the multi-org predicate resolves correctly:

  • Listing disbursements for an award:
    SELECT disb_num, disb_gross_amt, fee_1, fee_2, disb_net_amt, disb_date FROM igf_sl_awd_disb_loc WHERE award_id = :award_id ORDER BY disb_num;
  • Summarizing gross disbursements by award:
    SELECT award_id, SUM(disb_gross_amt) gross_total, SUM(disb_net_amt) net_total FROM igf_sl_awd_disb_loc GROUP BY award_id;
  • Identifying unreleased holds:
    SELECT award_id, disb_num, disb_gross_amt, hold_rel_ind FROM igf_sl_awd_disb_loc WHERE hold_rel_ind = 'N';

In migration or recovery scenarios, developers frequently query the base table IGF_SL_AWD_DISB_LOC_ALL directly, since the view may not exist in a given environment. In all cases, verifying object existence and consulting the appropriate ETRM release documentation before relying on this view is recommended.