Skip to main content

Student course session (StudentCourseSession)

Back to Student

Key Value
Name Student course session
Short Name StudentCourseSession
Version 1.7.0
Description A Student course session records a specific Student's activity for a course.
Uniquely Identified by

Each Student course session (StudentCourseSession) is uniquely identified by:

Applicable to England Northern Ireland Scotland Wales
Coverage In general, one StudentCourseSession must be returned to record each year of activity that a student undertakes on a course as part of their Engagement. In some cases the StudentCourseSession may be less than a year or a StudentCourseSession may be required to record that a student is dormant. Please see guidance for full details.

A StudentCourseSession associates a Student with the Course that the student is engaging with. In most cases, the StudentCourseSession will represent a year of the student's study.

The StudentCourseSession is also associated with the relevant SessionYear that reflects the planned start date of the year of programme they are engaging with.

The associated SessionYear will represent a year of the programme. The dates returned on the StudentCourseSession will reflect the start and end of the students activity within that session year. The StudentCourseSession dates may therefore differ from the SessionYear dates if the student starts the year late or leaves early.

Please see the SessionYear guidance for guidance on returning SessionYears.

StudentCourseSessions must be returned in line with the below principles:

  • The start and end dates of the StudentCourseSesion must fall between the start and end dates of the associated SessionYear.

  • StudentCourseSessions must not be longer than a year

  • An Engagement cannot have overlapping StudentCourseSessions

  • If a student transfers between different Courses within the same Engagement, the first StudentCourseSession must be closed and a new StudentCourseSession opened associated with the new Course. In these cases, StudentCourseSessions may be shorter than a year, depending on when the transfer happens.

  • Once submitted, a StudentCourseSession must continue to be returned until the StudentCourseSession.SCSENDDATE is returned to indicate it has ended. If there is no activity for an open StudentCourseSession in a given reference period, the StudentCourseSession would still be returned with the FTE information and SessionStatus indicating that the student is dormant.

Postgraduate research and fully flexible courses

For these courses, StudentCourseSessions are not required to be associated with a SessionYear as the flexible nature of these programmes means that the concepts of a planned start date and end date often do not apply.
When a student starts studying one of these Courses, a StudentCourseSession is returned associated with the relevant Course with the StudentCourseSession.SCSSTARTDATE indicating the students start date. From this point, yearlong StudentCourseSessions would be returned until the student completed their studies with the final StudentCourseSession having a StudentCourseSession.SCSENDDATE indicating their actual end date. Each StudentCourseSession would therefore start at the same point in each year of the students studies.

Quality Rules Quality rules to follow
Reason Required To allow linking between students and Courses, to hold information regarding a student's study including mode, FTE, type of activity and fees and funding information.
Minimum Occurrences 0
Maximum Occurrences unbounded
Field Field Length Optional?
Student course session identifier (SCSESSIONID) 50 No
Course identifier (COURSEID) 50 No
Employer fees (EMPFEES) 2 Yes
Expected end date (EXPECTEDENDDATE) 10 Yes
Fee method (FEEMETHOD) 2 Yes
Intended thesis title (INTENDEDTHESISTITLE) 500 Yes
Intercalation (INTERCALATION) 2 Yes
Invoice fee amount (INVOICEFEEAMOUNT) 10 Yes
Invoice HESA identifier (INVOICEHESAID) 4 Yes
PGR language identifier (PGRLANGID) 2 Yes
PGR language percentage (PGRLANGPCNT) 4 Yes
PhD submission date (PHDSUB) 10 Yes
Placement (PLACEMENT) 2 Yes
Predicted student load (PREDICTEDSTULOAD) 4 Yes
Preparatory Student course session flag (PREPFLAG) 2 Yes
Reason for Student course session ending (RSNSCSEND) 2 Yes
Student course session end date (SCSENDDATE) 10 Yes
Student course session fee amount (SCSFEEAMOUNT) 10 Yes
Student course session mode (SCSMODE) 2 No
Student course session start date (SCSSTARTDATE) 10 No
Session year identifier (SESSIONYEARID) 50 Yes
Study abroad (STUDYABROAD) 2 Yes
Student load (STULOAD) 4 Yes
Programme year (YEARPRG) 2 Yes
Parent Entity Engagement (Engagement)
Child Entities
Revision History
Coding Manual Version Element Version Notes
1.4.0 1.0.2 Coverage updated indicating when a StudentCourseSession is required, the guidance should be referred to for full details.
1.2.0 1.0.1 Guidance added to state that StudentCourseSessions must continue to be returned until they have ended, even if there is no activity in a given reference period.

Contact Liaison by email or on +44 (0)1242 388 531.