Search Results disb_process_date




Overview

IGF_GR_YTD_DISB_ALL is a Financial Aid (IGF) module table in Oracle E-Business Suite that stores year-to-date disbursement data for students receiving financial aid. It serves as the persistent repository for cumulative disbursement activity, capturing origination, acceptance, and payment information tied to a specific award year and academic calendar instance. The table is owned by the IGF schema and is documented as VALID in both EBS 12.1.1 and 12.2.2.

The table is the physical home of records used by federal and institutional financial aid reporting processes, including year-to-date disbursement reporting to external agencies (Common Origination and Disbursement and similar interfaces). It maintains a lifecycle of disbursement flows rather than static reference data, with each row representing a disbursement event keyed by YTDDS_ID.

Under the heuristic Data Vault classification mined from the FK structure, this object is satellite-leaning. In a Data Vault model, this suggests IGF_GR_YTD_DISB_ALL is best treated as a descriptive satellite attached to a hub or link representing the student award, calendar instance, or disbursement business key, rather than a pure hub. The strongest observable link is to IGS_CA_INST_ALL via CI_CAL_TYPE and CI_SEQUENCE_NUMBER.

Key Information Stored

The surrogate primary key is YTDDS_ID, enforced through the index IGF_GR_YTD_DISB_ALL_PK. The ETRM metadata also documents IGF_GR_YTD_DISB_ALL_U1 as a unique index on YTDDS_ID, meaning no separate natural business key is enforced at the index level; the surrogate is the sole documented uniqueness mechanism.

The most significant documented columns include:

Standard audit and concurrency columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID) are present to support traceability.

Common Use Cases and Queries

Typical usage centers on year-to-date disbursement reconciliation, financial aid reporting, and audit of aid delivery. Reporting queries commonly aggregate DISB_ACCPT_AMT by FIN_AWARD_YEAR_NUM, STUDENT_NAME, or DISB_BATCH_ID.

A representative query retrieving YTD totals for a student:

  • SELECT YTDDS_ID, STUDENT_NAME, FIN_AWARD_YEAR_NUM, DISB_DT, DISB_ACCPT_AMT, DB_CR_FLAG FROM IGF.IGF_GR_YTD_DISB_ALL WHERE STUDENT_NAME = :name AND FIN_AWARD_YEAR_NUM = :year AND ORG_ID = :org ORDER BY DISB_DT;
  • Batch-level audit: SELECT DISB_BATCH_ID, SUM(DISB_ACCPT_AMT) FROM IGF.IGF_GR_YTD_DISB_ALL GROUP BY DISB_BATCH_ID;
  • Calendar instance join to enrich academic context: SELECT g.YTDDS_ID, c.CAL_TYPE, g.DISB_DT FROM IGF.IGF_GR_YTD_DISB_ALL g, IGS.IGS_CA_INST_ALL c WHERE g.CI_CAL_TYPE = c.CAL_TYPE AND g.CI_SEQUENCE_NUMBER = c.SEQUENCE_NUMBER;

Because DB_CR_FLAG and DISB_REL_IND affect net totals, reporting logic must account for credit and release rows to avoid double counting.

Related Objects

Documented FK relationships tie this table primarily to academic calendar and financial aid award structures:

  • IGS_CA_INST_ALL — joined via CI_CAL_TYPE and CI_SEQUENCE_NUMBER; supplies academic calendar instance context.
  • Origination and award tables — referenced through ORIGINATION_ID, linking disbursements to their award origin.
  • Disbursement batch processing objects — related through DISB_BATCH_ID for batch-level reconciliation and payment run reports.
  • Multi-org operating unit views — ORG_ID aligns rows to the security profile applied to IGF reports.
  • Student and person reference structures — implied by STUDENT_NAME, CURRENT_SSN_TXT, and STUDENT_BIRTH_DATE for student identity resolution.

Because documented dependency metadata is limited to the calendar instance FK, developers should inspect the IGF schema for additional programmatic dependents (concurrent programs, SQL*Loader control files, and reporting views) before extending or purging rows.