eSchoolPLUS – Schoolzilla Pro

How We Connect

eSchoolPLUS data is pulled nightly via a secured Open Database Connection (ODBC). Traffic is encrypted in transit and at rest and a successful connection requires an SSH server or VPN. For more information about ODBC and VPN, please review our Connecting your SIS to Schoolzilla via ODBC overview.

For more information about getting connected, please review our setup article here.

Mappings Overview

If a field can be further configured by a Schoolzilla admin or relates to metric configurations, then there will be a link to the relevant part of Data Configuration Settings below.

Students

Student demographic data is sourced from the REG, REG_PERSONAL, and REG_ENTRY_WITH tables. The documentation below represents the default mappings in place. Some of these mappings can be customized and are typically updated during initial setup. Customizable fields have an asterisk(*).

Key Field(s)	Mapping(s)
System Student ID	Values are populated using the Student_ID field in the REG table.
Full Name	Values are populated using the Last_Name and First_Name fields in the REG table.
Current Grade Level	Values are populated using the Grade field in the REG table. We translate the number to a descriptor with an ordinal indicator.
EL Status*	Values are populated using the ESL field in the REG_PERSONAL table.
FRL Status*	Values are populated with the Meal_Status field in the REG_PERSONAL table. We translate these values using the description field in the REGTB_MEALSTATUS table.
Foster Care Status*	Values are equal to "In Foster Care" when the Foster_Care field in the REG_PERSONAL table is equal to "Y". This field is equal to "Not In Foster Care" when Foster_Care is "N".
Gender*	Values are populated using the Gender field in the REG table.
Grade Level at the Time	Values are populated using the Grade field in the REG_ENTRY_WITH table. We translate the number to a descriptor with an ordinal indicator.
Homeless Status*	Values are equal to "Is Homeless" when the Homeless_Status field in the REG_PERSONAL table is equal to "Y", "D", "HM", "S", or "U". This field is equal to "Not Homeless" when Homeless_Status is "N".
Is SPED*	Values are populated with "In Special Education" when the HAS_IEP field in the REG_PERSONAL table is Y. All other students are set to "Not in Special Education".
Migrant Status*	Values are equal to "Migrant" when the Migrant field in the REG_PERSONAL table is equal to "Y". This field is equal to "Not a Migrant" when Migrant is "N".
Military Family Status*	Values are not populated by default.
Primary Ethnicity*	Values are populated using the Ethnic_Code field in the REG_PERSONAL table. We translate this value using the Description field in the REGTB_ETHNICITY table.
SPED Status*	Values are populated using the Disability column in the REG_DISABILITY table. If a student has multiple current disabilities, we use the one with Disability_Order of 1. We translate this value using the Description field in the REGTB_DISABILITY table.

Staff

A comprehensive list of teacher users is sourced from the REG_STAFF table.

Key Field(s)	Mapping(s)
Full Name	Values are populated using the Last_Name and First_Name fields in the REG_STAFF table.
Email	Values are populated using the Email field in the REG_STAFF table.

Calendars

School calendar data is sourced from the REG_CAL_DAYS table.

Key Field(s)	Mapping(s)
School Year	Calendars are linked to school years using the School_Year field in the REG_CAL_DAYS table.
In Session	Days are considered "In Session" if the Membership_Day field in the REG_CAL_DAYS table is "Y".

School Enrollment & Retention

Student school enrollment history is populated using the REG_ENTRY_WITH table.

Key Field(s)	Mapping(s)
School Year	Enrollments are linked to school years using the School_Year column in the REG_ENTRY_WITH table.
Entry Date	Values are populated using the Entry_Date field in the REG_ENTRY_WITH table.
Exit Date	Values are populated using the Withdrawal_Date field in the REG_ENTRY_WITH table. If the Withdrawal_Date field is NULL, the exit date is defaulted to the last day of the school year for the student's school.
Exit Code	Values are populated using the Withdrawal_Code field in the REG_ENTRY_WITH table.
No Show	Enrollments are considered "No Show" records if the Withdrawal_Code description stored in the Description field in the REGTB_WITHDRAWAL table includes "No Show."
School	Enrollments are linked to schools using the Building field in the REG_ENTRY_WITH table.

Student Rosters (Class & Teacher Associations)

Students are rostered to classes and teachers using the SCHD_STU_CRS_DATES, SCHD_MS, SCHD_MS_SESSION and SCHD_MS_STAFF tables.

Key Field(s)	Mapping(s)
School Year	Class enrollments are linked to school years using the School_Year field in the SCHD_MS table.
Class Entry Date	Values are populated using the Date_Added field in the SCHD_STU_CRS_DATES table. If the Date_Added value occurs prior to the term starting for the scheduled section, the first day of the term is used as the class entry date. This value comes from the Start_Date in the REG_MP_DATES table.
Class Exit Date	Values are populated using the Date_Dropped field in the SCHD_STU_CRS_DATES table. If the Date_Dropped field is not populated or occurs after the term closes, the last day of the term is used as the class exit date. This value comes from the End_Date in the REG_MP_DATES table.
Staff	Class enrollments are linked to staff using the Primary_Staff_Id field in the SCHD_MS_SESSION table and the Staff_Id field in the MS_STAFF table.

Attendance

Daily attendance is constructed using the REG_ENTRY_WITH and ATT_STU_DAY_TOTALS tables. We assume a student is present for every in-session school day they were enrolled at their school, unless otherwise marked absent.

Key Field(s)

Mapping(s)

Attendance Value

Values are populated using the Att_Code_Value field in the ATT_STU_DAY_TOTALS table for the View_Type you specify.

Student are considered absent for the full day if Att_Code_Value is 1.
Students are considered absent for a half day if Att_Code_Value is .5.
Students are considered present for the full day if Att_Code_Value is 0 or there is no record in the table for the student on the day, the day was in session and the student was enrolled.

The default attendance View_Type used is ATTND. Please contact support to specify which View_Type to use for daily attendance.

Absence Code

Values are populated using the Attendance_Code in the ATT_STU_DAY_TOTALS table. A code is considered "absent" if the State_Group in the ATT_CODE table is equal to "A" or if it has been configured as an absence code.

Please contact support to configure State_Group codes as Absent if group values other than "A" are used.

School

Attendance data are linked to schools using the Building field in the REG_ENTRY_WITH table.

Behavior

Behavior data is loaded from the DISC_INCIDENT and DISC_OFF_ACTION tables.

Key Field(s)	Mapping(s)
School Year	Behavior incidents are linked to school years using the Incident_Date and Building fields in the DISC_INCIDENT table.
School	Behavior incidents are linked to schools using the Building field in the DISC_INCIDENT table.
Incident Date	Values are populated using the Incident_Date field in the DISC_INCIDENT table.
Incident Time of Day	Values are populated using the Incident_Time field in the DISC_INCIDENT table.
Behavior Category	Values are populated using the Description field in the DISC_INCIDENT_CODE table for the Incident_Code in the DISC_INCIDENT table.
Behavior Location	Values are populated using the Description field in the DISCTB_LOCATION table for the Location in the DISC_INCIDENT table.
Behavior Response	Values are populated using the Description field in the DISCTB_OFF_ACTION table for the Action_Code in DISC_OFF_ACTION.

GPA

Cumulative (Cumulative & Rolling Cumulative) and Term GPAs are sourced from the MR_STU_GPA table.

Key Field(s)

Mapping(s)

GPA Calculation

GPA_TYPE is used to determine the GPA Calculation.

Please contact support to configure which GPA_Type(s) should be used for Cumulative, Rolling Cumulative and Term GPA.

GPA Value

Values are populated using the CUM_GPA (for Cumulative) and CUR_GPA (for Term) fields in the MR_STU_GPA table.

Grades

Grades data is sourced from the MR_STU_MARKS and MR_IPR_STU_MARKS tables. Some of these mappings can be customized and are typically updated during initial setup. Customizable fields have an asterisk(*).

Key Field(s)	Mapping(s)
School Year	Final grades are linked to a school year using the School_Year field in the MR_STU_MARK table. In-progress grades are linked to a school year using the School_Year field in the SCHD_MS table.
School	Final grades are linked to schools using the Building field in the MR_STU_MARK table. In progress grades are linked to schools using the Building field in the SCHD_MS table.
Course Subject*	Values are populated using the Description field in the REGTB_DEPARTMENT table for the Department code in the SCHD_COURSE table.
Class Period	Values are populated using the first valid option: The Description field in the SCHD_PERIOD table for the Start_Period of the course from the MS_SESSION table. The Start_Period of the course from the MS_SESSION table.
Grade Name	Values are populated using the Mark_Value field from the MR_STU_MARKS and MR_IPR_STU_MARKS tables.
Grading Period	Grades are linked to grading periods using the Building and Mark_Type fields. Values are populated using the Mark_Type field in the MR_MARK_TYPES table.
Term	Final grades are linked to terms using the School_Year, Building and Marking_Period. Values are populated using the Marking_Period field in the REG_MP_WEEKS table. In-progress grades linked to terms based on IPR_Date.**
Grade Type	Values are populated using Description field in the MR_MARK_TYPES table for the Mark_Type field from the MR_STU_MARKS and MR_IPR_STU_MARKS tables.
Grade Status	All grades from MR_STU_MARKS are considered "Final". All grades from MR_IPR_STU_MARKS are considered in-progress.

Known Limitations

Class Subject - eSchoolPLUS supports tagging a course with multiple subjects. Schoolzilla will only link a course to one subject; the subject with subj_order = 1.

Frequent Data Quality Issues

No known frequent issues at this time.

Frequently Asked Questions

None at this time.