Search Results assessment_type




Overview
Explore in AI Chat

Overview

The IGS_AS_ANON_ID_ASS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (OSM) product, owned by the IGS schema. Its primary function is to manage the assignment of anonymous identifiers to students for specific assessment periods. This mechanism is critical for maintaining student privacy and ensuring impartiality during the grading process, particularly in high-stakes or blind-marking scenarios. The table acts as a secure cross-reference, linking a student's internal PERSON_ID to a generated or user-provided ANONYMOUS_ID for a defined assessment load calendar, thereby decoupling student identity from submitted work during evaluation.

Key Information Stored

The table's columns are designed to enforce a unique mapping within the context of an assessment period and track the origin of the identifier. The mandatory columns define the core relationship: PERSON_ID (the student), ANONYMOUS_ID (the pseudonym), ASSESSMENT_TYPE, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER (which together define the academic period). The SYSTEM_GENERATED_IND flag is crucial for audit, indicating whether the anonymous ID was auto-generated by the system or supplied via a custom user hook. The table also includes standard EBS WHO columns (CREATED_BY, CREATION_DATE, etc.) for auditing and columns (REQUEST_ID, PROGRAM_ID, etc.) to track concurrent program executions that may populate or modify the data. Two unique indexes enforce data integrity: one ensures a person gets only one anonymous ID per assessment period, and the other guarantees the anonymity of the ID itself is unique within that period.

Common Use Cases and Queries

The primary use case is the anonymization workflow for assessments. When work is submitted for grading, applications can join to this table to retrieve the anonymous ID for a known student, or to resolve an anonymous ID back to a student identity after grading is complete. Common reporting and validation queries include verifying assignments for a specific assessment load calendar or identifying system-generated versus manually assigned IDs. A typical query to retrieve all anonymous mappings for a given academic period would be:

  • SELECT person_id, anonymous_id, system_generated_ind FROM igs.igs_as_anon_id_ass WHERE load_cal_type = '<CAL_TYPE>' AND load_ci_sequence_number = <SEQ_NUM> ORDER BY anonymous_id;

Another critical operational query resolves an anonymous ID submitted with an assessment back to the student: SELECT person_id FROM igs.igs_as_anon_id_ass WHERE anonymous_id = '<ANON_ID>' AND load_cal_type = '<CAL_TYPE>' AND load_ci_sequence_number = <SEQ_NUM>;

Related Objects

Based on the provided dependency information, the IGS_AS_ANON_ID_ASS table is a foundational object referenced by other components within the APPS context. While the metadata does not specify foreign key relationships from this table, its structure implies relationships with core person/student tables (likely via PERSON_ID) and academic calendar tables (via LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER). The documented reference from the APPS synonym IGS_AS_ANON_ID_ASS confirms it is the primary table accessed by the application layer for all anonymous ID assignment functionality. Modules handling assessment submission, grading, and result processing will directly query or join to this table to perform identity resolution.