Results for “igs_ad_apl_rvpf_rsl_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The package body APPS.IGS_AD_APL_RVPF_RSL_PKG is a member of the Oracle E-Business Suite Student System (formerly Student Records / Admissions) module, delivered under the APPS schema in EBS 12.1.1 and 12.2.2. Its object name decomposes as IGS (Student System), AD (Admissions), APL (Applicant), RVPF (Review Profile), and RSL (Result). The package therefore supports the storage and maintenance of applicant review profile results — the outcome records produced when an admissions review profile is applied to an applicant. It functions as a generated, table-handler style API providing row-level insert, update, delete, locking, primary/unique/foreign-key validation, and a BEFORE_DML trigger helper around the entity IGS_AD_APL_RVPF_RSL and its translation/extension table. ETRM classifies the API as OTHER, indicating it is an internal supporting package rather than a formal public business API; it is intended primarily for use by generated Forms, triggers, and dependent packages within the Admissions subsystem.

Key Procedures and Functions

The documented ETRM metadata lists eleven procedures/functions, forming the standard DML and validation surface of an EBS table-handler package:

• INSERT_ROW — Inserts a new review profile result row into the base table, populating WHO columns via FND_GLOBAL.
• LOCK_ROW — Issues a SELECT ... FOR UPDATE against the primary key to serialize concurrent modification of an existing result row.
• UPDATE_ROW — Updates an existing row identified by primary key, applying optimistic locking semantics through the WHO audit columns.
• ADD_ROW — Convenience wrapper combining existence check and insert, used by the Forms layer when creating new results.
• DELETE_ROW — Performs a physical delete of the row (and, where applicable, its child translation rows) after foreign-key validation.
• GET_PK_FOR_VALIDATION — Returns the primary key for a row so that callers can validate identity before DML.
• GET_UK_FOR_VALIDATION — Returns the unique key used to detect duplicates and to enforce the alternate unique constraint on the entity.
• GET_FK_IGS_AD_APL_REV_PRF — Retrieves the foreign key value linking the result row to its parent applicant review profile definition (IGS_AD_APL_REV_PRF_PKG).
• GET_FK_IGS_AD_CODE_CLASSES — Retrieves the foreign key value referencing the classification code (IGS_AD_CODE_CLASSES).
• GET_FK_IGS_AD_RATING_SCALES — Retrieves the foreign key value referencing the rating scale (IGS_AD_RATING_SCALES) used by the review profile.
• BEFORE_DML — Shared pre-DML routine invoked by Forms triggers and by the API itself to enforce business rules and default WHO columns prior to insert/update/delete.

Standard error reporting is handled through APP_EXCEPTION, FND_MESSAGE, and IGS_GE_MSG_STACK, following the conventional EBS message-stack pattern.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

• IGS_AD_APL_RVPF_RSL — The base transactional table holding applicant review profile result rows; primary DML target.
• IGS_AD_APL_RVPF_RSL_S — The corresponding translation/synonym table used for descriptive columns and language-specific attributes.
• IGS_AD_CODE_CLASSES — Reference table for admissions classification codes; read for FK validation via IGS_AD_CODE_CLASSES_PKG.
• IGS_AD_RATING_SCALES — Reference table for rating scales; read for FK lookup and validation via IGS_AD_RATING_SCALES_PKG.

Dependencies also include IGS_AD_APL_REV_PRF_PKG, which supplies the parent review-profile validation logic, and FND_GLOBAL for the WHO session context.

Usage Notes

This package is not intended for direct invocation by end users. It is typically called from the Admissions Forms module (the applicant review profile result window) and from BEFORE INSERT OR UPDATE OR DELETE database triggers defined on IGS_AD_APL_RVPF_RSL. Custom extensions to admissions review results should invoke INSERT_ROW, UPDATE_ROW, and DELETE_ROW rather than issuing raw DML, so that WHO columns, foreign-key validation, and message-stack error handling are consistently applied. ETRM records the package as not referenced by any database object other than its declared dependent packages and referenced by one other package, confirming its role as a leaf-level supporting unit. Because the object is VALID in the delivered 12.1.1/12.2.2 ETRM metadata, no customization of the package body is recommended; changes should be made through supported personalization or extension points. Callers must ensure the correct FND_GLOBAL session context is established before invocation, as the package relies on it for audit stamping and validation of the operating unit and language.