Search Results igs_uc_applicants_s1

Overview

The APPS.IGS_UC_APPLICANTS_PKG package body is a core data-access and maintenance component within the Oracle E-Business Suite (EBS) Student Systems / Recruiting and Admissions ("UC") module. Its principal business function is to manage applicant records held in the IGS_UC_APPLICANTS entity, which stores the primary applicant details captured by the admissions and application-tracking process. The package encapsulates the standard Oracle Forms "table handler" pattern, exposing a consistent set of DML and validation routines that Oracle Forms-based applicant maintenance screens invoke automatically during query, insert, update, delete, and row-locking operations. In EBS 12.1.1 and 12.2.2 the package is registered with a status of VALID in the APPS schema and is classified as an OTHER API, indicating it is an internal supporting object rather than a public, published interface. The presence of a GET_..._FOR_VALIDATION family and LOCK_ROW/BEFORE_DML routines confirms the package is tightly coupled to Forms-level record processing and referential integrity enforcement against related UC sub-entities.

Key Procedures and Functions

The ETRM metadata documents ten procedures/functions. Each serves a specific role in the Forms transaction lifecycle:

• INSERT_ROW — Performs the physical insert of a new applicant row into IGS_UC_APPLICANTS, applying standard WHO columns and default audit values.
• LOCK_ROW — Obtains a row-level lock on the target applicant record, supporting Forms optimistic concurrency control.
• UPDATE_ROW — Applies modifications to an existing applicant record after validation.
• ADD_ROW — Initialises a new record buffer with defaulted field values prior to insert.
• DELETE_ROW — Removes an applicant record, typically guarded by integrity checks against child tables.
• GET_PK_FOR_VALIDATION — Resolves and validates the primary key of the applicant entity.
• GET_UK_FOR_VALIDATION — Validates the unique key, ensuring duplicate applicant identifiers are not introduced.
• GET_FK_IGS_UC_DEFAULTS — Validates the foreign-key relationship to the UC defaults entity.
• GET_FK_IGS_PE_PERSON — Validates the foreign-key relationship to the person entity in the IGS_PE (People) schema.
• BEFORE_DML — A trigger-style routine ensuring all required validations and derivations execute immediately before the DML operation.

Tables Accessed

The package operates on three documented tables via APPS synonyms. IGS_UC_APPLICANTS is the primary base table holding applicant data and is the target of insert, update, delete, and lock operations. IGS_UC_APPLICANTS_S1 is a secondary table — most likely a sequence/ID or shadow/summary table — referenced by the package, and it is the object implicated by the user's search term "igs_uc_applicants_s1". DUAL supplies the standard single-row source used by key-generation and validation lookups. The package depends on supporting packages including IGS_PE_PERSON_PKG (person creation/validation), IGS_UC_APP_* sub-packages (addresses, choices, clearing, names, referees, results, stats), IGS_UC_DEFAULTS_PKG, IGS_UC_FORM_QUALS_PKG, IGS_GE_MSG_STACK and FND_MESSAGE (message/error handling), and APP_EXCEPTION for exception propagation.

Usage Notes

This package is normally invoked implicitly by Oracle Forms applicant maintenance blocks through the standard table-handler triggers (PRE-INSERT, ON-LOCK, etc.); developers rarely call it directly. It may also be referenced by concurrent programs or custom PL/SQL that load or migrate applicant data, provided the caller honours the FK validation routines and the BEFORE_DML sequence. Because it is classified OTHER and is not referenced by other database objects, it should be treated as an internal implementation detail rather than a supported integration interface. The referenced-by count of twelve packages indicates it sits within a broader UC applicant subsystem; modifications should be validated against those dependents and against the IGS_UC_APPLICANTS_S1 object identified in the search.