Results for “igs_as_derive_grade”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AS_DERIVE_GRADE is an Oracle EBS Student Systems (IGS — Student Information) PL/SQL package owned by the APPS schema. It encapsulates the business logic used to derive and validate academic grades for student unit attempts within the assessment and grading framework of Oracle Student Information. In the terminology of the product, "AS" refers to assessment, "SU" to student unit, and "UA" to unit attempt. The package's core responsibility is to convert raw assessment outcome data recorded against a student's unit attempt into a formal grade, and to apply the institution's grading scheme rules to that derivation.

The package is classified as an API of type OTHER, meaning it is an internal utility package rather than a formally published public API. It is referenced by other database objects — specifically the view IGSFV_AS_SU_ATMPT_OUTCOMES, the view IGS_AS_UG_ADI_V, and the recursive reference from IGS_AS_DERIVE_GRADE itself — and it references two other packages. Its status is VALID at the recorded ETRM release level, confirming it is a live, compiled object at 12.1.1 and, by inheritance, at 12.2.2 where the IGS data model is unchanged.

Key Procedures and Functions

Ten documented procedures and functions are exposed by this package. Their names describe the derivation and validation workflow:

• VALIDATE_AI_US_GRD_MARK_RANGE — validates that an assessment item mark falls within the permitted grade or mark range defined for the grading scheme.
• DERIVE_SUAO_MARK_GRADE_SUAIO — derives the student unit attempt outcome mark and grade from student unit attempt assessment item outcomes.
• DERIVE_SUAO_MARK_FROM_SUAIO — derives the outcome mark from the contributing assessment item outcomes.
• DERIVE_SUAO_GRADE_FROM_SUAIO — derives the final grade from the assessment item outcomes.
• GET_ASSESSMENT_STATUS — returns the assessment status associated with the unit attempt or assessment item.
• GET_GRADING_PERIOD_CODE — returns the grading period code applicable to the grading event.

The documented list totals ten entries; the extract above names six, all centred on the same derive-and-validate theme. No parameter lists are published in the metadata, so signatures cannot be stated with certainty and are deliberately omitted here.

Tables Accessed

The package reads and writes a defined set of IGS tables through APPS synonyms. Configuration tables — IGS_AS_CAL_CONF and IGS_AS_ENTRY_CONF — supply assessment calendar and entry configuration rules. Grading scheme definition is drawn from IGS_AS_GRD_SCH_GRADE, IGS_PS_UNIT_GRD_SCHM and IGS_PS_USEC_GRD_SCHM, which together describe which grading scheme applies to a unit offering option (IGS_PS_UNIT_OFR_OPT_ALL). Assessment item structure is held in IGS_PS_UNITASS_ITEM and IGS_AS_UNITASS_ITEM_ALL, while student attempt data resides in IGS_EN_SU_ATTEMPT_ALL, IGS_AS_SU_ATMPT_ITM, IGS_AS_GAA_SUB_HIST and IGS_AS_SU_STMPTOUT_ALL. The outcome of derivation is persisted to IGS_AS_SU_STMPTOUT_ALL — the student unit attempt outcome record — which is why the package is referenced by the SU attempt outcome view.

Usage Notes

IGS_AS_DERIVE_GRADE is typically invoked from the Student Assessment and Grading forms and from assessment-related concurrent programs that process marks and grades in batch. Because it is not a published API but an internal utility, custom code should generally call the higher-level published assessment APIs rather than this package directly; direct calls risk breaking on patch application since the package signature is not guaranteed. Where it is referenced, such as through IGSFV_AS_SU_ATMPT_OUTCOMES, the derivation is triggered implicitly when outcome data is queried or recomputed. Developers investigating "igs_as_derive_grade" are most often tracing how a student's grade was calculated, and should examine the grading scheme configuration and assessment item outcome rows in parallel with the package logic. As with all APPS-owned IGS objects, any modification should be confined to a custom schema wrapper rather than editing the seeded package body.