Search Results igf_aw_li_disb_ints

Overview

The IGF_AW_LI_DISB_INTS table resides in the IGF schema and belongs to the Financial Aid (IGF) product family within Oracle E-Business Suite. Its documented purpose is to serve as an Award Disbursements Interface Table for Legacy Data Import. In practical terms, it is a staging and interface structure: external or legacy financial aid systems populate rows into this table, and Oracle EBS concurrent programs subsequently validate, transform, and load those rows into the permanent award disbursement tables.

The table is documented in both ETRM 12.1.1 and 12.2.2, where it is flagged with a VALID status and comprises 31 physical columns. From a modeling perspective, the metadata classifies the object as standalone under the heuristic Data Vault classification. This suggests that, absent mined foreign-key dependencies, the most defensible Data Vault treatment is as an independent structure rather than a hub, link, or satellite tied to other vault entities. Because it is an interface table rather than a transactional master, it is not normally exposed through standard Oracle Forms or self-service UI; it is manipulated programmatically by import processes and by technical staff performing data conversion.

Key Information Stored

The documented physical schema contains 31 columns. The primary key, IGF_AW_LI_DISB_INTS_PK, is a composite surrogate identifier composed of four business-key columns:

• CI_ALTERNATE_CODE — the institution (campus or CI) alternate identifier forming the first PK component.
• PERSON_NUMBER — the student or person identifier, second PK component.
• AWARD_NUMBER_TXT — the textual award number, third PK component, tying the disbursement to a specific award.
• DISBURSEMENT_NUM — the disbursement sequence number, fourth PK component.

Beyond the key, the most operationally significant columns include LD_ALTERNATE_CODE and TP_ALTERNATE_CODE, which carry the location and third-party alternate codes used during legacy conversion. The financial columns OFFERED_AMT, ACCEPTED_AMT, INT_REBATE_AMT, FEE_1_AMT, FEE_2_AMT, FEE_PAID_1_AMT, and FEE_PAID_2_AMT capture the monetary values associated with the offer, acceptance, and fee structure of the disbursement. DISB_DATE, DISB_EXP_DATE, AUTHORIZATION_DATE, and ELIG_STATUS_DATE carry the temporal milestones — scheduled disbursement, expiration, authorization, and eligibility status. TRANS_TYPE_CODE, FEE_CLASS_CODE, ATTENDANCE_TYPE_CODE, and BASE_ATTENDANCE_TYPE_CODE hold the classification codes that determine processing rules, while AFFIRM_FLAG, FORCE_DISB_FLAG, PLANNED_CREDIT_FLAG, and MIN_CREDIT_PTS_NUM encode flags and thresholds governing eligibility and credit-based disbursement behavior. Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are also present.

Common Use Cases and Queries

The primary use case is legacy data conversion: institutions migrating from an external financial aid system stage disbursement records here, then run the Oracle-provided import concurrent program to validate and transfer them. A second use case is reconciliation reporting — comparing staged amounts against the converted disbursement records to confirm load integrity. A third is exception handling: rows that fail validation remain in the interface table for correction and re-import.

A typical staging review query totals the monetary columns by institution and person:

SELECT ci_alternate_code, person_number, award_number_txt,
  SUM(offered_amt) offered, SUM(accepted_amt) accepted
 FROM igf.igf_aw_li_disb_ints
 GROUP BY ci_alternate_code, person_number, award_number_txt;

A useful integrity check confirms that no disbursement is duplicated on the composite key:

SELECT ci_alternate_code, person_number, award_number_txt,
  disbursement_num, COUNT(*)
 FROM igf.igf_aw_li_disb_ints
 GROUP BY ci_alternate_code, person_number, award_number_txt,
  disbursement_num
 HAVING COUNT(*) > 1;

Filtering by AFFIRM_FLAG or FORCE_DISB_FLAG isolates records requiring manual confirmation before downstream processing.

Related Objects

The metadata records no mined foreign-key relationships, consistent with its standalone classification and its role as an interface (staging) table rather than a normalized child of a parent master. Its significant associations are therefore integration-level rather than declarative FK references:

• Award disbursement base tables in the IGF schema — the actual target of the legacy import, joined on award and disbursement identifiers.
• Person and student records (PERSON_NUMBER) — used to resolve the staged person to the EBS person or student identifier.
• Institution/campus configuration (CI_ALTERNATE_CODE) — the financial aid institution entity governing disbursement rules.
• Award master data (AWARD_NUMBER_TXT) — the parent award to which each staged disbursement belongs.
• Third-party and location lookups (TP_ALTERNATE_CODE, LD_ALTERNATE_CODE) — reference data validated during import.
• Code validation tables for TRANS_TYPE_CODE, FEE_CLASS_CODE, and ATTENDANCE_TYPE_CODE — source of valid values checked at load time.
• IGF import concurrent programs and their log tables — executables that read, validate, and clear rows from this interface table.

Because the object is proprietary Oracle schema data, direct DML should be limited to controlled conversion activities, and all modifications should respect the composite primary key to preserve audit and reconciliation integrity.