Results for “attendance_flag”

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

Overview

The IGS_AS_SUA_SES_ATTS table is a transactional data object within the Oracle E-Business Suite IGS (Student System) product module. It stores attendance records captured for a student's unit attempt against a specific teaching session. In operational terms, the table acts as the attendance register layer of the Student System: for each combination of student, unit offering, and session, it records whether the student attended, was absent, or met the applicable attendance flag condition. Each row therefore represents a single attendance event for a single student against a single scheduled session.

From a Data Vault modeling perspective, the metadata's foreign key topology suggests treating IGS_AS_SUA_SES_ATTS as a link entity. The heuristic classification is derived from the fact that its primary key is composed entirely of foreign key columns rather than a single generated surrogate identifier. In this reading, the table occupies the intersection between the student unit attempt (represented through IGS_EN_SU_ATTEMPT_ALL) and the session definition (represented through IGS_AS_USEC_SESSNS), with the attendance flag carried as a descriptive payload on the relationship. Confirmed at version 12.1.1 and carried into 12.2.2, the object remains schema-owned by IGS with the documented status of VALID.

Key Information Stored

The table contains ten documented physical columns. The most significant are the four key components and the attendance payload:

• PERSON_ID — identifies the student whose attendance is recorded. This forms the leading column of the primary key and points back to the student unit attempt.
• COURSE_CD — the course code associated with the attempt, also part of the composite primary key.
• UOO_ID — the unit offering option identifier, joining the record to both the unit attempt and the session definition.
• SESSION_NAME — the name of the session against which attendance is taken, completing the composite key.
• ATTENDANCE_FLAG — the descriptive attribute recording the attendance outcome for that student-session pairing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns that capture who created and last modified the record, when, and from which login session.

The unique constraint IGS_AS_SUA_SES_ATTS_PK, comprising PERSON_ID, COURSE_CD, UOO_ID, and SESSION_NAME, is the business-key candidate enforcing that a student may have only one attendance record per session. No separate generated surrogate key is documented; the composite business key functions as the primary identifier.

Common Use Cases and Queries

Typical applications include attendance reporting for a unit offering, verification of session-level participation, and extraction of attendance history for a student attempt. A representative query counts attendance flags across all sessions of a given offering:

• SELECT SESSION_NAME, ATTENDANCE_FLAG, COUNT(*) FROM IGS_AS_SUA_SES_ATTS WHERE UOO_ID = :uooid GROUP BY SESSION_NAME, ATTENDANCE_FLAG;
• SELECT * FROM IGS_AS_SUA_SES_ATTS WHERE PERSON_ID = :person_id AND COURSE_CD = :course_cd ORDER BY SESSION_NAME;

Because the primary key is entirely composed of join columns, the table is efficient for FK-driven lookups from the unit attempt or session side. Reports commonly aggregate by student for attendance percentage calculations or extract full session rosters for tutor review.

Related Objects

The foreign key metadata identifies two principal parent objects:

• IGS_EN_SU_ATTEMPT_ALL — joined on PERSON_ID, COURSE_CD, and UOO_ID; supplies the student unit attempt context.
• IGS_AS_USEC_SESSNS — joined on UOO_ID and SESSION_NAME; supplies the session definition against which attendance is recorded.

Downstream reporting and validation logic typically traverses these relationships rather than querying the attendance table in isolation, ensuring that attendance flags are always interpreted in the context of a valid attempt and a defined session.