Search Results revision_code

Overview

IGFFV_AWARD_DISBURSEMENTS is a full view owned by the APPS schema in Oracle E-Business Suite, belonging to the IGF (Financial Aid) product family. It exposes one row per award disbursement, consolidating disbursement amounts, eligibility and status attributes, fund release information, notification data, and coded lookup meanings into a single queryable entity. In the Oracle EBS 12.1.1 and 12.2.2 releases, the object is documented as VALID and serves as the primary reporting and integration surface for financial aid disbursement data, shielding downstream consumers from the multi-table join structure required to assemble a complete disbursement record. The view is defined with the _ALL suffix base tables and therefore respects multi-org (operating unit) security filtering when queried under an appropriately set org context.

Underlying Base Objects

The view text joins six documented base objects. The driving table is IGF_AW_AWD_DISB_ALL (aliased AAD), which holds the disbursement entity itself. IGF_AW_AWARD_ALL (AWD) provides the parent award context, and IGF_AP_FA_BASE_REC_ALL (BASE) supplies the underlying person identifier (BASE.PERSON_ID). Three instances of IGS_CA_INST_ALL are joined — aliased CI, LD, and TP — to resolve calendar instance records: CI for the calendar instance descriptor, LD for the load calendar type/sequence, and TP for the teaching period calendar type/sequence. Note that the stored view text appears to be truncated mid-join in the captured metadata; the documented base object list at the view metadata level is empty, so the join relationships above are derived from the embedded view text rather than from formal dependency documentation. Practitioners should validate the exact predicates in the deployed view via ALL_VIEWS or DBA_DEPENDENCIES on their specific instance.

Key Columns

Disbursement identity and financial columns include AWARD_ID, DISB_NUM, DISB_GROSS_AMT, FEE_1, FEE_2, DISB_NET_AMT, INT_REBATE_AMT, DISB_ACCEPTED_AMT, DISB_PAID_AMT, FEE_PAID_1, and FEE_PAID_2. Status and eligibility attributes include ELIG_STATUS, ELIG_STATUS_DATE, DISB_STATUS, DISB_STATUS_DATE, FUND_STATUS, FUND_STATUS_DATE, and DISB_EXP_DT. Several columns are exposed through inline lookup subqueries against IGF_LOOKUPS_VIEW or IGS_LOOKUP_VALUES, returning decoded MEANING values for TRANS_TYPE, ELIG_STATUS, AFFIRM_FLAG, HOLD_REL_IND, MANUAL_HOLD_IND, LATE_DISB_IND, FUND_DIST_MTHD, PREV_REPORTED_IND, FUND_STATUS, FORCE_DISB, FEE_CLASS, and SHOW_ON_BILL. Party and calendar context is provided via PE.PARTY_NUMBER, PE.PARTY_NAME, and the CI, LD, and TP ALTERNATE_CODE / DESCRIPTION / date range triplets. Of particular relevance to the "revision_code" search term, the view exposes RVSN_ID and the joined RVSN.DESCP from the revision table referenced in the join clause. The column annotated with this meaning is RVSN.DESCP — the descriptive text for a revision code. In the underlying IGF schema, award revisions (for example, revision codes applied to award amounts and disbursement schedules) are maintained in a revision master table keyed by such an ID, and DESCP carries the human-readable revision code description. Report authors who need the revision code value associated with a disbursement should query RVSN_ID for the foreign key and RVSN.DESCP for the revision code description.

Common Use Cases and Queries

Typical uses include student disbursement registers, fund release tracking, reconciliation of gross-to-net disbursement amounts against fee deductions, and extracting revision code context for audit. A sample query retrieving disbursements with their revision code and party details:

• SELECT award_id, disb_num, disb_gross_amt, disb_net_amt, disb_date, rvsn_id, descp, party_number, party_name FROM apps.igffv_award_disbursements WHERE rvsn_id IS NOT NULL;
• SELECT disb_status, COUNT(*) FROM apps.igffv_award_disbursements GROUP BY disb_status;
• SELECT award_id, disb_num, disb_net_amt, fund_status, fund_release_date FROM apps.igffv_award_disbursements WHERE fund_status_dat

(The preceding query is illustrative; complete the predicate per requirement, e.g. filtering on fund_release_date ranges.) Because the view carries the _ALL base tables, always initialize the org context (for example via fnd_global.apps_initialize or the MO: Operating Unit profile) before querying to avoid cross-operating-unit data leakage or ORA-01403 style empty results.