Search Results disb_exp_dt




Overview

APPS.IGF_SE_AWD_DISB_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as IGF.IGF_SE_AWD_DISB_V. It is part of the IGF product family, which supports student financial aid processing, and specifically exposes award disbursement information for awards managed within that module. Per the ETRM metadata, the view carries a status of VALID and is classified as a "supplementary view used to simplify forms coding," with an explicit Oracle warning that querying or altering data through it is not recommended because its definition may change dramatically in subsequent minor or major releases.

In practice, the view presents a flattened, forms-oriented projection of award disbursement records. It is intended to support the Oracle Forms user interface layer rather than to serve as a stable integration contract. For EBS 12.1.1 and 12.2.2 environments, this distinction matters: developers and report authors who rely on the view inherit some release-coupling risk, whereas direct queries against the underlying base tables are generally more durable.

Underlying Base Objects

The supplied ETRM metadata documents no referenced base objects for this view. This is a documentation gap rather than evidence that the view is standalone — a view of this shape must be defined over one or more base tables, and the presence of standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), a ROW_ID ROWID column, ORG_ID, and the REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE concurrency set is characteristic of a view built over a multi-org transactional base table. Because the base objects are not enumerated in the metadata, consumers should confirm the actual dependency chain in their own environment by querying ALL_DEPENDENCIES and ALL_VIEWS before treating any column-level assumption as authoritative.

Key Columns

Common Use Cases and Queries

Typical uses include disbursement reconciliation reports, forced-disbursement audits, and Forms-driven lookups. A representative query filtering on the searched attribute is:

SELECT award_id, disb_num, disb_status, force_disb, disb_date, disb_net_amt FROM apps.igf_se_award_disb_v WHERE force_disb = 'Y' AND org_id = :p_org_id AND disb_date BETWEEN :p_start AND :p_end;

A second pattern retrieves the disbursement status history for a single award:

SELECT disb_num, disb_status, disb_status_date, elig_status, fund_status, disb_accepted_amt, disb_paid_amt FROM apps.igf_se_award_disb_v WHERE award_id = :p_award_id ORDER BY disb_num;

Given the documented Oracle warning, production reporting should prefer the underlying IGF base tables where their identities are confirmed, reserving this view for Forms-equivalent read behavior.