Results for “igs_ad_appl_eval_pkg”

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

Overview

The APPS.IGS_AD_APPL_EVAL_PKG package body is a core component of the Oracle E-Business Suite Student System (Advanced Admissions / Admissions product family). It encapsulates the business logic governing applicant evaluations — the recorded assessments, ratings, and decisions applied to a prospective student's application during the admissions review cycle. Evaluations typically capture which evaluator assessed an application, the rating scale used, the outcome value, sequence ordering, and associated comments.

This package is the generated PL/SQL layer that supports the IGS_AD_APPL_EVAL entity and its intersection with application instances, reviewer profiles, and rating scales. The body implements the standard table-handler pattern (insert/lock/update/delete plus validation and DML event hooks) and augments it with evaluation-specific functions such as finding the previous sequence number and the next evaluation in a review chain. It is classified in ETRM as an OTHER API, meaning it is primarily consumed internally by the admissions subsystem rather than documented as a public integration interface.

Key Procedures and Functions

• INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW — the standard row maintenance primitives that persist changes to the underlying evaluation table and enforce concurrency control via a lock operation.
• ADD_ROW — a convenience wrapper that adds a new evaluation record, typically applying defaulting and sequencing before delegating to INSERT_ROW.
• GET_PK_FOR_VALIDATION — resolves the primary key of an evaluation record, used to validate that the row exists before further processing.
• GET_FK_IGS_AD_RS_VALUES, GET_FK_IGS_AD_CODE_CLASSES, GET_FK_IGS_AD_PS_APPL_INST, GET_FK_IGS_PE_PERSON, GET_FK_IGS_AD_RATING_SCALES — foreign-key resolution routines that validate and derive the related rating value, code class, application instance, person, and rating scale identifiers associated with an evaluation.
• CHECK_CONSTRAINTS, BEFORE_DML, AFTER_DML — constraint enforcement and pre/post-DML event handlers that apply business rules and maintain derived data around insert, update, and delete operations.
• WF_EVALUATOR_VALIDATION — validates the evaluator (reviewer/profile) assignment, supporting workflow-driven evaluation approval.
• NOTIFICATION_ON_DELETE — raises a notification (via the message/workflow stack) when an evaluation is removed, preserving the audit trail expected in admissions decisions.
• FIND_PREV_SEQ_NUMBER, FIND_NEXT_EVAL — navigation helpers used to traverse the ordered sequence of evaluations for an application, establishing the previous and next records in the review chain.

Tables Accessed

• IGS_AD_APPL_EVAL / IGS_AD_APPL_EVAL_S — the base and translated (TL) tables that store the evaluation records themselves; these are the primary read/write targets.
• IGS_AD_APL_REV_PRF_ALL — applicant reviewer profile data, used to validate and resolve the evaluator assigned to an evaluation.
• IGS_AD_APPL_ARP — application/admissions review profile linkage, providing context for which reviewer profile governs the evaluation.
• IGS_AD_PS_APPL_INST_ALL — application instance records, supplying the admission instance to which evaluations are attached.

Foreign-key and reference data are additionally obtained through the referenced packages (IGS_AD_RS_VALUES_PKG, IGS_AD_CODE_CLASSES_PKG, IGS_PE_PERSON_PKG, IGS_AD_PS_APPL_INST_PKG), and error/warning handling relies on APP_EXCEPTION, FND_MESSAGE, FND_FILE, and IGS_GE_MSG_STACK.

Usage Notes

This package body is invoked indirectly through the Admissions forms and concurrent processes that manage application evaluations — for example, entering, sequencing, or deleting an evaluation in the applicant review UI, or running batch evaluation processing. Because the object carries a VALID status and is referenced by seven other packages (including IGS_AD_ASSIGN_EVAL_AI_PKG and the generated table handlers), it should be treated as an internal dependency rather than a standalone public API. Customizations should avoid calling the row-level routines directly; instead they should route through the higher-level admissions APIs so that BEFORE_DML, AFTER_DML, and the notification and validation logic execute in the intended order. Direct DML against the underlying tables bypasses the sequence-management and notification behavior implemented here.