Search Results igs_uc_expunge_app




Overview
Explore in AI Chat

Overview

IGS_UC_EXPUNGE_APP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the data lifecycle management operations of the Oracle Student System (formerly Oracle iRecruitment/Student Administration), specifically within the Universities and Colleges (UC) module that handles admissions applications. The package is classified in the ETRM repository as an "OTHER" API, indicating it is not part of a formally published public API set but rather an internal utility or batch-processing program.

The term "expunge" is significant. In the higher-education context, expunging refers to the controlled removal, archiving, or purging of applicant records and their associated data. This package therefore serves as a housekeeping and data-retention instrument, allowing institutions to comply with data protection policies, manage storage growth, and clear obsolete application records after the admissions cycle has concluded.

At the time of documentation, the package is recorded with a VALID status in both the 12.1.1 and 12.2.2 ETRM repositories, and it exposes a single documented program unit. Its dependency footprint is limited to SYS.STANDARD and the compiled package body itself, with no other APPS packages referencing it, which confirms its role as a terminal consumer rather than a shared library.

Key Procedures and Functions

The ETRM metadata records exactly one program unit within IGS_UC_EXPUNGE_APP:

  • EXPUNGE_PROC — The sole documented procedure. Its purpose is to execute the expunge operation: identifying candidate application records that meet the relevant retention or purge criteria and removing or archiving them along with their dependent child rows. As a PROC rather than a function, it returns no value and is intended to be invoked for its side effects on the underlying tables.

No public function variants, overloads, or additional helper procedures are recorded in the ETRM extract. Because the parameter list is not documented, the exact signature cannot be stated; in practice the procedure is likely driven by configuration values or selection criteria supplied at invocation time rather than by a rich argument list. Consumers should inspect the package specification on the target instance before attempting to call it directly.

Tables Accessed

IGS_UC_EXPUNGE_APP references a broad set of tables through APPS synonyms. These fall into three functional groups and indicate the scope of a typical expunge operation.

The presence of both UC external (UCAS) staging data and internal AD application data confirms that expunging must respect referential integrity across the full admissions chain.

Usage Notes

Because no other APPS package references IGS_UC_EXPUNGE_APP, it is not invoked by the standard application modules during normal admissions processing. Its callers are therefore expected to be one of the following:

  • A concurrent program registered against the package procedure, scheduled by administrators to run period-end or retention-driven cleanups.
  • Custom code or a wrapper package developed by the institution to sequence the expunge with backups, audits, or staged deletes.
  • An administrative maintenance script executed by DBAs during data migration, testing refreshes, or archive rollovers.

Given the destructive nature of an expunge and the absence of a documented parameter interface, it is strongly recommended that any invocation be preceded by a verified backup and, where possible, executed first on a non-production clone. The broad table footprint means a failure mid-execution could leave partially purged data, so transactional boundaries and error logging should be considered essential. On R12.2.2, where online patching and editioning apply, care must also be taken that calls target the correct edition of the package body.