Search Results create_perstat_row




Overview
Explore in AI Chat

Overview

IGS_AD_SS_APPL_UPD_PAGE is an Oracle EBS Student Systems (Advanced Admissions / iRecruitment-independent Admissions) PL/SQL package owned by APPS. It supports the self-service admissions application update pages, providing the server-side validation and persistence logic that drives the applicant-facing "Update Application" flow. The package is declared AUTHID CURRENT_USER, so all unqualified references resolve against the invoking schema's privileges, and it is classified generically as OTHER rather than as a published public API. Its source header indicates a last revision of 115.2 dated 2003/06/20, consistent with the 12.1.1 and 12.2.2 code lines in which legacy Admissions self-service objects were carried forward largely unchanged.

Functionally, the package encapsulates two concerns: creating and validating admission application personal-statement rows, and evaluating the validity of applicant preferences and admissions due dates against the admissions calendar configuration. The user search term admp_val_chg_of_pref corresponds to the package function ADMP_VAL_CHG_OF_PREF, which governs whether a change of preference is permitted for a given application context.

Key Procedures and Functions

  • CREATE_PERSTAT_ROW — Inserts a personal statement row for an application, returning the new ROWID and APPL_PERSTAT_ID to the caller.
  • CHECK_ADM_DUE_DATE_ISVALID — Validates an admissions due date for a given calendar type, calendar instance sequence, category, and admission process type, returning message count, message data, and return status.
  • VALIDATE_DUE_FINAL_DT — Validates the due/final date for an application, additionally considering course, course version, academic calendar type, location, attendance mode, and attendance type.
  • VALIDATE_PREF_UNIQUE — Confirms that a nominated course preference for a person and application sequence number is unique.
  • ADMP_VAL_CHG_OF_PREF — Function determining whether a change of preference is valid for the supplied application and academic context.
  • ADMP_VAL_ACAI_UPDATE — Validation routine associated with updating application course/attendance instance choices.
  • ADMP_VAL_ACAI_PREF — Validates a preference entry in the application course/attendance instance set.
  • ADMP_VAL_ACAI_OPT — Validates an option entry within the application course/attendance instance set.
  • ADMP_VAL_ACAI_US — Validates an unqualified/unspecified selection within the same choice structure.
  • ADMP_VAL_AA_UPDATE — Validation routine invoked when updating admission application attributes.
  • FINAL_SCRN_INTW_EVENT — Handles the final-screen interview event, writing to the workflow screen interview staging table.

Tables Accessed

  • IGS_AD_APPL_PERSTAT / IGS_AD_APPL_PERSTAT_S — Personal statement base and translation tables written by CREATE_PERSTAT_ROW.
  • IGS_AD_CAL_CONF — Admissions calendar configuration, read to resolve calendar type and instance sequence.
  • IGS_AD_PECRS_OFOP_DT — Preference/course offer date data used by change-of-preference validation.
  • IGS_AD_WF_SCRN_INTW_S — Workflow screen interview staging table populated by FINAL_SCRN_INTW_EVENT.
  • IGS_CA_DA / IGS_CA_DA_INST — Calendar detail and calendar detail instance tables, read for date validation.
  • DUAL — Used for single-row computations and function returns.
  • PLITBLM — The standard EBS message-handling table used with the message count/message data/return status convention.

Usage Notes

The package is typically invoked from the Admissions self-service application update pages and supporting workflow activities rather than from concurrent programs. The ADMP_VAL_ACAI_* family is called during interactive validation of applicant course and attendance preferences; ADMP_VAL_CHG_OF_PREF is called when an applicant attempts to modify a nominated preference. ADMP_VAL_AA_UPDATE and FINAL_SCRN_INTW_EVENT are invoked at submission or final screen completion. The validation routines follow the EBS message stack convention (l_msg_count, l_msg_data, l_return_status), so custom code should check return status and empty the message stack after each call. Because the package is AUTHID CURRENT_USER and not master-documented as a public API, direct invocation from custom code is discouraged; preference should be given to the supported Admissions APIs. The package is referenced by one other package within the applications schema.