Search Results igf_aw_process_s




Overview

IGF_AW_COA_CALC is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified in ETRM documentation as an OTHER-type API rather than a formal public interface. It forms part of the Oracle Grants / Oracle Financial Aid (IGF) module family, specifically the Award (AW) subcomponent. Its role is to calculate and derive Chart of Accounts (COA) values for awards and award-related distributions, and to support the generation and update of COA item data used downstream by award processing logic. The package is a supporting utility within the award COA generation chain rather than a standalone entry point; it is not referenced by any other database object according to the documented dependency metadata, which indicates it is invoked directly by concurrent programs, forms, or the award generation routines rather than being called from other shared packages.

Key Procedures and Functions

The ETRM metadata documents a single procedure, RUN. This procedure constitutes the operational entry point of the package and is responsible for orchestrating the COA calculation logic, including the reading of award and award-attribute records, resolution of COA item and item-term definitions, and the population or recalculation of the relevant award COA structures. Because the package body is documented as VALID and contains one procedure, custom extensions should treat RUN as the sole supported invocation point rather than attempting to call internal, undocumented subprograms.

Tables Accessed

The package reads and writes an identifiable set of documented tables, all referenced through APPS synonyms:

Usage Notes

IGF_AW_COA_CALC is typically invoked as part of award COA generation and update processing, most likely from concurrent programs or award maintenance forms that drive the RUN procedure. The package depends on a wide set of supporting packages, including IGF_AW_COA_GEN, IGF_AW_COA_UPDATE, IGF_AW_GEN, IGF_AW_PACKNG_SUBFNS, IGF_AP_SS_PKG, IGS_GE_MSG_STACK, and FND utilities for logging, messaging, and file output (FND_FILE, FND_LOG, FND_MESSAGE, APP_EXCEPTION). Because it depends on FND_FILE, the RUN procedure is likely designed to run under concurrent manager control, where output and log files are available. Custom code should call only the documented RUN procedure, avoid direct manipulation of the underlying COA tables, and preserve the package's dependency on the standard message and logging infrastructure. Since the package is not referenced by any other database object, its execution lineage must be traced through the calling concurrent program or form rather than through package call graphs.