Search Results check_acad_load_adm_rel

Overview

IGS_FI_PRC_STDNT_DPSTS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API object. It belongs to the Oracle Student System (formerly Oracle iLearning/Student System) product family and supports the Financials (IGS_FI) module, specifically the processing of student deposits and their interaction with academic load and admissions-related relationship data. The package operates as a server-side processing component rather than a public callable API, meaning it is referenced internally by other constructs rather than being exposed as a standalone interface for external integration. It is documented in both EBS 12.1.1 and 12.2.2, where it holds a VALID status in the APPS schema. Its role centers on validating and processing student deposit records in relation to academic enrollment and admission status, ensuring that financial deposit transactions are consistent with the student's academic program level, offer response status, and institutional configuration.

Key Procedures and Functions

The ETRM metadata documents a total of two procedures/functions within this package. The principal documented program unit is:

• CHECK_ACAD_LOAD_ADM_REL — This procedure performs a validation check that relates a student's academic load to admission-relevant relationship data. In practice, this is used to determine whether a student's academic load (for example, the number of enrolled credit hours or registered units) is consistent with their admission relationship status and program level before deposit processing proceeds. It acts as a rules-based gate that confirms the student's academic and admission context is valid for the financial deposit being processed.

The second documented program unit is not separately detailed in the excerpted dependency metadata. Consistent with ETRM documentation practices, parameter lists for both units are intentionally withheld here; the package signature should be inspected directly in the database or via the "show dependent code" reference flagged in the ETRM dependency section. The dependency listing shows the package is self-referencing (APPS.IGS_FI_PRC_STDNT_DPSTS references itself), indicating internal recursion or helper routine reuse within the package body.

Tables Accessed

The package reads and writes the following tables via APPS synonyms, which reveal its functional scope:

• IGS_FI_CONTROL_ALL, IGS_FI_CREDITS_ALL, IGS_FI_CR_TYPES_ALL — Financials control, credit, and credit type configuration tables that define deposit rules, credit application logic, and credit type definitions used when processing student deposits.
• IGS_AD_DEPLVL_PRG, IGS_AD_DEPLVL_PRGTY, IGS_AD_OFRDFRMT_STAT, IGS_AD_OFR_RESP_STAT, IGS_AD_SS_APPL_TYP — Admissions tables covering departmental program levels, program types, offer formats, offer response status, and application types that establish the student's admission context.
• IGS_CA_INST_REL, IGS_CA_TYPE — Calendar instance relationship and calendar type tables, used to resolve the academic period relevant to the deposit.
• HZ_PARTIES — The Trading Community Architecture party table, used to resolve student identity.
• IGS_PE_PRSID_GRP_MEM_ALL — Person identifier group membership, used for grouping and eligibility checks.
• FND_NEW_MESSAGES — Oracle Application Object Library message table, used to retrieve user-facing error or warning messages.
• DUAL, PLITBLM — The standard dual table and the PL/SQL integer table type used for set-based operations.

Usage Notes

The ETRM dependency data shows that, as of the documented release, IGS_FI_PRC_STDNT_DPSTS is referenced by no other packages and is listed as being referenced only by itself. This indicates the package is a leaf-level processing unit that is invoked directly by Oracle Student System forms, concurrent programs, or Student System Financials setup flows rather than through a wider chain of dependent APIs. When extending or customizing, developers should not treat it as a supported public API, since its classification is OTHER rather than a designated public interface. Any wrapper code should call it only after confirming the parameter signatures via the database, and should respect the admission, calendar, and financials configuration assumptions embedded in the tables it accesses.