Search Results get_cumulative_coa_amt

Overview

IGF_AP_GEN is a generic PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, delivering shared functionality required by the legacy Student Financial Aid and Title IV processing modules associated with the Oracle Financial Aid (IGF) product family. The package header carries the RCS identifier IGFAP36S.pls, version 120.2, last modified in December 2005. Its stated purpose is to provide the generic building blocks needed by legacy batch and eligibility processes, particularly within the Title IV (Pell, Direct Loan, and campus-based aid) and ISIR (Institutional Student Information Record) correction and validation flows.

The package encapsulates lookup resolution against Oracle lookup types, profile option evaluation, person and identifier validation, award-year calendar-instance validation, and cumulative/individual Cost of Attendance (COA) amount retrieval. It exposes twelve documented program units and is referenced by twenty-four other packages, indicating that it functions as a low-level shared library across the IGF application module rather than as a user-facing API. Its metadata classification is OTHER, since it does not conform to the standard EBS open-interface or public API patterns.

Key Procedures and Functions

• GET_LOOKUP_MEANING — returns the human-readable meaning for a given lookup type and lookup code combination, isolating callers from direct queries against the lookup tables.
• GET_AW_LOOKUP_MEANING — an award-year-aware variant of the lookup resolution routine, accepting a system award year so that year-dependent lookup values are resolved against the correct set.
• CHECK_PROFILE — evaluates a profile option setting (documented as check_profile), returning a VARCHAR2 result so that callers can branch on profile-driven behavior; this is the unit most commonly targeted by searches such as "check_profile".
• CHECK_PERSON — validates a person number against the person identifier schema, ensuring the referenced individual is resolvable before downstream processing proceeds.
• CHECK_BATCH — verifies batch records within the Title IV and loan batch interface structures.
• VALIDATE_CAL_INST — validates calendar instances and their relationships used for academic-year and payment-period timing.
• GET_ISIR_VALUE — retrieves a fielded value from the ISIR matched-data records for downstream Federal Need Analysis usage.
• GET_INDV_EFC_4_TERM — returns the individual Expected Family Contribution (EFC) attributable to a specific term.
• GET_INDIVIDUAL_COA_AMT and GET_CUMULATIVE_COA_AMT — return Cost of Attendance amounts on an individual and cumulative basis respectively, supporting award packaging and fund-limit checks.
• UPDATE_TD_STATUS — updates the status of Title IV item records.
• UPDATE_PREFLEND_TODO_STATUS — updates the status of preferred-lender "to-do" records; this unit was added under Bug 4773795.

Tables Accessed

Access is performed through APPS synonyms. The package reads and maintains Title IV and borrower base data in IGF_AP_FA_BASE_REC_ALL and IGF_AP_ISIR_MATCHED_ALL; item and batch interface data in IGF_AP_TD_ITEM_INST_ALL, IGF_AP_TD_ITEM_MST_ALL, and IGF_AP_LI_BAT_INTS; loan-interview and COA intersection data in IGF_AW_LI_COA_INTS and the COA item terms in IGF_AW_COA_ITM_TERMS; and preferred-lender data in IGF_SL_CL_PREF_LENDERS. Lookup resolution draws from IGF_FC_SAR_CD_MST. Calendar validation joins IGS_CA_TYPE, IGS_CA_INST_ALL, and IGS_CA_INST_REL. Person data is sourced through HZ_PARTIES and IGS_PE_HZ_PARTIES. The package also references DBMS_UTILITY, used for array types declared in the header.

Usage Notes

IGF_AP_GEN is invoked as an internal shared utility rather than as an end-user API. It is called by other PL/SQL packages (twenty-four documented dependents) that implement the batch eligibility, ISIR correction, packaging, and disbursement processes for Title IV aid. The CHECK_PROFILE function is typically called at the start of a legacy process to read a profile option and select the appropriate processing path; callers should treat its return value as a branching flag rather than a validation exception. Because the package manipulates data across Title IV, person, calendar, and lender structures, custom code should invoke it in the sequence expected by the enclosing process and should not call status-update procedures directly against production data without the surrounding batch context. Seeded grants remain the authoritative mechanism for granting execute privileges on this package.