Search Results igs_pr_get_std_gpa

Overview

IGS_PR_GEN_006 is a PL/SQL package owned by the APPS schema that forms part of the Oracle E-Business Suite product family associated with Student Systems / Student Records (the IGS namespace). The package is registered in ETRM as VALID and is classified under the generic API category OTHER, indicating that it is an internal processing utility rather than a formally published public API. Its identifier and dependency footprint place it within the "PR GEN" series of generation and progression packages (IGS_PR_GEN_003 through IGS_PR_GEN_006), which collectively support the derivation, validation, and maintenance of student progression, academic standing, and sponsored or funded study entitlement data.

In practical terms, the package encapsulates the business rules and helper logic used to evaluate progression outcomes: computing grade point averages and weighted averages, resolving sponsor entitlement application windows, checking sponsorship comment and expiry conditions, copying progression application records, and updating status flags on student course attempts and sponsored awards. Because it is consumed by several sibling packages and by the IGS_PR_STU_ACAD_V view, it functions as a shared library of progression calculations rather than an entry point in its own right.

Key Procedures and Functions

Fifteen documented procedures and functions are catalogued for this package. Their naming conventions indicate the following responsibilities:

• IGS_PR_GET_STD_GPA and IGS_PR_GET_STD_WAM — return a student's grade point average and weighted average mark respectively, used as inputs to progression and standing decisions.
• IGS_PR_GET_SPO_APLY_DT, IGS_PR_GET_SPO_CMT, IGS_PR_GET_SPO_EXPIRY — retrieve sponsored award attributes: the application date, associated comment text, and expiry date, supporting the validation of sponsored study entitlements.
• IGS_PR_GET_SCSC_COMP, IGS_PR_GET_SPRC_DSP, IGS_PR_GET_WITHIN_APPL — return derived progression values, including completion indicators and display-related attributes, and evaluate whether a given point in time falls within an applicable application window.
• IGS_PR_INS_COPY_PRA and IGS_PR_INS_SSP_CMP_DTL — insert routines that copy progression application rows and create sponsored study plan component detail records.
• IGS_PR_UPD_PEN_CLASH, IGS_PR_UPD_SCA_STATUS, IGS_PR_UPD_SPO_PEN — update routines that resolve penalty clashes, set student course attempt status, and record sponsored award penalties.
• GET_ANTCP_COMPL_DT — returns an anticipated completion date, used in progression planning and reporting.

The parameter lists are not exposed in the ETRM metadata; callers must therefore consult the package specification directly before invoking any of these units.

Tables Accessed

Documented dependencies show the package referencing IGS_EN_STDNT_PS_ATT_ALL, the student course attempt table, which is the primary source of enrolment and outcome data for the GPA, weighted average, and status-update logic. Additional tables accessed through APPS synonyms include configuration and reference data such as IGS_CA_DA_INST, IGS_CA_INST_REL, IGS_CA_STAT, IGS_CA_TYPE (calendar and institution reference data), IGS_EN_ENCMB_EFCTTYP and IGS_FI_ENC_DFLT_EFT (encumbrance effect types and default financial encumbrance settings), IGS_OR_REL_PS_TYPE and IGS_OR_UNIT_REL (organisational unit relationships), and exclusion tables IGS_PE_COURSE_EXCL, IGS_PE_CRS_GRP_EXCL, IGS_PE_FUND_EXCL, and IGS_PE_PERSENC_EFFCT. Party and user context is drawn from HZ_PARTIES and FND_USER. Together these tables supply the academic, financial, and organisational context required for progression and sponsorship evaluation.

Usage Notes

The package is referenced by five other packages — IGS_PR_GEN_003, IGS_PR_GEN_004, IGS_PR_GEN_005, IGS_PR_GEN_006, and IGS_PR_VAL_SPO — and by the view IGS_PR_STU_ACAD_V. This dependency pattern indicates that it is normally invoked indirectly: either as part of a larger progression batch, through the validation logic in IGS_PR_VAL_SPO, or when the academic view is queried in forms and reports. Because it is classified as OTHER rather than a public API, direct invocation from custom code should be undertaken cautiously, with the package specification reviewed first and dependencies revalidated after any upgrade. The presence of both insert and update routines suggests it participates in data-maintenance flows, so callers should ensure they run inside appropriate transaction boundaries and commit scopes.