Search Results igs_ad_acad_interest_pkg




Overview
Explore in AI Chat

Overview

The IGS_AD_ACAD_INTEREST_PKG package resides in the APPS schema and forms part of the Oracle E-Business Suite Student System (formerly Oracle Student System, now marketed as Oracle Student Administration / Campus Solutions heritage), specifically within the Admissions (AD) product family. Its name — Academic Interest — reflects the admissions concept of tracking an applicant's declared areas of academic interest, which may include intended majors, fields of study, or subject preferences captured during the application process.

The package is classified as an OTHER API type within the ETRM (E-Business Suite Technical Reference Manual) documentation set. This classification indicates that the package is not a formally published public API intended for external integration, but rather an internal package that supports the core admissions data model. It nonetheless exposes a structured set of procedures that together implement the standard CRUD (Create, Read, Update, Delete), locking, validation, and pre-DML processing behavior expected of a generated or template-driven table handler in the E-Business Suite environment. The object is reported with status VALID in Oracle EBS 12.1.1, and the same architectural pattern carries forward into 12.2.2, where the file system is replaced by the Web ADI/ADOP adoption model but the underlying PL/SQL package structures remain consistent.

Key Procedures and Functions

The documented interface exposes eleven procedures and functions. Their purposes are as follows:

  • INSERT_ROW — Inserts a new academic interest record into the underlying entity table.
  • UPDATE_ROW — Modifies an existing academic interest record.
  • DELETE_ROW — Removes an academic interest record.
  • ADD_ROW — Adds a row, typically invoked following successful validation, functioning as a higher-level insert wrapper.
  • LOCK_ROW — Acquires a row-level lock, commonly via SELECT ... FOR UPDATE, to enforce concurrency control during multi-user edits.
  • GET_PK_FOR_VALIDATION — Retrieves or derives the primary key value required for validation logic.
  • GET_UK_FOR_VALIDATION — Retrieves the unique key value used to validate uniqueness constraints before commit.
  • GET_FK_IGS_PS_FLD_OF_STUDY — Resolves the foreign key relationship to the IGS_PS_FLD_OF_STUDY (field of study) entity, confirming valid references.
  • GET_FK_IGS_AD_APPL — Resolves the foreign key relationship to the IGS_AD_APPL (admissions application) entity.
  • CHECK_CONSTRAINTS — Performs declarative validation of business and database constraints.
  • BEFORE_DML — Executes pre-insert/pre-update logic such as setting WHO columns, defaults, and audit fields.

Tables Accessed

The package operates against two documented tables accessed through APPS synonyms:

  • IGS_AD_ACAD_INTEREST — The primary transactional table storing the academic interest records associated with an application. INSERT_ROW, UPDATE_ROW, DELETE_ROW, and ADD_ROW all target this table.
  • IGS_AD_ACAD_INTEREST_S — The corresponding _S (secondary/language or audit) table, maintained in parallel to support translated or historical attribute storage consistent with the EBS multi-language table convention.

Foreign key lookups reference IGS_PS_FLD_OF_STUDY and IGS_AD_APPL, confirming the entity's place between an application and its chosen fields of study.

Usage Notes

The package is referenced by five other database objects — IGS_AD_APPL_PKG, IGS_AD_IMP_003, IGS_AD_INT_RECONSIDER, IGS_AD_SS_GEN_001, and IGS_AD_VAL_ACAI_FTR_OFFER — indicating that it is invoked from several admission processing flows. IGS_AD_APPL_PKG suggests integration during application creation or maintenance; IGS_AD_IMP_003 implies import or interface processing; IGS_AD_INT_RECONSIDER and IGS_AD_SS_GEN_001 point to self-service and reconsideration workflows; and IGS_AD_VAL_ACAI_FTR_OFFER indicates use in validation of future-term course offerings. In practice the package is most often called from Oracle Forms (the Admissions application forms), from concurrent programs performing bulk data loads, and from custom PL/SQL code that requires controlled insert, update, or validation of academic interest data. Because it is classified OTHER rather than a published API, direct custom invocation should be undertaken cautiously, and dependencies on the wrapper packages above should be considered when diagnosing behavior.