Search Results disburse_verification_hold

Overview

The IGF_AP_LI_FAB_INTS table is a core interface table within the Oracle E-Business Suite (EBS) Financial Aid module (IGF). Its primary role is to serve as the staging area for importing legacy financial aid base record data into the production system during data conversion or integration processes. As an interface table, it is designed to hold data extracted from external or legacy systems before it is validated and processed by the application's concurrent programs or APIs for permanent storage in transactional tables. The table's designation as a BUSINESS_ENTITY for IGF_BASE_RECORD underscores its critical function in representing the foundational student award information within the data import lifecycle. Its storage in the APPS_TS_INTERFACE tablespace is a standard architectural pattern for EBS interface objects.

Key Information Stored

The table stores a combination of unique identifiers, status flags, and process dates for financial aid awards. The primary key is a composite of CI_ALTERNATE_CODE (the award year) and PERSON_NUMBER, ensuring a unique record per student per year. A critical column for import process control is IMPORT_STATUS_TYPE, which tracks the processing state (e.g., NEW, ERROR, PROCESSED) of each interface record. Other significant columns manage the award lifecycle: AWARD_PROCESS_STATUS_CODE and its associated date track the packaging status, while AWARD_NOTIFY_STATUS tracks notification. Operational flags like OVERRIDE_NSLDS_FLAG, PROFESSIONAL_JUDGMENT_FLAG, and DISBURSE_VERIFICATION_HOLD control specific financial aid business rules. The table also includes standard EBS "Who" columns (CREATED_BY, CREATION_DATE, etc.) for auditing.

Common Use Cases and Queries

The primary use case is monitoring and managing the legacy data import process. Administrators frequently query this table to assess the volume and status of pending records, identify errors, and troubleshoot failed imports. Common SQL patterns include checking the import status for a specific batch or student, and identifying records that have failed to process. For example:

• To find all records in a specific batch that encountered an error: SELECT * FROM igf.igf_ap_li_fab_ints WHERE batch_num = <batch_id> AND import_status_type = 'ERROR';
• To count records by their current import status for reporting: SELECT import_status_type, COUNT(*) FROM igf.igf_ap_li_fab_ints GROUP BY import_status_type;
• To locate the interface record for a specific student and award year: SELECT * FROM igf.igf_ap_li_fab_ints WHERE person_number = '<student_id>' AND ci_alternate_code = '<year>';

Data is typically inserted into this table via SQL*Loader scripts or custom PL/SQL programs, and subsequently processed by dedicated Financial Aid concurrent requests.

Related Objects

As an interface table, IGF_AP_LI_FAB_INTS is a source for downstream processing. Its relationships are primarily defined by its unique key and status columns. The documented primary key index, IGF_AP_LI_FAB_INTS_PK, enforces uniqueness on the combination of CI_ALTERNATE_CODE and PERSON_NUMBER. The non-unique index IGF_AP_LI_FAB_INTS_N1 on the IMPORT_STATUS_TYPE column is crucial for the performance of status-based queries during import job processing. This table feeds data into the core Financial Aid transactional tables, though the specific target tables are not listed in the provided metadata. It is logically related to other IGF interface tables (e.g., for awards, disbursements) that share the BATCH_NUM and PERSON_NUMBER columns for coordinated processing. The PROGRAM_APPLICATION_ID and PROGRAM_ID columns indicate its integration with the EBS Concurrent Manager framework.