Search Results award_number_txt




Overview

The IGF_AW_LI_HOLD_INTS table is a critical interface table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Grants and Financial Aid (IGF) module. Its primary role is to serve as a staging area for the "Legacy - Award and Disbursement Data Import Process." This process facilitates the bulk import of historical or external data related to financial aid award disbursement holds into the core EBS transactional tables. The table is designated as a BUSINESS_ENTITY under the IGF_AWARD category, confirming its central role in managing award lifecycle data. As an interface table residing in the APPS_TS_INTERFACE tablespace, it is designed for temporary data staging before validation and migration, ensuring data integrity in the production environment.

Key Information Stored

The table stores the necessary attributes to uniquely identify a financial aid award disbursement and associate a hold action with it. The key columns form a composite primary key (IGF_AW_LI_HOLD_INTS_PK) and include CI_ALTERNATE_CODE (Award Year), PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM, and HOLD_CODE. This structure allows for multiple holds on a single disbursement. The DISBURSEMENT_NUM column, which was the focus of the user's search, is a mandatory numeric field that identifies the specific disbursement installment of an award to which the hold applies. Other significant columns track the hold lifecycle: HOLD_DATE and RELEASE_DATE record the action timestamps, while RELEASE_REASON_TXT provides context for a hold's removal. Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, etc.) are present for auditing.

Common Use Cases and Queries

The predominant use case is the execution of the legacy data import process, where data is inserted into this table via SQL*Loader, custom scripts, or external system feeds before being processed by concurrent programs. A common reporting or validation query involves checking for active holds on specific disbursements. For example, to find all unreleased holds for a given award and disbursement number, one might use:

SELECT PERSON_NUMBER, HOLD_CODE, HOLD_DATE FROM IGF.IGF_AW_LI_HOLD_INTS WHERE AWARD_NUMBER_TXT = '&AWARD_NUM' AND DISBURSEMENT_NUM = &DISB_NUM AND RELEASE_DATE IS NULL;

Another typical operation is identifying all imported records pending processing by checking for those not yet transferred to base tables, often indicated by a status flag in a related control table or by the presence of data in this interface table after an import job has run.

Related Objects

Based on the provided metadata, the IGF_AW_LI_HOLD_INTS table has a defined unique index but no explicitly documented foreign key relationships within the excerpt. The dependency information states it "does not reference any database object" and is referenced by others. Its primary relationship is functional rather than declarative; it serves as the direct source for the award disbursement hold import process. This process likely populates core transactional tables such as IGF_AW_DISB_HOLDS or related award disbursement entities. The table's columns (CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM) are designed to join with key award and disbursement master tables in the IGF schema, like IGF_AW_AWARD and IGF_AW_DISB, to validate incoming interface records during the import.