Search Results igs_ad_ofr_resp_stat_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGS_AD_OFR_RESP_STAT_PKG package body is a component of the Oracle E-Business Suite (EBS) Student System / Student Information Management (SIS) product family, specifically within the Admissions (IGS_AD) module. Its name indicates that it manages the Offer Response Status entity — the records that track how an applicant responds to an admission offer extended by an institution, such as acceptance, decline, or deferral. The package is an automatically generated table-handler (also referred to as a TAPI-style or "C" API) associated with the IGS_AD_OFR_RESP_STAT table. It encapsulates the DML and validation logic required to insert, update, delete, and lock rows in that table, while enforcing foreign-key and lookup integrity and raising user-facing messages through the Oracle message stack. As a PACKAGE BODY in the APPS schema with VALID status, it is a core, supported repository object in both EBS 12.1.1 and 12.2.2 environments, and its API classification is listed as OTHER (that is, a table-handler rather than a public business API).

Key Procedures and Functions

The documented interface exposes nine procedures and functions, all centred on row-level manipulation and validation of the offer response status data:

  • INSERT_ROW — Performs the primary insert of a new offer response status record, populating the table columns and capturing who/when audit information.
  • UPDATE_ROW — Modifies an existing record, typically used when an applicant changes their response or when administrative corrections are required.
  • DELETE_ROW — Removes an offer response status record, subject to referential-integrity checks against dependent entities.
  • LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) to prevent concurrent modification during a transaction.
  • ADD_ROW — A higher-level convenience or "add" wrapper that orchestrates validation and insertion in a single call.
  • GET_PK_FOR_VALIDATION — Resolves and returns the primary key used by the validation routines, ensuring a unique row is identified before constraints are tested.
  • GET_FK_IGS_LOOKUPS_VIEW — Retrieves the foreign-key value(s) referencing the IGS lookups view, supporting validation of code-based columns.
  • CHECK_CONSTRAINTS — Runs the package's constraint and business-rule validation logic, including lookup and foreign-key verification, and raises errors via FND_MESSAGE and IGS_GE_MSG_STACK.
  • BEFORE_DML — A pre-DML hook that fires mandatory validations before any insert, update, or delete, and records the DML action for auditing.

Tables Accessed

The package's principal data store is the IGS_AD_OFR_RESP_STAT table, accessed through an APPS synonym. This is the entity that holds offer response status definitions or applicant-level response records. Validation support is drawn from the IGS_AD_VAL_AORS validation package and the IGS_LOOKUPS_VIEW_PKG, which supplies lookup-code enforcement. Utility dependencies include APP_EXCEPTION and IGS_GE_MSG_STACK for error propagation, and FND_MESSAGE/FND_GLOBAL for user-facing messages and session/audit context. The package also references helper logic in IGS_AD_PS_APPL_INST_PKG, indicating interaction with the application-instance data that underpins admission offers.

Usage Notes

This package body is not referenced by any other database object per the ETRM metadata, confirming it is an entry-point table handler rather than an internal subroutine. It is typically invoked by the corresponding Oracle Forms screen (maintained in the Admissions application) when users create or maintain offer response status records, and by concurrent programs or custom PL/SQL that need to respect the table's validation rules. Because it is not a public API, direct custom calls should replicate the standard handler pattern: obtain the primary key, call BEFORE_DML or CHECK_CONSTRAINTS, then perform ADD_ROW, UPDATE_ROW, or DELETE_ROW within an explicit transaction. The dependent objects listed — including five packages that reference it — should be reviewed for upstream or downstream impact before any extension or modification.