Search Results igs_ps_val_uoo




Overview
Explore in AI Chat

Overview

IGS_PS_VAL_UOO is a validation package body in the Oracle E-Business Suite Student Systems (IGS) product family, owned by the APPS schema. The "PS" component of the name associates it with the PeopleSoft-derived student records lineage embedded in Oracle Student System, while the "VAL" segment identifies it as a validation utility and "UOO" denotes the Unit Offering Option entity. The package encapsulates the business rules that govern the creation, maintenance, and lifecycle of unit offering options within an institution's academic structure.

Unit offering options represent the specific teaching instances derived from a unit offering — for example, a particular location, delivery pattern, class grouping, or attendance mode. Because these records influence enrolment, fee assessment, and scheduling, the institution must enforce referential and semantic integrity before such rows are committed. IGS_PS_VAL_UOO provides that enforcement layer as a server-side PL/SQL API, ensuring that validation logic is centralised rather than duplicated across forms, concurrent programs, and interfaces. The package is documented with STATUS: VALID in the ETRM repository, confirming it is an active, supported component of the 12.1.1 and 12.2.2 code lines. It is recorded as not referenced by any database object, indicating that it is invoked from client-side or mid-tier callers rather than through database-level triggers or views.

Key Procedures and Functions

The package exposes four documented procedures, each addressing a discrete validation concern:

  • CRSP_VAL_LOC_CD — Validates the location code associated with a unit offering option. It confirms that the supplied location exists and is active in the institution's location reference data, guarding against orphaned or obsolete location references.
  • CRSP_VAL_UOO_UC — Validates the unit class relationship for the unit offering option, confirming that the unit class reference is consistent with the parent unit offering and the institution's class definitions.
  • CRSP_VAL_UOO_CONTACT — Validates the contact or party details attached to the option, using the HZ_PARTIES registry to confirm that the referenced person or organisation is known and valid.
  • CRSP_VAL_UOO_INACTIV — Validates the inactivation state of a unit offering option, ensuring that deactivation requests respect existing dependencies such as active enrolments or scheduled classes before the status change is permitted.

Each procedure follows the IGS convention of raising messages through the IGS_GE_MSG_STACK and APP_EXCEPTION utilities so that calling forms and programs can surface user-readable errors via FND_MESSAGE.

Tables Accessed

The ETRM dependency listing identifies HZ_PARTIES as the primary table accessed through APPS synonyms. HZ_PARTIES supplies the party registry used by CRSP_VAL_UOO_CONTACT to verify person and organisation identities. Additional dependencies in the listing indicate that the package also consults IGS_AD_LOCATION and IGS_AD_LOCATION_TYPE for location validation, IGS_AS_UNIT_CLASS for class relationships, IGS_PE_PERSON for person records, and companion validation packages IGS_AS_VAL_UAI, IGS_PS_VAL_UNIT, and IGS_EN_GEN_003. These references are predominantly read-only lookups; the procedures evaluate the caller's proposed values against existing reference data rather than performing direct inserts or updates on the referenced tables.

Usage Notes

IGS_PS_VAL_UOO is typically invoked from the Oracle Student System forms that maintain unit offering options, and from batch or interface programs that load offering data through public APIs. The documented reference count of seventeen dependent packages confirms that it is a widely reused validation component within the IGS schema. When extending or customising unit offering functionality, developers should call these procedures rather than reimplementing the checks, so that validation behaviour remains consistent across standard and custom code paths. Because the package is not referenced by any database object, callers must invoke it explicitly; it will not fire automatically as a consequence of DML. The package is present and valid in both 12.1.1 and 12.2.2, and no version-specific divergence is documented in the ETRM metadata.