Search Results igs_uc_offer_conds_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGS_UC_OFFER_CONDS_PKG package body is a server-side PL/SQL component within the Oracle E-Business Suite UC (Universities and Colleges) product family. Its purpose is to encapsulate the data manipulation logic and row-level locking behaviour for the IGS_UC_OFFER_CONDS entity, which stores conditions attached to offers made to applicants through the UCAS admissions process. In the ETRM classification the object is registered as an OTHER API, indicating that it is an internal supporting package rather than a formally published public interface, yet it remains a stable and dependency-bearing element of the 12.1.1 and 12.2.2 releases.

The package body is recorded as VALID in the APPS schema and acts as the procedural layer behind the offer-conditions table, centralising the standard insert, update, delete, lock, and pre-DML validation patterns used consistently across IGS packages. Because it is not referenced by any other database object, it functions as a leaf-level utility invoked directly by forms or sibling packages rather than through an inheritance chain.

Key Procedures and Functions

The package body exposes seven documented program units, each conforming to the conventional IGS table-handler pattern:

  • INSERT_ROW — inserts a new offer-conditions record into the underlying table.
  • UPDATE_ROW — applies modifications to an existing offer-conditions record.
  • DELETE_ROW — removes an existing offer-conditions record.
  • LOCK_ROW — acquires a row-level lock, typically via SELECT ... FOR UPDATE, to enforce concurrency control before modification.
  • ADD_ROW — provides the user-facing wrapper that performs validation, locking, and dispatch to the insert or update path as appropriate.
  • GET_PK_FOR_VALIDATION — retrieves the primary key of the target record so that validation logic can confirm existence and identity prior to DML.
  • BEFORE_DML — performs the mandatory pre-DML checks and derived-column population common to all write operations.

No parameter signatures are reproduced here because the ETRM metadata documents unit names and purposes only.

Tables Accessed

The only documented table referenced via an APPS synonym is IGS_UC_OFFER_CONDS. This table holds the condition records associated with UCAS offers, and the package body both reads from and writes to it. Read access supports the validation, locking, and primary-key retrieval operations (GET_PK_FOR_VALIDATION, LOCK_ROW, BEFORE_DML), while write access supports INSERT_ROW, UPDATE_ROW, and DELETE_ROW. The remaining dependencies are on supporting infrastructure packages and utilities rather than on additional application tables.

Usage Notes

IGS_UC_OFFER_CONDS_PKG is typically invoked from the Oracle Forms-based maintainance screens for UC offers and conditions, and from the three sibling packages that reference it — notably the application-choices and condition-details packages that share the same processing model. Because the ETRM records it as an OTHER API, customisations should treat it as an internal implementation detail: it may be called directly where a client extension must persist offer conditions, but the recommended approach is to rely on the surrounding IGS API surface. Support dependencies on APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, and IGS_GE_MSG_STACK indicate that error handling, session context, and message-stack conventions are consistently applied, so any custom caller should be prepared to interpret standard FND and IGS error messages raised by these units.