Results for “igs_as_anon_id_ps”

42 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGS_AS_ANON_ID_PS table is a core component of the Oracle E-Business Suite Student System (IGS) product family. It stores the association between a person (student) and an assigned Anonymous ID generated by the Assessment subsystem, specifically for the assignment Method designated "PROGRAM". This allows institutions to track and reconcile anonymous identifiers that are issued to candidates sitting assessments, enabling the institution to map an anonymous mark or result back to the correct person only when authorized to do so.

The table resides in the IGS schema and holds 13 documented columns. In Data Vault modeling terms, the metadata characterises it as satellite-leaning. This is a modeling suggestion: the table acts primarily as a descriptive satellite attached to the person/course business key, holding the anonymous identifier and related audit attributes rather than serving as an independent hub. The distinction matters when designing downstream reporting layers — the anonymous ID should be treated as an attribute of the person/course relationship, not as an entity in its own right.

Key Information Stored

The table's principal business content is captured by a small set of highly significant columns. The composite primary key IGS_AS_ANON_ID_PS_PK is formed by PERSON_ID and COURSE_CD, which together identify the unique combination of person and course to which an anonymous ID applies. A second, unique constraint IGS_AS_ANON_ID_PS_UK (documented as IGS_AS_ANON_ID_PS_U2) enforces uniqueness on ANONYMOUS_ID, ensuring no two anonymous identifiers collide — this is the business-key candidate most relevant to the user's search term igs_as_anon_id_ps_uk.

  • PERSON_ID — identifier of the student or person receiving the anonymous ID; also a foreign key to the student attendance table.
  • ANONYMOUS_ID — the actual anonymous identifier value assigned; protected by a unique index.
  • SYSTEM_GENERATED_IND — flag indicating whether the anonymous ID was system-generated or manually entered.
  • COURSE_CD — course code context for the assignment; part of the composite primary key.
  • CREATED_BY, CREATION_DATE — standard audit columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent change.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and form context columns used to trace which process loaded or modified the row.

Together these columns distinguish the surrogate/unique key from the descriptive satellite attributes, reinforcing the satellite-leaning classification.

Common Use Cases and Queries

Typical scenarios include reconciling anonymous marks back to students, auditing which anonymous IDs were issued per course, and reporting on system-generated versus manual identifiers. A common retrieval pattern joins the table to the student attendance view using the documented foreign key columns:

  • Look up a person by anonymous ID: SELECT person_id, course_cd FROM igs.igs_as_anon_id_ps WHERE anonymous_id = :id;
  • List all anonymous IDs for a course: SELECT anonymous_id, system_generated_ind FROM igs.igs_as_anon_id_ps WHERE course_cd = :course;
  • Confirm uniqueness and detect duplicate assignment attempts against IGS_AS_ANON_ID_PS_UK.
  • Audit loads using REQUEST_ID and PROGRAM_ID to trace concurrent program executions.

Related Objects

The most significant dependency is IGS_EN_STDNT_PS_ATT_ALL, the documented foreign-key target referenced through PERSON_ID and COURSE_CD. Additional dependent objects in the IGS Student System typically include:

  • IGS_EN_STDNT_PS_ATT_ALL — student attendance records; joined on PERSON_ID and COURSE_CD.
  • IGS_AS_ANON_ID_PS_PK / _UK / _U1 / _U2 — primary and unique indexes governing integrity.
  • Assessment and exam result tables that resolve anonymous IDs to marks.
  • Student/person base tables (HZ_PARTIES, PER_ALL_PEOPLE_F) referenced transitively via PERSON_ID.
  • Concurrent program definitions behind PROGRAM_ID/PROGRAM_APPLICATION_ID audit columns.

Because the table is satellite-leaning, reporting layers should always join back to the person/course hub rather than treating ANONYMOUS_ID as an isolated entity.