Search Results get_fk_igs_pe_note_type




Overview
Explore in AI Chat

Overview

IGF_AP_PERS_NOTE_PKG is an Oracle Application Object Library (AOL) style PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It encapsulates the database operations for the IGF_AP_PERS_NOTE table, which stores personal note records associated with student financial aid and student-records processing in the Oracle Grants and Student Systems (IGF) product family. The package follows Oracle's standard table-handler pattern, providing a controlled procedural interface so that forms, concurrent programs, and custom code can insert, lock, update, delete, and validate rows without issuing direct DML against the base table. The package is declared with AUTHID CURRENT_USER, meaning that privileges are evaluated against the invoking schema rather than the definer, so any caller must hold the necessary object grants on the underlying table and its foreign-key parents. The header comment, $Header: IGFAI43S.pls 115.5 2002/11/28, confirms the package has been stable since the 11i era and is reused unchanged across 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • INSERT_ROW — Inserts a new personal note record into IGF_AP_PERS_NOTE, returning the generated ROWID and reference number through NOCOPY OUT parameters.
  • LOCK_ROW — Acquires a row-level lock on an existing record, used by the Oracle Forms framework before an update or delete to enforce optimistic locking.
  • UPDATE_ROW — Updates the columns of an existing personal note identified by its ROWID, reference number, base identifier, and note type.
  • ADD_ROW — Combines the insert and lock semantics so that a record is created and immediately available for further manipulation within the same transaction.
  • DELETE_ROW — Removes a personal note record identified by its ROWID.
  • GET_PK_FOR_VALIDATION — Boolean function that validates whether a supplied reference number corresponds to an existing primary key.
  • GET_FK_IGS_PE_NOTE_TYPE — Foreign-key validation routine for the PE_NOTE_TYPE column, confirming that the note type value passed in exists in the IGS_PE_NOTE_TYPE reference table.
  • GET_FK_IGF_AP_FA_BASE_REC — Foreign-key validation routine for the BASE_ID column, confirming that the base record referenced exists in IGF_AP_FA_BASE_REC.
  • BEFORE_DML — Centralized pre-DML trigger body that populates WHO columns (creation date, created by, last update date, last updated by, last update login) and enforces validation logic across all DML paths.

Tables Accessed

The package reads and writes the single documented table IGF_AP_PERS_NOTE, accessed through the APPS synonym. Business data — base identifier, note type, short description, and response responsibility — is persisted there. Foreign-key validation procedures reference parent objects: GET_FK_IGS_PE_NOTE_TYPE confirms the note type against the IGS_PE_NOTE_TYPE lookup, and GET_FK_IGF_AP_FA_BASE_REC confirms the relationship to the IGF_AP_FA_BASE_REC financial-aid base record. These cross-references maintain referential integrity without requiring the caller to query the parent tables directly.

Usage Notes

IGF_AP_PERS_NOTE_PKG is typically invoked from the Oracle Forms interface that maintains personal notes for student financial-aid records, where the standard table-handler wiring calls LOCK_ROW, UPDATE_ROW, INSERT_ROW, and DELETE_ROW as the user navigates and saves blocks. Concurrent programs and custom PL/SQL that need to create or maintain note records call the same procedures so that WHO columns and foreign-key checks are handled consistently. One other packaged object in the APPS schema references this package, indicating reuse within the IGF module. The get_fk_igs_pe_note_type routine, which the search term references, is the standard validation hook the Forms layer calls to verify a PE_NOTE_TYPE value before accepting the row; developers extending the form or writing integration code should call it rather than querying IGS_PE_NOTE_TYPE directly.