Search Results igs_as_msht_su_atmpt

Overview

The table IGS_AS_MSHT_SU_ATMPT is a core data object within the Oracle E-Business Suite Student System (IGS) module. It serves as a critical junction table that links student academic assessment records with the physical or electronic mark sheets used for grading. Its primary function is to document which specific student unit attempts (enrollments) were included on a given mark sheet and to record the precise order in which those attempts were listed on the original hard-copy sheet. This table is essential for maintaining an audit trail between the administrative process of marking (via sheets) and the official student academic records stored in the system, ensuring data integrity and traceability for assessment-related activities in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each record by combining identifiers for the student, their course, the unit attempt, and the specific mark sheet. The key columns are PERSON_ID (identifying the student), COURSE_CD (the course code), UOO_ID (the Unit Offering Option, identifying the specific class/section instance), and SHEET_NUMBER (the identifier of the mark sheet). Collectively, these columns store the fundamental relationship: that a particular student's attempt at a specific unit offering was recorded on a designated mark sheet. The table likely includes additional columns to store the SEQUENCE_ORDER or POSITION on the sheet, as implied by the description regarding "order in which student unit attempt appeared."

Common Use Cases and Queries

This table is central to queries that reconcile assessment data. A common use case is auditing or troubleshooting grade entry, such as identifying all students whose grades were submitted via a particular mark sheet or finding which mark sheet was used to record grades for a specific student's unit attempt. For reporting, it enables the regeneration of a mark sheet's layout or the analysis of marking workflows. A typical SQL pattern involves joining to the mark sheet and student unit attempt tables to get a complete view.

• Find all unit attempts on a mark sheet: SELECT * FROM igs_as_msht_su_atmpt WHERE sheet_number = :p_sheet_num ORDER BY sequence_order;
• Find the mark sheet for a student's unit attempt: SELECT sheet_number FROM igs_as_msht_su_atmpt WHERE person_id = :p_person_id AND uoo_id = :p_uoo_id;
• Audit join example: SELECT msht.*, su.unit_cd FROM igs_as_msht_su_atmpt msht JOIN igs_en_su_attempt_all su ON msht.person_id = su.person_id AND msht.course_cd = su.course_cd AND msht.uoo_id = su.uoo_id WHERE msht.sheet_number = :p_sheet;

Related Objects

The table IGS_AS_MSHT_SU_ATMPT maintains defined foreign key relationships with two primary transactional tables in the Student System, as documented in the ETRM metadata.

• IGS_AS_MARK_SHEET_ALL: The SHEET_NUMBER column in IGS_AS_MSHT_SU_ATMPT references this table, which stores the master record for each generated mark sheet. This relationship ensures every recorded unit attempt links to a valid mark sheet header.
• IGS_EN_SU_ATTEMPT_ALL: The composite key of PERSON_ID, COURSE_CD, and UOO_ID in IGS_AS_MSHT_SU_ATMPT references this table, which is the central repository for all student unit enrollment attempts. This relationship guarantees that the mark sheet entry corresponds to a legitimate and existing student academic record.

These relationships enforce critical business rules, preventing orphaned records and ensuring that grading actions performed via mark sheets are permanently anchored to both the assessment instrument (the sheet) and the official student academic history.