Search Results igs_ad_app_intent_s

Overview

The APPS.IGS_AD_APP_INTENT_PKG package body is a core member of the Oracle E-Business Suite (EBS) Student System Admissions (AD) product family. It provides the database-level business logic that governs applicant intent records held in the Admissions application. In the 12.1.1 and 12.2.2 releases the package carries a status of VALID in the APPS schema and is classified as an OTHER API, meaning it is an internally consumed procedural unit rather than a formally published public interface. Its central role is to encapsulate the insert, update, delete, locking, and validation behaviour required by the IGS_AD_APP_INTENT entity so that forms, concurrent programs, and other packages do not manipulate the underlying tables directly.

Key Procedures and Functions

The documented package exposes eleven procedures and functions that together implement a standard table-handler pattern.

• INSERT_ROW — performs the physical insertion of a new applicant intent record.
• UPDATE_ROW — applies modifications to an existing record.
• ADD_ROW — the user-facing entry point that accepts a new intent and orchestrates the creation logic.
• DELETE_ROW — removes a record that is no longer required.
• LOCK_ROW — acquires a row-level lock to serialise concurrent amendment.
• GET_PK_FOR_VALIDATION — resolves the primary key value used during validation.
• GET_UK_FOR_VALIDATION — resolves the unique key value used during validation.
• GET_FK_IGS_AD_CODE_CLASSES — resolves the foreign key relationship to the code classes entity.
• GET_FK_IGS_AD_APPL — resolves the foreign key relationship to the application entity.
• CHECK_CONSTRAINTS — validates data against the business and referential constraints that apply to the entity.
• BEFORE_DML — executes pre-insert and pre-update logic such as defaulting, auditing, and column population.

Tables Accessed

The package reads and writes two base schema objects, both accessed through APPS synonyms. IGS_AD_APP_INTENT is the primary transaction table for applicant intent, and the package performs its full lifecycle of inserts, updates, deletes, and locks against it. IGS_AD_APP_INTENT_S is the corresponding shadow or sequence-support object, referenced by the type definition layer. The metadata additionally records dependencies on IGS_AD_APPL_PKG and IGS_AD_CODE_CLASSES_PKG, confirming that applicant and code-class validation are delegated rather than duplicated. Supporting calls to FND_MESSAGE, FND_GLOBAL, IGS_GE_MSG_STACK, IGS_AD_GEN_002, and IGS_SC_GEN_001 show that error messaging, session context, and generic Admissions utilities are used throughout.

Usage Notes

Because the package is not referenced by any other database object, invocations flow inward: Admissions forms and other packages call it, but it calls nothing back into them. The documented dependency list shows that six other packages reference IGS_AD_APP_INTENT_PKG, so it is a shared building block. Typical invocation points are the Admissions maintenance form, validation logic in the Admissions setup, and any custom code that must create or amend applicant intent records. Customisations should call ADD_ROW, UPDATE_ROW, and DELETE_ROW rather than issuing DML against IGS_AD_APP_INTENT directly, so that BEFORE_DML, CHECK_CONSTRAINTS, and the key-resolution routines execute as designed. Error conditions are surfaced through the standard EBS message stack, which calling code should inspect after each invocation.