luAbsenceType lookup table

The luAbsenceType lookup table is used to record the type of absence that appears on the Create Absence Event window. See Individual student absence events in the Attendance and absence events manual.

In New Zealand schools, the absence types are set by the New Zealand Ministry of Education (NZMOE). See Attendance codes for New Zealand schools in the Attendance and absence events manual.
The absence types also appear on the:






Unique code used to identify the absence type.


Description as it appears in the Absence Type field on the Create Absence Event window.


Used by Synergetic to fill in the Absence Type on the Create Absence Event window for some modes; this speeds up data entry.

For example, when entering:

  • a late sign in, Synergetic automatically fills in the Absence Type with the Late description

  • an excursion, Synergetic automatically fills in the Absence Type with the Excursion description.

    A SynergyMeaning of:
  • Truant is used in New Zealand schools to convert unknown absence events to truant if there is no explanation within a specified number of days.
  • Unknown may also be required for the BeepWhenUnexplainedFlag setting. See BeepWhenUnexplainedFlag configuration setting.


Not used.


Used by Synergetic when determining whether to count an absence event as absent or present. For example, when calculating truancy in New Zealand schools.
In this example, absence events with this absence type are counted as being absent:

In this example, absence events with this absence type are counted as being present:


Type in the code of the report to be printed when this absence type is selected.
Note: By default, the report references the vStudentAbsenceEvents view in the database. To generate a report with a different database view, add the database name in brackets next to the report code. For example, LateReport(uAbsenceCustomTable). The parameter AbsenceEventSeq is passed into the nominated view.
Also, see the ReportCode field in the luAbsenceEventType lookup table.


A single character representation of the absence type, displayed for each period in the Today field on the Attendance window.

A hyphen (-) is used to indicate that a class has not been marked.
All other codes use the Absence Type recorded for the each of the student's classes during the day. For example, Amanda attended the dentist or doctor (D) in period 1 but period 2 is unknown (?). Further investigation reveals that Amanda was held up at the doctor and the code for period 2 is changed to D as well.
Note: It is advisable that New Zealand schools use the same values as the absence types outlined in Attendance codes for New Zealand schools in the Attendance and absence events manual.


Order that the absence types are displayed on the Absence Type drop-down list.

The higher the number the later in the list that the entry appears.


Absence type is active when this field is selected.
Clear the field to set the absence type to inactive.


If teachers are configured to enter attendances as possibilities, you can automatically treat the feedback for selected absence types as definitive.

The Teacher/Attendance Officer mode is enabled using the EnableAttendanceOfficerModeFlag. See EnableAttendanceOfficerModeFlag configuration setting.
In the following example, the SubmitPossibleAsActualFlag field has been selected for the Sickbay absence type in the luAbsenceType lookup table.

A teacher has marked attendances for the class - one student went to the sick bay and another was thought to be at the dentist.

Two corresponding absence events are created when the teacher submits the class attendances. As shown below, when the Attendance Officer reviews these the:

  • Sickbay (S) entry is already treated as definitive - the type has been set to Sickbay and the other details supplied by the teacher are recorded as well
  • Doctor/Dentist (D) entry is treated as a possibility (Unexplained Absence) until the Attendance Officer can verify the details.


External system if the records have been loaded from an existing file. For example, NZMOE for New Zealand Ministry of Education.
See Loading lookup tables for external systems.


External system code to link the Synergetic value to an external system. For example, NZMOE.


Date of the last time the lookup table entry was modified.


User that last modified the lookup table entry.