Results for “repp_get_cal_str”

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

Overview

IGS_GE_VAL_PARAM is a PL/SQL validation package in the Oracle EBS Student Systems (IGS) product family, owned by the APPS schema. Its filename convention (IGSGE08S.pls) and procedure naming prefix (repp_val_) indicate that it belongs to the general setup (GE) module and is used by the reporting and parameter-entry layer of the Student Systems forms. The package provides a centralized library of lookup validation routines that accept a user- or report-supplied code, verify it against the corresponding IGS reference table, and return a Boolean success indicator together with an error message name suitable for display by the calling form or concurrent program.

The original header carries a creation date of 21/08/98 by MSONTER and a last modification of 2005/09/30, reflecting the package's long-standing role as shared validation plumbing rather than application business logic. It is classified by ETRM as OTHER, meaning it is not a public APIs package but an internal utility that other IGS components call. For a user searching on "igs_ps_units," the salient entry point is the function that validates the IGS_PS_UNIT code against the IGS_PS_UNIT_VER_ALL table.

Key Procedures and Functions

The documented interface exposes eighteen functions, all following the repp_val_ (validation) or repp_get_ (retrieval) naming pattern:

• REPP_VAL_UNIT_CD — validates an IGS_PS_UNIT code, which is the object referenced by the user's search term "igs_ps_units." It confirms that the supplied unit code exists in the versioned unit table.
• REPP_VAL_LOCATION — validates attendance location codes against IGS_AD_LOCATION_ALL.
• REPP_VAL_ATT_MODE and REPP_VAL_ATT_TYPE — validate attendance mode and attendance type codes respectively.
• REPP_VAL_UNIT_CLASS, REPP_VAL_UNIT_MODE, and REPP_VAL_UNIT_MODE_CLASS — validate unit classification and unit mode combinations.
• REPP_VAL_CRS_TYPE — validates course type codes against IGS_PS_TYPE_ALL.
• REPP_VAL_ENR_CAT, REPP_VAL_ADM_CAT, and REPP_VAL_FEE_CAT — validate enrolment, admission, and fee category codes.
• REPP_VAL_UNIT_CAL — validates the calendar associated with a unit offering.
• REPP_VAL_COURSE — validates a course (program) code against IGS_PS_VER_ALL.
• REPP_VAL_ASS — validates an assessment code.
• REPP_VAL_ORG_CD — validates an organizational unit code, drawing on HZ_PARTIES and IGS_OR_STATUS.
• REPP_GET_CURR_CAL, REPP_GET_NOMIN_CAL, and REPP_GET_CAL_STR — retrieve the current calendar, the nominated calendar, and a calendar string representation used to default calendar parameters during report execution.

Each validation function accepts a single code, validates it, and returns BOOLEAN plus an OUT message name so that the caller can display a standard EBS error via FND_MESSAGE.

Tables Accessed

The package reads the following APPS synonyms: IGS_PS_UNIT_VER_ALL and IGS_PS_VER_ALL (unit and course version headers), IGS_AD_LOCATION_ALL (attendance locations), IGS_EN_ATD_MODE_ALL and IGS_EN_ATD_TYPE_ALL (attendance reference data), IGS_AS_UNIT_CLASS_ALL and IGS_AS_UNIT_MODE (unit academic structure), IGS_EN_ENROLMENT_CAT, IGS_FI_FEE_CAT_ALL, and IGS_PS_TYPE_ALL (categories and program types), IGS_CA_INST_ALL, IGS_CA_TYPE, and IGS_CA_STAT (calendar instance, type, and status), HZ_PARTIES (organization validation), and IGS_OR_STATUS (organization status). All access is read-only validation against reference and setup data.

Usage Notes

IGS_GE_VAL_PARAM is invoked from Student Systems forms, concurrent program parameter windows, and custom PL/SQL that needs to confirm the existence of a coded value before processing. The BOOLEAN return pattern means it is typically called inside IF ... THEN blocks, with the OUT p_msg_name passed to FND_MESSAGE.SET_NAME and FND_MESSAGE.RAISE_ERROR for user feedback. The NOCOPY hint on the IN OUT parameters reflects a performance-conscious design for repeated validation inside loops. ETRM records zero packages referencing it directly, indicating it is called from form-level triggers or anonymous report logic rather than from other pl/sql APIs, and it should be treated as an internal component when planning 12.1.1 or 12.2.2 customizations.