Search Results igs_as_val_atyp

Overview

IGS_AS_VAL_ATYP is a validation package in the APPS schema belonging to the Oracle Student Systems (IGS) product family, specifically the Assessment and Progression (AS) module. Its naming convention — IGS_AS_VAL_ATYP — indicates that it is a validation routine ("VAL") concerned with assessment types ("ATYP"). In Oracle EBS 12.1.1 and 12.2.2, packages of this class encapsulate business-rule checks that guard the integrity of assessment type configuration and related assessment item data before insert, update, or processing operations are committed. The package is classified as OTHER in the documented API taxonomy, meaning it is not published as a formal public API but serves as an internal validation utility consumed by other assessment processing packages. Its status is VALID in the ETRM registry, confirming it is a shipped and active database object.

Key Procedures and Functions

The ETRM metadata documents two procedures within this package. Their parameter lists are not published and are therefore not reproduced here.

• ASSP_VAL_SAT_CLOSED — A validation routine associated with the student assessment type (SAT) configuration. Its purpose is to verify the closed status of an assessment type or associated assessment instance, preventing operations that would act upon a closed assessment type record. This supports institutional rules that lock assessment structures once they have been closed for entry or maintenance.
• ASSP_VAL_AI_EXIST2 — A second validation routine concerned with assessment item existence. It checks whether a corresponding assessment item record exists (and is valid) before downstream processing proceeds, guarding against orphaned or invalid references. The "2" suffix indicates this is a variant of an earlier validation, reflecting the iterative evolution of the assessment rules across releases.

Both procedures follow the standard validation-package pattern: they evaluate data state and raise an application error or return a status indicator that the calling code interprets, rather than performing transactional DML themselves.

Tables Accessed

The package references two base tables through APPS synonyms, as documented in the dependency listing:

• IGS_AS_ASSESSMNT_ITM_ALL — The assessment item table, which stores individual assessment items associated with assessment types. The validation logic in ASSP_VAL_AI_EXIST2 most likely queries this table to confirm (or refute) the existence of a given assessment item.
• IGS_AS_SASSESS_TYPE — The student assessment type table, holding assessment type definitions and their status attributes. ASSP_VAL_SAT_CLOSED would query this table to determine whether the relevant assessment type is closed.

Both objects are accessed read-only for validation purposes; the package carries no documented insert, update, or delete dependencies, consistent with its role as a pre-processing integrity checker.

Usage Notes

IGS_AS_VAL_ATYP is an internal supporting package. The dependency metadata shows it is referenced by IGS_AS_ASSESSMNT_TYP_PKG, confirming that assessment type maintenance logic invokes these validations as part of its own processing flow. It also references itself via dependent code, indicating shared internal helper logic reused between the two procedures.

Typical invocation scenarios in an EBS 12.1.1 / 12.2.2 environment include:

• Assessment type setup and maintenance forms within the Student Systems responsibility, where the form's underlying package calls these validations before saving records.
• Concurrent programs that process or migrate assessment data, invoking the validations to reject invalid rows.
• Custom extensions and integrations that call IGS_AS_ASSESSMNT_TYP_PKG, thereby indirectly invoking this package.

Because the package is classified as OTHER rather than a public API, direct calls from custom code should be avoided. Customers should instead invoke the owning package (IGS_AS_ASSESSMNT_TYP_PKG) or use supported public APIs, and should revalidate any custom dependency after applying patches or upgrades, as internal validation signatures may change between releases.