Search Results anonymous_id




Overview
Explore in AI Chat

Overview

The IGS_AS_ANON_ID_US table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (OSM) product, as indicated by the IGS (iGrad Student) schema. Its primary function is to manage the mapping between students (PERSON_ID) and anonymized identifiers (ANONYMOUS_ID) within the context of a specific academic assessment section (UOO_ID). This table is critical for supporting anonymous marking processes, where a student's identity is concealed from graders during the evaluation of assignments or examinations. The metadata confirms it is designed to "Holds the person with the assigned Anonymous Id for the method SECTION," indicating its role in section-level anonymous assessment configurations.

Key Information Stored

The table's structure captures the essential links between student enrollment, the academic offering, and the generated anonymous identifier. The most critical columns include:

  • PERSON_ID, COURSE_CD, UOO_ID: Together, these form the table's primary key (IGS_AS_ANON_ID_US_PK), uniquely identifying a student's enrollment in a specific unit offering option (section).
  • ANONYMOUS_ID: The anonymized identifier (VARCHAR2) assigned to the student for the section.
  • SYSTEM_GENERATED_IND: A flag ('Y'/'N') indicating whether the anonymous ID was auto-generated by the system or provided via a custom user hook, offering flexibility in ID generation logic.
  • LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER: Define the academic load calendar instance for the enrollment.
  • TEACH_CAL_TYPE and TEACH_CI_SEQUENCE_NUMBER: Define the teaching calendar instance for the unit section.
  • UNIT_CD: The code of the academic unit.

The table also contains standard EBS WHO columns (CREATED_BY, CREATION_DATE, etc.) and concurrent program tracking columns.

Common Use Cases and Queries

This table is central to reporting and processes involving anonymous assessment. A common use case is retrieving the anonymous ID for a specific student in a section to label submissions or to reverse-engineer the identity after grading is complete. Administrators may also run queries to audit ID generation or identify sections using anonymous marking. A foundational query to retrieve the mapping for a specific academic load calendar would be:

SELECT person_id, anonymous_id, uoo_id, system_generated_ind
FROM igs.igs_as_anon_id_us
WHERE load_cal_type = :load_cal_type
AND load_ci_sequence_number = :load_ci_seq_num;

Another critical pattern is joining to student information tables to produce grader-ready reports that exclude personal identifiers, relying solely on the ANONYMOUS_ID from this table.

Related Objects

As per the provided relationship data, IGS_AS_ANON_ID_US is integrally linked to other key OSM tables via foreign key constraints. These relationships enforce data integrity and define common join paths:

These relationships indicate that anonymous ID assignments are tightly scoped to a valid student enrollment in a defined academic section within a specific calendar period.