Search Results igs_as_unitass_item_s




Overview

The APPS.IGS_AS_UNITASS_ITEM_PKG package body supports the assessment item functionality of the Oracle E-Business Suite Student System (IGS) module, specifically the maintenance of unit assessment items. Unit assessment items represent the individual scored components (for example, assignments, examinations, or practical assessments) that make up a student's unit assessment record. The package exposes the standard TAPI (Table API) interface pattern used throughout the Oracle Student System, providing the insert, update, delete, lock, and validation routines that forms, concurrent programs, and dependent packages invoke when manipulating assessment item data. Its status is recorded as VALID in the APPS schema, and it operates under the ETRM API classification of OTHER rather than as a public, externally supported API.

Key Procedures and Functions

The package body defines eighteen documented procedures and functions that follow the conventional TAPI structure:

Tables Accessed

The package reads and writes the base table IGS_AS_UNITASS_ITEM_ALL (through the APPS synonym) and the corresponding IGS_AS_UNITASS_ITEM_S security/translation view, along with DUAL for scalar lookups. Foreign-key validation touches parent entities such as assessment items, calendar instance and type, grading schema, location, unit class, unit mode, unit assessment item group, and unit offering pattern. The dependency list also cites IGS_AS_UNITASS_ITEM_S, which aligns with the user search term igs_as_unitass_item_s and indicates that the security-checked view is a primary access path.

Usage Notes

Because the package is not referenced by any other database object, it is invoked directly by Oracle Student System forms, concurrent processes, and occasionally by custom code that must maintain unit assessment item data. The dependency list shows that it relies on shared utilities such as FND_MESSAGE, FND_GLOBAL, IGS_GE_MSG_STACK, IGS_GE_NUMBER, and IGS_GE_DATE for messaging, auditing, and date handling, and on validation packages including IGS_AS_VAL_UAI, IGS_AS_VAL_AIEM, and IGS_PS_VAL_UNIT. Customisations should call the documented TAPI entry points rather than performing direct DML, and should expect APP_EXCEPTION-based error signalling on validation failure.