Search Results igs_gr_note_type_pkg

Overview

The IGS_GR_NOTE_TYPE_PKG package body in the APPS schema supports the Oracle E-Business Suite student records domain — specifically the configuration and maintenance of grade note types. In Oracle Student System (the IGS product family, formerly part of Oracle Higher Education), note types define the categories of annotations that can be associated with a student's grade record, such as remarks, comments, or coded observations attached during grade entry or grade processing workflows.

This package is classified under the ETRM repository as an OTHER API type rather than a public PL/SQL API. It provides the low-level data manipulation and validation logic that a generated maintenance form or associated calling package relies upon to insert, lock, update, and delete rows in the underlying note-type table. The package is documented as VALID at release 12.1.1 and remains relevant through 12.2.2, since the IGS-Student System schema objects were not materially restructured between those releases.

Key Procedures and Functions

The ETRM metadata records eight documented procedures or functions in the package body. Their purposes are as follows:

• INSERT_ROW — Performs the core insert of a new note-type row into the base table. Acts on the entity as a whole, carrying the column values populated by the calling form or package.
• LOCK_ROW — Issues a locking read against an existing note-type row so that concurrent maintenance transactions cannot modify the same record simultaneously.
• UPDATE_ROW — Applies changes to an existing note-type row, typically after LOCK_ROW has secured the record.
• ADD_ROW — Convenience entry point that sequences insertion of a new record, generally combining validation with INSERT_ROW.
• DELETE_ROW — Removes a note-type row from the base table, subject to any constraint checks performed first.
• GET_PK_FOR_VALIDATION — Retrieves or derives the primary key value needed when validating a row, ensuring that validations operate against a fully identified record.
• CHECK_CONSTRAINTS — Central validation routine that enforces the business and referential rules governing a note-type row before it is committed.
• BEFORE_DML — Pre-DML hook invoked ahead of the insert, update, or delete operations, used to set WHO columns and prepare the row for persistence.

Tables Accessed

The package operates against a single documented base table, IGS_GR_NOTE_TYPE, accessed through its APPS synonym. This table stores the definition of grade note types — the name, code, and associated attributes that determine how a grade annotation is presented and used. All eight procedures above ultimately read from or write to this table: INSERT_ROW and ADD_ROW add records, UPDATE_ROW modifies them, DELETE_ROW removes them, and the locking and validation routines (LOCK_ROW, GET_PK_FOR_VALIDATION, CHECK_CONSTRAINTS) interrogate it to secure or verify existing rows.

Usage Notes

As a non-public package, IGS_GR_NOTE_TYPE_PKG is not intended for direct invocation by customer code. Dependency information shows that it references APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, and IGS_GR_CRMN_NOTE_PKG, and that it is referenced by one other package in the schema. The dependency on IGS_GR_CRMN_NOTE_PKG is significant: the CRM note package is the likely external caller, invoking these routines when grade-related notes are created or maintained in the Student System. FND_GLOBAL supplies the current session's application and user context, while FND_MESSAGE and APP_EXCEPTION handle user-facing error messaging and exception propagation during validation failures.

In practice, the package is executed indirectly — either through generated Oracle Forms maintenance screens for the IGS_GR_NOTE_TYPE entity or through the calling package that manages grade/CRM note processing. Administrators configuring grade note types, and batch processes that attach notes to student grade records, therefore exercise this package transparently. ETRM lists IGS_GR_NOTE_TYPE_PKG as referenced by no database object, confirming that its only inbound link is at the package level. Because the IGS schema is release-stable across 12.1.1 and 12.2.2, no release-specific behavioral differences are documented.