Search Results get_fk_igs_as_grd_schema

Overview

IGS_PS_UNIT_GRD_SCHM_PKG is a PL/SQL API package owned by APPS in the Oracle E-Business Suite, part of the Student Systems / Higher Education product family (IGS schema prefix). It encapsulates the database operations for the IGS_PS_UNIT_GRD_SCHM entity, which associates a grading schema (and a specific grading schema version) with a versioned academic unit, and designates whether that association is the default for the unit. In institutional terms, this package governs the rules that determine how a student's performance in a unit of study is graded — for example, which grade scale, mark ranges, and outcomes apply to a given unit offering. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than the definer, and its header carries the $Header tag IGSPI99S.pls 115.8 2002/11/29, indicating a long-standing seeded component of the IGS data model present across EBS 12.1.1 and 12.2.2. The package is classified as OTHER (a table-maintenance API rather than a business-process API) and is referenced by five other packages, confirming its role as a shared low-level access layer for unit-to-grading-schema relationships.

Key Procedures and Functions

• INSERT_ROW — Inserts a new unit grading schema association, including unit code, unit version number, grading schema code, grading schema version number, default flag, and the generated primary key. Accepts an X_MODE parameter (default 'R').
• ADD_ROW — Companion insert routine with the same logical payload as INSERT_ROW, used where the caller supplies or receives the surrogate identifier in a slightly different pattern. Also accepts X_MODE.
• UPDATE_ROW — Modifies an existing association identified by its primary key values, updating the grading schema and default flag attributes. Accepts X_MODE.
• LOCK_ROW — Issues a locking read against the row for the supplied key values, providing concurrency control consistent with Oracle Forms optimistic locking.
• DELETE_ROW — Deletes the row identified by X_ROWID.
• GET_PK_FOR_VALIDATION — Validates the existence of a row by primary key (unit grading schema ID) and returns BOOLEAN.
• GET_UK_FOR_UK_FOR_VALIDATION — Validates uniqueness of the alternate key composed of unit version number, grading schema code, grading schema version number, and unit code; returns BOOLEAN.
• GET_FK_IGS_PS_UNIT_VER — Foreign-key validation helper confirming that the referenced unit code and version number exist in the unit version entity.
• GET_FK_IGS_AS_GRD_SCHEMA — The routine the user searched for. It performs foreign-key validation against the grading schema entity, taking a grading schema code and version number, to ensure the schema referenced by a unit grading schema association is valid before insert or update.
• CHECK_CONSTRAINTS — Validates column-level database constraints for a named column.
• BEFORE_DML — Internal row-level trigger logic invoked before DML to enforce WHO columns and derived values.

Tables Accessed

• IGS_PS_UNIT_GRD_SCHM — The base table holding unit-to-grading-schema associations; the target of all insert, update, delete, and lock operations.
• IGS_PS_UNIT_GRD_SCHM_S — The translated/security shadow table for the base entity, maintained in parallel by the DML routines.
• DUAL — Used for single-row lookups and validation selects.

Foreign-key validation routines implicitly query the referenced unit version and grading schema entities (IGS_PS_UNIT_VER and IGS_AS_GRD_SCHEMA) through their APPS synonyms.

Usage Notes

The package is invoked primarily from the Oracle Forms front end that maintains unit grading schema assignments, where triggers call INSERT_ROW, UPDATE_ROW, and DELETE_ROW and rely on LOCK_ROW for concurrency. Validation triggers call GET_PK_FOR_VALIDATION, GET_UK_FOR_VALIDATION, and the Get_FK_* helpers, while CHECK_CONSTRAINTS and BEFORE_DML support constraint enforcement and audit column population. Because it is referenced by five other packages, custom PL/SQL integrations and data-load routines for the IGS schema should call this package rather than performing direct DML on IGS_PS_UNIT_GRD_SCHM, ensuring the shadow table, audit WHO columns, and validation rules remain consistent.