Search Results admp_val_aal_exists

Overview

IGS_AD_VAL_AAL is a PL/SQL validation package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Student System (formerly Oracle iLearning/Recruiting & Admissions) modules. It is classified as API classification OTHER in the ETRM repository, indicating that it is an internal validation routine rather than a formally published public API. The package is declared with AUTHID CURRENT_USER, meaning its unqualified database object references are resolved against the privileges of the calling schema rather than the definer, a convention typical of IGS validation packages intended to be invoked within the security context of the calling application module.

The package encapsulates business rules governing correspondence types associated with admission application letters. These rules ensure that letters generated during the admissions lifecycle use a correspondence type that is appropriate for the given admission category, admission process type, and application state, and that duplicate unsent letters are not created for the same person and application.

Key Procedures and Functions

• ADMP_VAL_AAL_CORT — Validates the correspondence type for an admission application letter. It evaluates whether the specified correspondence type is permissible given the admission category and the admission process type, returning a Boolean result and populating a message name output parameter with any error identifier when validation fails.
• ADMP_VAL_AAL_EXISTS — This is the function associated with the user search term admp_val_aal_exists. It validates whether an unsent admission application letter already exists for the same correspondence type, keyed by person and admission application number. It returns a Boolean result and sets a message name output parameter when a duplicate condition is detected. The function is intended to prevent redundant letter records prior to generation or dispatch.
• CORP_VAL_CORT_CLOSED — Validates the correspondence type closed indicator. It determines whether the referenced correspondence type is flagged as closed, returning a Boolean result and a message name output for error handling, thereby blocking use of retired correspondence types.

All three documented functions follow the same convention: they return BOOLEAN and expose an OUT NOCOPY VARCHAR2 message name parameter so that callers can translate validation failures into user-facing messages via the standard message dictionary.

Tables Accessed

The package reads from four tables through APPS synonyms:

• IGS_AD_APPL_LTR — Admission application letter records; the primary table examined by ADMP_VAL_AAL_EXISTS when checking for unsent letters.
• IGS_AD_PRCS_CAT_LTR — Maps admission process types and categories to permitted correspondence letters, supporting ADMP_VAL_AAL_CORT.
• IGS_CO_S_LTR — Correspondence setup for letters, providing validation attributes used in correspondence type checks.
• IGS_CO_TYPE — Correspondence type definitions, including the closed indicator validated by CORP_VAL_CORT_CLOSED.

The package is documented as read-oriented validation logic; the metadata does not indicate direct inserts or updates to these tables.

Usage Notes

IGS_AD_VAL_AAL is referenced by five other packages, confirming its role as a shared validation dependency within the admissions and correspondence processing stack. It is typically invoked from admissions application forms, correspondence generation routines, and concurrent programs that create or release admission letters, as well as from custom extensions that enforce the same duplicate-letter and correspondence-type constraints. Because the functions return BOOLEAN and use an OUT message parameter, callers must handle the return value in PL/SQL and map the message name to a translated error string. The package header identifies version 115.4 with a last ship date of 2002, reflecting its stability across the 12.1.1 and 12.2.2 releases. Custom code should treat it as an internal validation utility and avoid direct dependency where a formally published API is available.