Search Results igr_i_appl_pkg




Overview
Explore in AI Chat

Overview

IGR_I_APPL_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema, delivered as part of the Oracle Student System / Student Records (IGR and IGS product families). Its package body implements the core maintenance logic for applicant records held in the IGR_I_APPL_ALL table. Functionally, it behaves as a generated-style schema handler: it encapsulates row-level insert, update, delete, locking, primary key derivation, foreign key validation, and constraint checking for the applicant entity, and it delegates referential checks to the parent entity packages that own the referenced data. The package is classified as OTHER rather than as a public API, which indicates that its procedures are intended primarily for internal use by the Oracle forms and by other IGR packages rather than as a supported integration interface.

Key Procedures and Functions

The package body exposes twelve documented procedures and functions:

  • INSERT_ROW — Performs the physical insert of a new applicant row, populating the mandatory audit and business columns and obtaining sequence-based identifiers.
  • UPDATE_ROW — Applies changes to an existing applicant row, including audit stamping of the last-updated user and date.
  • ADD_ROW — Higher-level entry point that orchestrates validation and insert logic for a new applicant, typically called from the block-level DML handler.
  • DELETE_ROW — Removes an applicant row following the deletion of dependent child records.
  • LOCK_ROW — Issues a row lock for the specified applicant, ensuring concurrency safety during form-based update or delete operations.
  • BEFORE_DML — Central pre-DML routine that executes constraint checking before insert, update, or delete processing.
  • CHECK_CONSTRAINTS — Evaluates business and integrity constraints for the applicant record, restricting the operation when validation fails.
  • GET_PK_FOR_VALIDATION — Retrieves the primary key value used when validating a foreign key relationship.
  • GET_FK_IGS_PE_PERSON — Validates and resolves the person foreign key against the IGS_PE_PERSON_BASE_V view.
  • GET_FK_IGS_CA_INST_REL — Validates the institution relationship foreign key against the IGS_CA_INST_REL table.
  • GET_FK_IGR_I_ENTRY_LVLS — Validates the entry level foreign key against the entry level reference data.
  • GET_FK_IGS_AD_CODE_CLASSES — Validates the admission code class foreign key against the code class table.

Each GET_FK routine delegates to the recognised owner package for the parent entity, such as IGS_PE_PERSON_PKG, IGS_CA_INST_REL_PKG, IGR_I_ENTRY_LVLS_PKG, and IGS_AD_CODE_CLASSES_PKG, so that validation rules remain centralised.

Tables Accessed

  • IGR_I_APPL_ALL — The base applicant table and the primary target of all insert, update, delete, and lock operations.
  • IGR_I_APPL_S — The sequence or secondary applicant structure used to derive identifiers and support row generation.
  • IGS_PE_HZ_PARTIES — The person and party data source consulted to resolve and validate the applicant-to-person relationship.

Usage Notes

IGR_I_APPL_PKG is not referenced by any database object, but it is referenced by six other packages within the IGR family, confirming its role as an internal dependency rather than a top-level integration API. In practice it is invoked from the Oracle Forms applicant maintenance blocks, where BEFORE_DML, CHECK_CONSTRAINTS, ADD_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW execute as part of the standard transactional workflow. It also supports import and conversion routines that load applicant data and require the same validation and audit semantics. Because several procedures depend on FND_GLOBAL for the current user context, the package must execute within an APPS-initialised session. Custom code should treat these procedures as internal; direct calls bypass the form-level navigation and control structures and risk inconsistent applicant state if the surrounding validation sequence is not reproduced.