Search Results igf_aw_award_level_hist_s

Overview

The APPS.IGF_AW_LI_IMPORT package body is a PL/SQL component within the Oracle E-Business Suite Financial Aid / Student Aid module (IGF schema family). It functions as a data import and interface engine for award-level financial aid information, processing inbound records against the award, disbursement, and student authorization structures maintained by the Oracle Student System and Financial Aid (IGS/IGF) applications. The package is classified as an API of type OTHER, indicating that it is not a published public API in the traditional sense but instead serves as an internal processing routine invoked by concurrent programs, batch processes, or dependent packages. Its primary business purpose is to ingest external or staged award-level data, validate that data against existing award year, disbursement, and hold records, resolve person identifiers, and persist the accepted results into the appropriate IGF award and disbursement base tables. In the context of Oracle EBS 12.1.1 and 12.2.2, the package participates in the broader financial aid award lifecycle, complementing packages such as IGF_AW_AWARD_PKG, IGF_AW_AWARD_LEVEL_HIST_PKG, and IGF_AW_AWD_DISB_PKG, which manage award headers, award-level history, and disbursement records respectively.

Key Procedures and Functions

The package body exposes seven documented procedures and functions. MAIN serves as the primary entry point, orchestrating the overall import flow from staging data through validation to final persistence. RUN is the driver procedure, typically invoked by a concurrent program or scheduler to execute the import for a given run or parameter set. VALIDATE_AWDYEAR_INT_REC validates award year interface records, ensuring the award year and related context align with existing award definitions. VALIDATE_DISBURS_INT_REC validates disbursement interface records against award disbursement expectations. VALIDATE_DISB_ACT_INT_REC validates disbursement activity interface records, confirming that activity-level entries are consistent with the parent disbursement. VALIDATE_DISB_HOLD_INT_REC validates disbursement hold interface records, checking that holds are structured correctly before being written. GET_BASE_ID_FROM_PER_NUM is a lookup function that resolves a person identifier to its corresponding base ID, supporting linkage between imported records and existing party or person records. Parameter lists are not documented in the available metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes against numerous APPS synonyms. Interface staging tables include IGF_AW_LI_AWD_INTS, IGF_AW_LI_DISB_INTS, and related interface tables, which hold inbound award and disbursement records. Persistent award tables include IGF_AW_AWARD_ALL, IGF_AW_AWARD_LEVEL_HIST, IGF_AW_AWARD_LEVEL_HIST_S, and IGF_AW_AWD_DISB_ALL, which store award headers, award-level history, and disbursement detail. Supporting award configuration data is drawn from IGF_AW_COA_ITEMS, IGF_AW_COA_ITM_TERMS, IGF_AW_DB_CHG_DTLS, and IGF_AW_DB_COD_DTLS. Person resolution uses HZ_PARTIES. Batch/mapping and matched-ISIR data are sourced from IGF_AP_BATCH_AW_MAP_ALL, IGF_AP_FA_BASE_REC_ALL, and IGF_AP_ISIR_MATCHED_ALL. Logging is captured via FND_LOG_MESSAGES. The full dependency list also references many IGF_AP, IGF_AW, IGF_DB, IGF_SE, IGF_SL, IGS_FI, IGS_PE, and IGS_CA objects used indirectly through package calls.

Usage Notes

IGF_AW_LI_IMPORT is not referenced by any other documented package (referenced by 0 packages), which indicates that it is invoked directly rather than through internal package dependency chains. It is typically executed as part of a financial aid award import concurrent program or batch job, where the RUN procedure drives processing and MAIN coordinates validation and persistence. Because the package depends on FND_FILE, FND_LOG, FND_MESSAGE, FND_PROFILE, and FND_GLOBAL, it is designed for concurrent-manager execution, producing log output and raising Oracle EBS messages for error conditions. The presence of VALIDATE routines suggests a staged-validation pattern, where interface records are checked before being promoted to base tables. Customizations and extensions in Oracle EBS 12.1.1 or 12.2.2 should not modify this package body directly; instead, integrations should leverage the interface tables it consumes and trigger the import through the supported concurrent program path, preserving upgrade safety and ensuring validation logic remains intact.