Search Results igs_as_assessor_type




Overview
Explore in AI Chat

Overview

The IGS_AS_ASSESSOR_TYPE table is a core data object within the Oracle E-Business Suite Student System (IGS) module. It functions as a reference or lookup table designed to store and manage user-defined types of assessors. An assessor, in the academic context, is an individual responsible for evaluating student work, such as grading assignments or marking exams. This table provides a centralized, controlled mechanism for classifying these evaluators beyond basic person identifiers, enabling institutions to categorize assessors by role, responsibility, or qualification (e.g., Primary Marker, Secondary Reviewer, External Examiner, Moderator). Its primary role is to ensure data integrity and consistency across the assessment processes by serving as the authoritative source for valid assessor type codes, which are then referenced by transactional tables throughout the system.

Key Information Stored

Based on the provided metadata, the table's structure is centered on a code that uniquely identifies each assessor type. The primary and most critical column is ASS_ASSESSOR_TYPE, which serves as the table's primary key. This column holds the unique code for each user-defined assessor type. While the full column list is not detailed in the excerpt, typical reference tables in this module would also include descriptive columns such as a meaningful name (e.g., DESCRIPTION), an effective date range (START_DATE, END_DATE), and system control columns (CREATION_DATE, LAST_UPDATE_DATE, etc.). The existence of a primary key constraint (IGS_AS_ASSESSOR_TYPE_PK) on ASS_ASSESSOR_TYPE enforces the uniqueness and mandatory nature of this code.

Common Use Cases and Queries

This table is primarily used in two contexts: system setup and transactional reporting. During implementation, administrators populate this table with the institution's specific assessor classifications. Common operational queries include retrieving the list of all active assessor types for use in assessment definition forms or validating a user-entered assessor type. For reporting, it is frequently joined to transactional data to replace codes with meaningful descriptions. A typical SQL pattern involves joining to the related item assessor table:

  • Listing All Defined Assessor Types: SELECT ass_assessor_type FROM igs.igs_as_assessor_type ORDER BY 1;
  • Reporting on Assessments with Descriptions: SELECT aia.*, atype.description FROM igs.igs_as_item_assessor aia, igs.igs_as_assessor_type atype WHERE aia.ass_assessor_type = atype.ass_assessor_type;

Related Objects

The IGS_AS_ASSESSOR_TYPE table has a direct parent-child relationship with the IGS_AS_ITEM_ASSESSOR table, as documented in the provided foreign key metadata. The IGS_AS_ITEM_ASSESSOR table stores the specific assessors assigned to assessment items (like exams or assignments). It references IGS_AS_ASSESSOR_TYPE via its ASS_ASSESSOR_TYPE column, which is a foreign key to the primary key of IGS_AS_ASSESSOR_TYPE. This relationship ensures that every assessor type recorded against an assessment item in IGS_AS_ITEM_ASSESSOR is a valid, pre-defined type. No other foreign key relationships are documented in the provided excerpt.

  • Foreign Key Reference: Table IGS_AS_ITEM_ASSESSOR, column ASS_ASSESSOR_TYPE, references IGS_AS_ASSESSOR_TYPE (ASS_ASSESSOR_TYPE).