Search Results igs_ad_app_req_pkg




Overview
Explore in AI Chat

Overview

The IGS_AD_APP_REQ_PKG package is a PL/SQL component that resides in the APPS schema and is classified as a general-purpose API (API Classification: OTHER) within the Oracle E-Business Suite Student System (Advanced Degree / Admissions) module. Its primary business purpose is to manage data related to Application Requirements — the specific criteria, documents, or prerequisites that an applicant must satisfy in order to complete an admissions application. The package encapsulates the low-level DML operations for the IGS_AD_APP_REQ entity, allowing higher-level admissions processes to create, maintain, validate, and lock application requirement records without issuing raw SQL against the underlying tables.

Objects such as this are referenced by a broad cross-section of admissions logic, as evidenced by the nine dependent packages that call into it, including IGS_AD_APPL_PKG (the core application package), IGS_AD_CODE_CLASSES_PKG, IGS_AD_SS_APPL_FEE_PKG, and a series of generated and interface routines (IGS_AD_GEN_002, IGS_AD_GEN_015, IGS_AD_IMP_003, IGS_AD_INT_RECONSIDER, IGS_AD_SS_GEN_001, and IGS_AD_VAL_ACAI_FTR_OFFER). This dependency profile confirms that the package is a foundational table-handler for admissions requirement data, invoked both by data-entry forms and by batch/concurrent processing.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions within the package, oriented toward standard table-handler responsibilities:

  • INSERT_ROW — Inserts a new application requirement record into the base table, populating the primary key and mandatory attributes.
  • UPDATE_ROW — Updates an existing application requirement record with modified attribute values.
  • DELETE_ROW — Deletes an application requirement record identified by its primary key.
  • ADD_ROW — Provides a higher-level convenience wrapper that performs the required key assignment and insertion of a new row.
  • LOCK_ROW — Acquires a row-level lock on the specified application requirement record to enforce concurrency control during multi-step transactions.
  • GET_PK_FOR_VALIDATION — Retrieves the primary key of a record so that validation logic can confirm the row's existence and uniqueness before committing changes.
  • GET_FK_IGS_AD_CODE_CLASSES — Resolves the foreign key reference to the code-classes entity, supporting referential integrity checks and validation of requirement classifications.
  • GET_FK_IGS_AD_APPL — Resolves the foreign key reference to the parent admission application, ensuring each requirement is tied to a valid application.
  • CHECK_CONSTRAINTS — Validates the record against the business and referential constraints defined for the entity before DML is permitted.
  • BEFORE_DML — A pre-DML hook that performs common preparatory logic, such as defaulting WHO columns and validating state, prior to insert, update, or delete operations.

Tables Accessed

The package manipulates and references the following tables, accessed through APPS synonyms:

  • IGS_AD_APP_REQ — The base table storing application requirement records; the primary target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW.
  • IGS_AD_APP_REQ_S — The shadow/audit table associated with the base entity, used for tracking historical or translation-related changes.
  • IGS_AD_APPL_STAT — Stores application status information, used to validate the state of the parent application when processing requirements.
  • IGS_AD_CODE_CLASSES — Holds code-class definitions; accessed via GET_FK_IGS_AD_CODE_CLASSES to validate classification references.
  • IGS_FI_CONTROL_ALL — The Financials control table, used to verify system-level setup and control parameters.
  • FND_NEW_MESSAGES — The Oracle Application Object Library message repository, used to retrieve and raise user-facing validation and error messages.

Usage Notes

IGS_AD_APP_REQ_PKG is a server-side table handler and is not typically invoked directly by end users. It is called programmatically by the Admissions forms, concurrent programs, and interface routines that manage application data. Forms such as the application maintenance screens call these routines during record creation, modification, and deletion, while concurrent programs and interface processes (for example, IGS_AD_IMP_003 and the IGS_AD_GEN_* generators) use them to bulk-load or transform requirement data. Custom extensions that need to maintain application requirements should call this package rather than issuing direct DML, so that constraint checks, key resolution, locking, and message handling are consistently enforced. Because the package depends only on SYS.STANDARD and is relied upon by nine dependent objects, any modification should be treated as a change to a shared foundational API within the Student System admissions schema.