Search Results anum_id

Overview

The IGS_AS_ANON_NUMBER 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 (formerly Oracle Campus Solutions) product family under the IGS (iGrants) schema. Its primary function is to maintain a registry of anonymous identifiers used to recognize individuals within the assessment subsystem. This mechanism is critical for processes requiring confidentiality or blind marking, such as anonymizing student submissions during grading to ensure impartial evaluation. The table acts as a secure mapping between a system-generated unique key, an anonymous number, and the specific academic load calendar context, ensuring the anonymous identifier is meaningful only within a defined academic period.

Key Information Stored

The table's structure is designed to manage the lifecycle and context of anonymous identifiers. The key columns include:

• ANUM_ID: A mandatory, sequence-generated primary key (NUMBER(15)) providing a unique system identifier for each record.
• ANONYMOUS_NUMBER: A mandatory, unique anonymous identifier (NUMBER(15)) assigned to a person for a given context. This is the key data element for blind processing.
• LOAD_CAL_TYPE and LOAD_CI_SEQUENCE_NUMBER: These two columns (VARCHAR2(10) and NUMBER, respectively) together define the academic calendar context (e.g., a specific semester or term) for which the anonymous number is valid. Their combination is part of a unique constraint.
• Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): These audit columns track the creation and modification history of each record, adhering to Oracle EBS standards.

Common Use Cases and Queries

This table is central to assessment anonymity workflows. A common use case involves generating and distributing anonymous numbers to students for a particular course offering in a term, then using those numbers to identify submitted work without revealing student identities during initial grading. For reporting and administration, typical queries include retrieving all anonymous numbers for a specific academic load period or verifying the assignment of a particular anonymous number. The foundational query, as indicated in the ETRM, is:

SELECT ANUM_ID, ANONYMOUS_NUMBER, LOAD_CAL_TYPE, LOAD_CI_SEQUENCE_NUMBER FROM IGS.IGS_AS_ANON_NUMBER WHERE LOAD_CAL_TYPE = '&CAL_TYPE' AND LOAD_CI_SEQUENCE_NUMBER = &SEQ_NUM;

Data integrity is enforced via two unique indexes: IGS_AS_ANON_NUMBER_U1 on ANUM_ID (primary key) and IGS_AS_ANON_NUMBER_U2 on the combination of ANONYMOUS_NUMBER, LOAD_CAL_TYPE, and LOAD_CI_SEQUENCE_NUMBER, preventing duplicate anonymous numbers within the same academic context.

Related Objects

Based on the provided dependency information, the IGS_AS_ANON_NUMBER table is a referenced object, meaning other database objects likely depend on it via foreign key relationships, though specific foreign key constraints are not detailed in the excerpt. The documentation states it "is referenced by following: APPS.IGS_AS_ANON_NUMBER." This typically indicates the existence of an APPS synonym (IGS_AS_ANON_NUMBER) pointing to the IGS.IGS_AS_ANON_NUMBER base table, which is standard for EBS to facilitate access across schemas. The table does not itself reference other objects. In a typical implementation, this table would be joined to student enrollment and assessment submission tables via the ANONYMOUS_NUMBER or ANUM_ID columns to de-anonymize results after initial blind processing is complete.