Search Results get_fk_igs_tr_note_type

Overview

IGS_TR_TYP_STEP_NOTE_PKG is a PL/SQL package owned by the APPS schema that forms part of the Oracle E-Business Suite academic tracking infrastructure. In the context of the Student Records / Tracking functionality within the Oracle Student System, this package encapsulates the data-access and manipulation logic for the IGS_TR_TYP_STEP_NOTE entity. This entity represents note-type associations attached to individual steps within a tracking type — that is, the definition of which note types may be recorded against a given step of a tracking type as configured for an institution.

The package is a generated-style table-handler API. Its declared procedures map directly to the standard Oracle Forms-based DML handler pattern (insert, update, delete, lock) plus supporting validation and constraint procedures. It is declared with AUTHID CURRENT_USER, meaning the package executes with the privileges of the invoking user rather than the definer, and it is classified in the ETRM repository under the API classification OTHER. The presence of the source header ($Header: IGSTI07S.pls 115.5 2002/11/29) indicates the package has been stable since the early 11i-era architecture, which the 12.1.1 and 12.2.2 releases continue to carry.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. INSERT_ROW performs the primary insert of a tracking-type step note record and returns the associated ROWID. ADD_ROW provides the equivalent insert entry point used in the Forms ADD flow, including the operating-unit context. UPDATE_ROW modifies an existing record, and DELETE_ROW removes a record identified by its ROWID. LOCK_ROW implements pessimistic locking for concurrent editing in the Forms runtime.

• GET_PK_FOR_VALIDATION — validates that a primary-key combination exists in the base table, returning a Boolean result used to enforce uniqueness and FK-style checks.
• GET_FK_IGS_GE_NOTE — check that the referenced note (general note) exists for the given reference number. This is the foreign-key validation that the user's search term relates to.
• GET_FK_IGS_TR_NOTE_TYPE — validates that the supplied tracking note type exists in IGS_TR_NOTE_TYPE. This is the precise routine the user searched for; it confirms referential integrity of the X_TRK_NOTE_TYPE column.
• GET_FK_IGS_TR_TYPE_STEP — validates that the supplied tracking type and step identifier combination exists, ensuring the parent step is a legitimate parent for the note association.
• CHECK_CONSTRAINTS — an extension added to enforce database check constraints that cannot be deferred, taking optional column name and value arguments.
• BEFORE_DML — a centralised pre-DML hook that runs business validation (including the FK checks above) before any insert, update, or delete is performed.

Tables Accessed

The package reads and writes a single base table, IGS_TR_TYP_STEP_NOTE, accessed through its APPS synonym. This table stores the association between a tracking type step and the note types permitted or recorded for that step. The FK validation routines query the IGS_GE_NOTE, IGS_TR_NOTE_TYPE, and IGS_TR_TYPE_STEP tables to confirm that the foreign-key values supplied to the DML routines are valid against their parent entities.

Usage Notes

Because it is a Forms-generated table handler, this package is primarily invoked from the Oracle Forms user interface that maintains tracking type step note definitions, and it may equally be called from concurrent programs or custom PL/SQL that manipulate tracking configuration data. The three packages documented as referencing it depend on its row-level DML and validation logic, so any custom extension should call the documented routines rather than issuing direct DML against IGS_TR_TYP_STEP_NOTE, thereby preserving the constraint and FK validation enforced by BEFORE_DML.