Search Results admp_upd_acai_lapsed




Overview
Explore in AI Chat

Overview

IGSADJ03 is a concurrent program within the Oracle E-Business Suite Student System module (IGS). Its user-facing name is Lapsed Admission Offers, and its internal description mirrors that title. In the ETRM metadata for release 12.2.2, the program is listed as Enabled: Yes, indicating that it remains available for submission in environments where the Student System product is installed — although the product itself is classified as Obsolete, meaning Oracle no longer actively develops or supports it and customers are expected to migrate to successor offerings such as Oracle Student Cloud or PeopleSoft Campus Solutions.

Functionally, IGSADJ03 processes admission offers that have passed their validity window without a response from the applicant. Such offers are considered "lapsed," and the program updates the associated admission application records to reflect that status. This is a routine housekeeping and data-integrity process: without it, expired offers would remain in an active state, distorting admission pipeline reporting, seat-count projections, and downstream enrollment or registration processing. The search term admp_upd_acai_lapsed corresponds directly to the underlying PL/SQL package referenced in the executable definition, confirming the program's role in updating lapsed admission application instances.

Execution Details

The documented execution method is PL/SQL Stored Procedure, with an Argument Method of Standard. The concurrent program is registered under the executable name IGSADJ03, and the execution file is recorded as:

The dotted notation indicates a packaged procedure: the package IGS_AD_GEN_012 exposes a stored procedure ADMP_UPD_ACAI_LAPSED, which Oracle Concurrent Manager invokes directly. Because the argument method is Standard, parameters passed to the program follow the normal concurrent program token mechanism rather than a descriptive flexfield or a custom argument form.

How to Run

IGSADJ03 is submitted through the standard Submit Request (SRS) window, typically from the responsibility that owns admission processing — most commonly an Admissions or Student System Administration responsibility. There is no evidence in the metadata of an Oracle Applications concurrent manager-exclusive or request-set-only restriction, so the program should be submittable on demand.

Because the metadata does not enumerate specific parameters, administrators should inspect the parameters form attached to the concurrent program definition in the target instance. In practice, the arguments for this class of program generally identify the academic period or admission term, an effective date or cutoff date defining which offers are to be treated as lapsed, and sometimes an institution or career code. Oracle recommends running the program during off-peak windows, since it performs set-based updates against admission application tables and can generate significant redo and undo volume on large applicant populations. Requests should be monitored through the Concurrent Requests and Requests views after submission.

Related Objects

The program operates in the same functional area as other IGS admission utilities that share the IGS_AD_GEN_012 package family. Objects typically associated with this process include:

  • The base admission application and admission offer tables that store offer status and expiry dates (for example, the IGS_AD_APPL and offer/response tables in the IGS schema).
  • Sibling concurrent programs in the IGSADJ series that handle related admission adjustments.
  • Admissions status reports and pipeline or conversion reports that read the offer status updated by this program.
  • Any customer-defined alerts or interfaces that consume lapsed-offer status to trigger communication with applicants.

Given the product's Obsolete classification, the primary practical recommendation is to avoid new dependency on IGSADJ03 and to verify behaviour carefully in any environment where legacy data must still be reconciled.