Search Results get_ufk_igs_pr_class_std




Overview
Explore in AI Chat

Overview

IGS_AS_GPC_CLS_STNDG_PKG is a student systems package in the Oracle E-Business Suite Academic/Student (IGS) module, owned by the APPS schema. It encapsulates the data-access and validation logic for the IGS_AS_GPC_CLS_STNDG entity, which stores the relationship between a grading period code and an associated class standing designation. This entity supports grade processing and academic progression rules, where class standing values must be maintained and cross-validated against the grading period classification data before other grade-related processing can rely on them.

The package is compiled with AUTHID CURRENT_USER and therefore executes with the privileges of the invoking schema. Its header identifies the source file as IGSDI51S.pls (version 115.3), last shipped in November 2002. Within the documented API classification it is listed as OTHER, meaning it is not one of the curated public APIs, yet its named procedures and validation functions are commonly invoked from generated forms and internal packages. ETRM records nine procedures/functions in total and one downstream package reference.

Key Procedures and Functions

The package exposes the standard transactional and validation primitives expected of an IGS entity handler:

  • INSERT_ROW — inserts a new grading-period/class-standing row, returning the new row identifier and primary key to the caller. The x_mode parameter defaults to 'R'.
  • ADD_ROW — performs the same functional insertion as INSERT_ROW, conventionally used by the client form layer.
  • UPDATE_ROW — updates an existing row identified by rowid and primary key.
  • LOCK_ROW — acquires a pessimistic lock on a row so that concurrent update or delete operations are serialized.
  • DELETE_ROW — deletes a row, identified by its rowid.
  • GET_PK_FOR_VALIDATION — returns a Boolean indicating whether the supplied primary key identifies a valid row. It is the primary-key existence check used by foreign-key lookups.
  • GET_UK_FOR_VALIDATION — returns a Boolean indicating whether the supplied combination of grading period code and class standing is unique, the unique-key integrity check for the entity.
  • GET_UFK_IGS_PR_CLASS_STD — the user-facing (unique foreign key) validation routine for the IGS_PR_CLASS_STD reference. It accepts a class standing value and validates it against the class-standing reference data, enabling descriptive-flexfield and forms LOV validation when a user enters a class standing.
  • BEFORE_DML — the internal pre-DML hook that enforces Who-column defaults (creation date, created by, last update date, last updated by, last update login) and common business rules for insert, update and delete actions.

Tables Accessed

Through APPS synonyms, the package reads and writes the following base tables:

  • IGS_AS_GPC_CLS_STNDG — the primary entity table holding grading period code, class standing and the surrogate primary key. INSERT_ROW, ADD_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW and BEFORE_DML all operate here.
  • IGS_AS_GPC_CLS_STNDG_S — the corresponding sequence/identifier support object used to derive new primary key values on insert.
  • IGS_AS_GPC_PE_ID_GRP — the grading-period/identifier grouping entity referenced during validation of the grading period association.
  • DUAL — used for single-row PL/SQL SELECT expressions, typically inside the validation functions.

Usage Notes

The package is normally invoked in three contexts. First, from the Oracle Forms-based maintenance screens for grading period class standing, where the form calls ADD_ROW, INSERT_ROW, UPDATE_ROW, DELETE_ROW and LOCK_ROW to manage rows and BEFORE_DML to populate the Who columns. Second, from validation triggers and LOV definitions, which call GET_UFK_IGS_PR_CLASS_STD and GET_UK_FOR_VALIDATION to confirm that an entered class standing is properly defined before the record is committed. Third, from other PL/SQL packages; ETRM records one package that references this one, generally through the validation functions rather than the DML routines. Customizations should prefer the validation functions and treat the DML routines as form-server internals, since direct insertion bypasses the BEFORE_DML defaulting logic. As the package is AUTHID CURRENT_USER, callers must hold the underlying object privileges, and any wrapper code should preserve the x_mode and Who-column conventions to avoid invalid rows.