Search Results assp_val_uai_opt_ref

Overview

The APPS.IGS_PS_VAL_UAI package is a validation package within the Oracle E-Business Suite student systems (IGS) schema. Its broad purpose is to enforce business rules and referential integrity for assessment and unit-attempt data structures within the Student Information Management (SIMS) product family. It operates in the "Products and Programs" and "Assessment" functional areas, providing reusable validation logic that other packages and forms call to confirm that records involving unit assessment items, assessment types, calendar instances, and calendar statuses are internally consistent and legally combinable.

As with many legacy IGS validation packages, this object has undergone significant refactoring across releases, and several historical functions have been stripped out. The header comments record that procedures such as ASSP_VAL_AI_EXMNBL, ASSP_VAL_CUTOFF_DT, ASSP_VAL_UAI_CAL, and the ASSP_VAL_OPTNL_LINKS family were removed under Bug 1956374, and that ASSP_VAL_UAI_LINKS was retrenched and deleted because it was no longer required for the "Calculation of Results" requirement referenced in Bug 2162831. The current public surface is therefore substantially smaller than historic versions, and the package should be treated as a narrow, purpose-built validation utility rather than a comprehensive assessment engine.

Key Procedures and Functions

The package exposes three documented program units:

• CRSP_VAL_CRS_CI — Validates a calendar instance in the context of course information, confirming that the supplied calendar type and calendar instance sequence number represent a valid and usable instance for the course. It raises or returns messaging output for downstream callers and is declared with PRAGMA RESTRICT_REFERENCES (..., WNDS), indicating the function performs no database writes.
• ASSP_VAL_UAI_OPT_REF — Validates an optional reference associated with a unit assessment item, checking that the referenced unit code and version combination can lawfully stand as an optional reference rather than an obligatory or primary assessment record.
• ASSP_VAL_UAI_SAMEREF — Validates that multiple unit assessment item references resolve to the same underlying reference, i.e., confirming consistency and identity between compared assessment items rather than permitting conflicting references.

These functions return BOOLEAN success/failure values and, where relevant, emit a message name through an OUT NOCOPY parameter so that the caller can surface a standard EBS error message.

Tables Accessed

The package reads against four documented tables via APPS synonyms:

• IGS_CA_INST_ALL and IGS_CA_STAT — the calendar instance and calendar status structures. These underpin CRSP_VAL_CRS_CI, which must confirm that the referenced calendar instance exists and carries an active/valid status before permitting course assessment activity.
• IGS_PS_UNITASS_ITEM — the unit assessment item table, central to both ASSP_VAL_UAI_OPT_REF and ASSP_VAL_UAI_SAMEREF, providing the unit and version data being compared.
• IGS_AS_ASSESSMNT_TYP — the assessment type reference table, used to confirm that the assessment types attached to unit assessment items are legitimate entries.

No insert, update, or delete operations are documented; validation packages of this class are typically read-only with respect to the described tables.

Usage Notes

Because IGS_PS_VAL_UAI is a PL/SQL validation package, it is normally invoked indirectly rather than directly by end users. Typical call paths include OAF or Oracle Forms pages in the Student Information Management stack that capture unit assessment items, calendar instances, and assessment types, and internal SIMS packages performing pre-commit business-rule verification. The ETRM metadata records three dependent packages referencing this unit, which is consistent with an internal API consumed by higher-level validation and process packages. Custom extensions and interfaces that programmatically create or update records in IGS_PS_UNITASS_ITEM should call the appropriate validation functions before committing, since the underlying constraints are enforced in code rather than by database constraints alone.