Results for “resp_val_ca_sca_acai”

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

Overview

IGS_RE_VAL_CA is a validation package in the Oracle EBS Student Systems (Higher Education) product family, specifically within the Research Candidature (IGS_RE) module. Its name follows the module convention: "IGS_RE" identifies the Research Candidature schema component, "VAL" indicates a validation program unit, and "CA" denotes Candidature. The package body encapsulates the business rules that govern the integrity of candidature records and their related admission, submission, and outcome data.

The package serves the Research Candidature workflow by enforcing date and status validation logic against candidate records. Its most prominent documented function, ADMP_VAL_ACAI_COMM, validates the proposed commencement date (IGS_AD_PS_APPL_INST.PRPSD_COMMENCEMENT_DT) for an admission application instance. The validations confirm that a corresponding IGS_RE_CANDIDATURE record exists, that the proposed commencement date falls after the earlier of the course start date or the admission academic period's earliest research start date, and it issues a warning where the proposed date precedes an acceptable threshold. This date-centric validation protects the consistency of candidature lifecycle data across the Research and Admissions modules.

The package header comment references Oracle bug fixes 1956374 and 2661533, indicating longstanding maintenance, with the latter introducing a legacy flag (p_legacy) to several validation functions to preserve backward compatibility with earlier data conventions.

Key Procedures and Functions

• ADMP_VAL_CA_COMM — Validates the admission proposed commencement date against candidature existence and course/academic period start dates. This is the principal documented entry point excerpted in the source listing (referenced historically as removed and re-pointed under bug 1956374).
• RESP_VAL_CA_UPD — Validation associated with updating responsory or candidature records.
• RESP_VAL_CA_TOPIC — Validates research topic data for a candidature; per the change history, this routine accepts the p_legacy parameter introduced under bug 2661533.
• RESP_VAL_CA_ACAI — Validates admission application instance data in relation to candidature records.
• RESP_VAL_CA_MAXSBMSN — Validates the maximum submission date for a candidature; accepts p_legacy.
• RESP_VAL_CA_MINSBMSN — Validates the minimum submission date; accepts p_legacy.
• RESP_VAL_CA_SCA — Validates student course attempt data linked to a candidature.
• RESP_VAL_CA_ACAI_DEL — Deletion-time validation for admission application instance records.
• RESP_VAL_CA_SCA_DEL — Deletion-time validation for student course attempt records.
• RESP_VAL_GTCC_CLOSED — Validates whether a government or course-related code is closed, blocking processing where appropriate.
• RESP_VAL_CA_SCA_ACAI — Combined validation reconciling student course attempt and admission application instance data.

All functions return BOOLEAN, with output parameters carrying generated messages and, where applicable, a candidature sequence number.

Tables Accessed

• IGS_AD_OU_STAT — Admission organizational unit status; used to confirm the institutional unit's validity or status during validation.
• IGS_EN_SPA_AWD_AIM — Enrolment special award aim data; referenced when validating awards or aims tied to candidature or course attempt records.
• IGS_RE_GV_TOA_CLS_CD — Research type-of-award classification code; used to validate the classification assigned to a research candidature.

These referenced tables are accessed through APPS synonyms, consistent with standard EBS schema conventions.

Usage Notes

IGS_RE_VAL_CA is classified as an OTHER API and is not itself an exposed public interface. It is referenced by five other packages, meaning it is typically invoked indirectly: forms and concurrent programs within the Research Candidature and Admissions modules call the higher-level packages, which in turn call these validation routines before committing data. Custom code should not call these functions directly unless performing equivalent validation within the same transactional context, and callers must be prepared to interpret the BOOLEAN return value and the OUT message name to present meaningful errors to users.