Search Results igs_pr_get_class_std




Overview
Explore in AI Chat

Overview

IGS_PR_GET_CLASS_STD is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the Student Systems / Academic Records product family (the IGS prefix denotes the Oracle Student System). Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2 environments. The package encapsulates the retrieval logic for a student's class standing, a derived academic designation that reflects progression through a program of study based on completed credit and applicable progression rules. Rather than storing class standing as a persistent attribute of the student, the institution configures standing rules in the IGS_PR_* setup tables and the package resolves the appropriate standing dynamically at query time. The API classification is recorded as OTHER, indicating it is not part of a formally published public API set, though it is a functional dependency for numerous other packages within the product.

Key Procedures and Functions

The documented interface exposes a single program unit: GET_CLASS_STANDING. Its purpose is to return the class standing determined for a given student and academic context by applying the institution's configured class standing rules against the student's current progression data. Internally the package consults progression calendar structures and the class-standing rule definitions to decide which standing value applies.

The package body also declares the private constructs required to support that call. The dependency listing shows a self-reference to IGS_PR_GET_CLASS_STD, reflecting overloaded or recursively invoked internal logic, alongside helpers that read the effective standing-rule set, evaluate load or completed-credit thresholds, and stage interim results before the final standing is returned. Validation and diagnostic support is provided through FND_API, FND_MESSAGE, FND_LOG, APP_EXCEPTION, and IGS_GE_MSG_STACK, which together handle message derivation, error stacking, and debug logging. No procedural signatures are documented beyond the name and purpose of GET_CLASS_STANDING.

Tables Accessed

The package reads a set of configuration and transactional tables through APPS synonyms, reflecting a layered dependency model:

  • IGS_PR_CLASS_STD — the core definition of class standing codes and their rule attributes that the package must evaluate.
  • IGS_PR_CSS_CLASS_STD — the association between a class standing scheme and the class standing values belonging to that scheme.
  • IGS_PR_CS_SCHDL — the schedule relating class standing to progression calendar periods, governing which rule set applies at a given point in the student's study.
  • IGS_CA_INST_REL and IGS_CA_TYPE — calendar instance and calendar type data used to resolve the academic period against which standing is computed.
  • IGS_EN_SPA_TERMS — the student program attempt term records that supply the enrollment and progression context for the evaluated student.

Additional dependent objects referenced in the dependency tree, including IGS_EN_STDNT_PS_ATT, IGS_EN_SU_ATTEMPT, IGS_PS_VER, IGS_CA_INST, and the IGS_PR_CP_GPA computation package, supply program version, attempt, and grade point average inputs consumed during standing resolution. The package itself is not referenced by any database object, confirming that it is invoked from within PL/SQL rather than through database-level dependencies such as views or triggers.

Usage Notes

IGS_PR_GET_CLASS_STD is typically invoked indirectly. Sixteen other packages in the APPS schema depend upon it, making it a shared utility for any process that must display or evaluate class standing — student progression inquiries, enrollment validation, academic standing reports, and progression-related concurrent programs. Because it resolves standing dynamically from configuration, callers should expect the returned value to change as a student's attempt and grade data changes, without any explicit update to a standing attribute. Implementations should invoke GET_CLASS_STANDING in the correct program attempt and calendar context, since the rule schedule table (IGS_PR_CS_SCHDL) determines which standing definitions apply. Custom extensions should call the package rather than replicate its logic, and should observe the error-handling conventions of FND_API and IGS_GE_MSG_STACK so that failures propagate consistently. Debug output can be enabled through FND_LOG for troubleshooting rule-resolution issues.