Search Results chk_pell_orig




Overview

IGF_AP_ISIR_GEN_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the ISIR (Institutional Student Information Record) processing lifecycle within the Oracle Financial Aid module. The package is classified as API classification OTHER and is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Its principal business purpose is to generate, validate, lock, match, and remove ISIR data received from the federal processor and to synchronize that data with financial aid awarding records. The package serves as a central utility layer that coordinates ISIR interface staging, matched-person records, awarding eligibility, and the corresponding baseline records used in need analysis and award processing.

Key Procedures and Functions

The ETRM metadata documents sixteen procedures and functions. Their documented names and purposes are summarized below.

Tables Accessed

The package reads and writes a defined set of APPS synonyms. FND_USER and FND_RESPONSIBILITY provide the identity and responsibility context for processing actions. ISIR-specific data resides in IGF_AP_ISIR_INTS_ALL (interface staging), IGF_AP_ISIR_MATCHED_ALL (matched ISIRs), and IGF_AP_ISIR_CORR_ALL (corrections). Person matching is supported through IGF_AP_PERSON_MATCH_ALL and IGF_AP_MATCH_DETAILS. Need analysis and award processing use IGF_AP_FA_BASE_REC_ALL, IGF_AP_FA_ANT_DATA, and IGF_AW_AWARD_ALL. Additional references include IGF_AP_BATCH_AW_MAP_ALL, IGF_AP_HOUSING_MAP, IGF_AP_NSLDS_DATA_ALL, and IGF_GR_RFMS_ALL, which support batch awarding, housing, NSLDS, and RFMS integration respectively.

Usage Notes

IGF_AP_ISIR_GEN_PKG is referenced by the APPS packages IGF_AP_MATCHING_PROCESS_PKG and IGF_AP_SS_PKG, indicating that it is normally invoked indirectly through ISIR matching and self-service processing flows rather than directly by end users. Invocation typically occurs from financial aid concurrent programs, Oracle Forms-based ISIR maintenance and matching screens, and custom extensions that must validate, lock, or delete ISIR records. Because several routines perform destructive operations, custom callers should treat DELETE_ISIR, DELETE_INTERFACE_RECORD, DELETE_INT_RECORDS, and DELETE_PERSON_MATCH as privileged operations and invoke them only after confirming that associated award and validation data will not be orphaned. The package should always be called using the APPS schema or an APPS synonym, consistent with standard EBS API usage.