Search Results igs_gr_honours_level_pkg




Overview
Explore in AI Chat

Overview

IGS_GR_HONOURS_LEVEL_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Student System (IGS) product family. It supports the honours classification framework used by higher-education institutions to define and maintain the honours levels awarded to graduating students. In the EBS data model, honours levels represent the discrete bands of academic achievement — for example, first class, upper second class, lower second class, and pass — that are referenced when a student's final award is recorded. The package encapsulates the DML logic for the underlying IGS_GR_HONOURS_LEVEL_ALL entity, providing a controlled, reusable interface so that validation rules, primary-key derivation, and foreign-key checks are applied consistently wherever honours-level records are created or maintained. Its classification as OTHER confirms that it is an internal entity-maintenance utility rather than a public transactional API, and it is a standard component of the 12.1.1 and 12.2.2 file systems for the Student System module.

Key Procedures and Functions

The package exposes eight documented procedures and functions that together implement the complete maintenance cycle for an honours-level record:

  • INSERT_ROW — Inserts a new honours-level record into the base table, applying the package's standard column derivation and defaulting rules.
  • UPDATE_ROW — Updates the mutable attributes of an existing honours-level record while preserving the audit and key columns.
  • ADD_ROW — Higher-level wrapper that combines key derivation and insertion so that callers can add a record in a single call.
  • LOCK_ROW — Acquires a row-level lock on the target record, typically invoked at the start of an update or delete sequence to prevent concurrent modification.
  • BEFORE_DML — Central pre-DML hook that populates audit columns and applies the mandatory attribute defaults before any insert or update is committed.
  • CHECK_CONSTRAINTS — Executes the package's business-rule validations against the supplied record, returning or raising errors when the data violates the entity's constraints.
  • GET_PK_FOR_VALIDATION — Resolves and returns the primary-key value required to validate the record being processed.
  • GET_FK_IGS_GR_GOVT_HNS_LVL — Resolves the foreign-key relationship from the honours-level entity to the government honours-level reference data, ensuring referential integrity before the record is committed.

Tables Accessed

The package operates against the table IGS_GR_HONOURS_LEVEL_ALL, accessed through its APPS synonym. This table stores the honours-level definitions, including the identifying code, descriptive text, and the associated government honours-level mapping. All insert, update, lock, and validation operations documented above act on this single base entity, which is consistent with the package's narrow role as an entity-maintenance wrapper rather than a cross-entity processor.

Usage Notes

IGS_GR_HONOURS_LEVEL_PKG is referenced by two other packages: IGS_GR_GOVT_HNS_LVL_PKG, which manages the government honours-level reference data that this package validates against, and IGS_AD_TER_EDU_PKG, which consumes honours-level information during admissions and prior-education processing. The package is therefore normally invoked indirectly — through these dependent packages or through the Oracle Forms user interface that maintains honours-level setup data — rather than being called directly by end users. In custom extensions, it should be invoked only where the equivalent form-level validation cannot be reused, and any direct call should preserve the standard sequence of LOCK_ROW, BEFORE_DML, CHECK_CONSTRAINTS, and INSERT_ROW or UPDATE_ROW. Because the package manipulates the _ALL table, implementers must confirm that the correct operating-unit or multi-org context is established before invocation. In 12.2.2 online patching environments, the package is editioned along with the rest of the APPS code, so custom code that references it should be edition-enabled to avoid cross-edition dependency errors.