Overview

Security

Before Running the Rollover

New Year Rollover Settings

After the Rollover

Overview

The Aeries New Year Rollover is the process of closing out the current school year and preparing for the next school year. Certain data is rolled from the current year database into the next year database according to various district and school settings. The process is initiated from the current year database and performed for the entire district.

Security ↑

NOTE: For hosted customers, only Aeries support staff can edit the Settings tab and initiate the Rollover.

Before Running the Rollover ↑

The following steps should be completed in the current year database unless otherwise noted.

Database and Technical Requirements ↑

• Ensure Aeries is completely up to date for the district.

Self-Hosted Customers:

• Create the database for the next school year in SQL Server Management Studio. 
  • The new database must have the same Database Suffix as the current year database, with the year increased by one (e.g., DST24000EagleUSD). 
  • From New Year Rollover page on the Processes tab, click the Download SQLModel.sql button to download the most recent SQLModel database structure. 
  • Run the SQLModel script against the new database to create the table structure.
  • IMPORTANT: DO NOT log on to the next year database in AdminCS prior to running the Rollover. Using the latest SqlModel.sql file is sufficient to create all the tables and other objects in the next year database.
    NOTE: SqlModel.sql will make all available tables in the next year database ID-based tables, which is a prerequisite for running the Rollover.

• Ensure that the administrator performing the Rollover has the Database Owner (DBO) user name and password.
  NOTE: This SQL login level is necessary because the Rollover entails copying more than just data (e.g., security and table definitions).
  
  Minimum login requirements:
  • Member of the db_owner database role on both the current and next year databases
  • Has ALTER ANY LOGIN server-level permission
    
    

Using a login that is a member of the sysadmin fixed server role is one way to guarantee that permissions are adequate.

• For districts that use custom SQL modules, if any SQL modules belong to a custom schema or contain references to objects in custom schemas, the database administrator must create the schemas and their objects in the next year database prior to starting the Rollover in order for those modules to be copied. The Rollover will not create custom schemas.

Complete Grading ↑

• Complete entry of all grades (GRD).
  
  
• Complete entry of Standards Based Grades (SBG) and verify the roll to Standards Based History (SBH) is completed. See Standards Based Grade History.
  
  
• Ensure that the GRD marks are copied accurately to Grade History (GRH) and Transcripts (HIS) for high schools and middle schools. See Grade Reporting - Copy Grades to Grade History and Transcripts.
  
  
• On Report Card History, generate the report card history. This feature allows schools to save a permanent, electronic copy of every student's report card.
  
  • Regular report cards - See Report Card History.
  • Standards-based report cards - See Report Card History for Standards Based Report Cards.
    
    

Complete End-of-Year Processes ↑

California

• See CALPADS Annual Maintenance - Closing Out the School Year.
• Complete CALPADS procedures for exiting students. See EOY 2: CALPADS Student Withdrawal Data Population Chart.
  
  NOTE: 
  • Students whose End of Year Status (STU.EOY) is populated may also need to have the End of Year Next School (STU.ENS) populated. STU.EOY and STU.ENS do not affect the Rollover; they are populated for CALPADS reporting.
  • Students whose Grad Status (STU.HSG) is populated may also need to have the Grad Status Date (STU.DG) populated. STU.HSG and STU.DG do not affect the Rollover; they are populated for CALPADS reporting.
    
    
• Complete end-of-year withdrawals. See End of Year Withdrawals.
  
  

Texas

• See Texas - End-of-Year Processes.
• See Texas - Attendance Reconciliation - End of Year.

Complete End-of-Year State Reporting ↑

California

• See CALPADS EOY Reporting.
• Map state course codes. See State Course Code Transition.
  
  

Texas

• See Texas - PEIMS Summer (Submission 3).
  
  

Confirm District-Wide Dates ↑

Confirm the following:

• Last day of current school year
• First day of upcoming school year
• Dates to re-open parent/student/teacher portals
• Dates to hide/show scheduling and teacher information to students. See the After the Rollover section below.

Confirm Summer School Dates & Information ↑

Determine if summer school will be run in the current year, next year, or separate database. See Summer School Process.

• If running summer school in Aeries, confirm the following:
  • School codes for summer schools
  • Term start/end dates
  • Third-party programs used during summer school
    
    
• If running Data Confirmation during summer, confirm the following:
  • Date when Data Confirmation opens
  • Date for the Do NOT close AUT if Status Date is After option. Authorization records updated after this date are not closed. See Data Confirmation.
    
    
• On Portal Options:
  • If using Data Confirmation, set the Use eligibility guidelines for next year instead of this year option to indicate if you are using current year or next year guidelines for USDA Income Eligibility for the Income Survey. See Parent Data Confirmation Setup. If set, this option should be cleared after the Rollover.

Clean Up Database ↑

On Administrative Functions, run the following utilities to clean up the database:

• Database Cleanup 
• Launch Fix ENR Process
• Force Cascading DEL Tags
  

See Administrative Functions.

Sync or Lock Fields ↑

On Define Fields to Sync/Lock, review fields in the Student Data (STU), Secondary Student Data (SUP), and Supplemental (SSD) tables and identify fields that should be synced or locked. See Define Fields to Sync/Lock.

• Syncing a field ensures data automatically stays the same between the student's active record and pre-enrollment record at another school.
• Locking a field prevents users at the new school from changing important data. If locked, the field is read-only at the next school and cannot be changed.

Add Custom Tables ↑

On Define Custom Tables:

• Ensure custom tables and fields have been added if needed for next year.

Update Codes ↑

On Update Code Table: 

• Add the code and name for any new schools for the upcoming year (LOC.CD, LOC.NM).
• Update any district-level code tables for next year as needed.
• Update any school-level code tables for next year as needed.

Manage School Changes for Next Year ↑

On School Options (district):

• Use the Next School (STU.NS) is the next grade-level, not next matriculation-level option to indicate if the student's Next School field is used to hold the student's next year school (recommended). If disabled, Next School is only considered when the student completes the highest grade level at the school. In this case, the Next School field will be be set to 0 when there is no school for the student to matriculate to.

On School Options:

• Add new schools that will be opening next year. See Adding a New School in Aeries.
  
  
• Ensure that an Inactive school is set up. Typically the school ID is 999.
  
  
• If adding grade levels at any school, change the Low Grade and High Grade fields in the current school year.
  NOTE: If removing grade levels at any school, the Low Grade and High Grade  fields should be adjusted in the next school year (after the Rollover).
  
  
• Verify the Low Grade and High Grade (LOC.LO and LOC.HI) for the district and each school.
  • High Grade should never be above 12, even if using higher grade levels for Special Ed, Adult Ed or other students. Using grade 12 with a Next Grade of 13 ensures that the graduating seniors are dropped during the Rollover.
  • Exception: A school's High Grade can be above 12 if the Low Grade is also above 12 (e.g., Adult Ed with grade-range of 15-15). 
  • For students whose grade level is above 13, STU.GR is copied to Next Grd (STU.NG), unless the Do Not Bump Grade option is selected for that grade level on New Year Rollover; otherwise, they will roll over with the same grade level.
    
    

On Graduation Requirements:

• Review graduation requirements for next year and update or increment as needed. See Graduation Requirements.

Enter Student Information for Next Year ↑

• The following query allows you to list and verify retained students and returning seniors, including non-completers:
  
  The query lists students by current grade level whose Status is blank and grade level is "No grade level," including the student's school number, first and last name, ID, current grade level, next grade level, current school, next school, and status.
  
  LIST STU SN LN FN ID GR NG SC NS BY GR IF TG = " " AND GR = NG

• The following query allows you to verify that schools have set up their pre-enrolled students with the correct next grade and that there is an asterisk (*) in the Status (STU.TG) field.
  
  The query lists students by current grade level whose Status is Pre-enrolled, including the student's school number, first and last name, ID, current grade level, next grade level, current school, next school, and status.
  
  LIST STU SN LN FN ID GR NG SC NS TG BY GR IF TG = "*"

On Transcripts:

• Check Credit Compl (STU.CC) for all seniors and determine if any students will need to be retained in 12th grade.

On Demographics:

Texas users, see Texas - End-of-Year Processes.

• Enter the Next Schl field for all students (STU.NS), including returning students.
  • Use the current school or blank for students who are returning.
  • Use the next school if the student is moving to a different school within the district.
  • Use the Inactive school for students who are leaving the district. 
  • NOTE: Pre-enrolled students will roll into the school where the pre-enrolled record is created, unless the Copy Pre-Enrolled Students from This School to their Next School option is enabled on New Year Rollover.
  • Inactive students who are not active or pre-enrolled at another school will roll to the Inactive school regardless of the Next Schl field, unless the Bypass the Copy to Inactive School Process option is enabled on New Year Rollover.
  • The following query allows you to verify that STU.NS is populated with the school the student will be attending next year, even if the student is returning to the same school.
    
    The query lists students by Next Schl whose Status is blank and whose current school is not the same as the next school, and whose next grade level is greater than the current grade level, including the student's school number, first and last name, ID, current grade level, next grade level, current school, next school, and status.
    
    LIST STU SN LN FN ID GR NG SC NS TG BY NS IF TG = " " AND SC # NS AND NG < X
    
    (where X is the highest grade level for that school)
    
    
• Enter the Next Grd field for all students (STU.NG).
  • Typically the field is increased by 1 from the current Grade field (STU.GR).
  • For students who should not roll over, such as seniors, set Next Grd to the highest grade level at the school plus 1.
    Examples: 
    • At a 9-12 school, any student whose Next Grd is 13 will not roll over.
    • At a K-8 school, any student whose Next Grd is 9 will not roll over.
      
      
  • The following query allows you to verify that STU.NG is increased by one from the current Grade field to ensure that non-retained students will roll over correctly.
    
    The query lists students by current grade level whose Status is blank and whose next grade level is not equal to the current grade level plus 1, including the student's school number, first and last name, ID, current grade level, next grade level, current school, next school, and status.
    
    LIST STU SN LN FN ID GR NG SC NS TG BY GR IF TG = " " AND NG # (( GR + 1 ))
    
    
    
• Pre-enrolled students should have an asterisk (*) in the Status field (STU.TG).
  
  
• Verify the Next Teacher/Next Counselor (STU.NT) is set correctly for students who are assigned a teacher/counselor for the upcoming school year. 
  • Elementary schools use Teacher.
  • Secondary schools use Counselor.
    
    
• Verify the Next Trk (STU.NTR) is set correctly for students who are assigned a track for the upcoming school year.
  
  
• The following query allows you to verify Next Teacher/Counselor and Next Trk:
  
  The query lists students by next grade, next teacher/counselor, and next track whose Status is blank or Pre-enrolled, including the student's school number, first and last name, ID, current grade level, next grade level, current school, next school, next teacher/counselor, current teacher/counselor, current track, and next year track.
  
  LIST STU SN LN FN ID GR NG SC NS NT CU TR NTR BY NG NT NTR IF TG = " " OR TG = "*"
  
  
  
• If any of the following will be used during the Rollover, verify the values:
  • Next Grid Code (STU.NGC)
  • Next Elig Code (STU.NSP)
  • Next Prg 1, 2 (STU.NP1, STU.NP2)
  • Next ResSchl (STU.NRS)
  • Next Attr Code (STU.NIT)
  • Next ResDist (STU.NTD)

The following query allows you to verify the student "Next" fields. Add the BY….IF….statements below the queries if needed:

LIST STU SN LN FN ID GR SP NSP AP1 NP1 AP2 NP2 GC NGC RS NRS IT NIT ITD NTD

• Verify Next School of Residence
  BY SC NM IF NRS # RS
• Verify Next Inter/Intra District Transfer
  BY SC NM IF NIT # IT, BY SC NM IF NTD # ITD
• Verify Next Programs
  BY SC NM IF NSP # SP, BY SC NM IF NP1 # P1, BY SC NM IF NP2 # P2
• Verify Next Grid Code
  BY SC NM IF NGC # GC
• Verify Next Track (STU.NTR)
  LIST STU SN LN FN ID GR NG SC NS TR NTR BY NG NTR IF TG = " " OR TG = "*"

Run Pre-Rollover Reports ↑

Several reports should be run before initiating the Rollover. See the New Year Rollover Settings > Processes Tab section below.

Additional Checklists ↑

• Legacy New Year Rollover Preparation Checklist
• Hosted New Year Rollover Preparation Checklist

New Year Rollover Settings ↑

Data is rolled from the current year database to the next year database according to settings on the New Year Rollover page.

NOTE: Only self-hosted customers can update settings and push settings to other schools. 

For all other users, the Change and Push to Other Schools buttons are not displayed. Instead, the Informational section is displayed with Approve and Disapprove buttons allowing database administrators to verify and approve settings.

For self-hosted customers only:

• Click Change to modify the setting for any fields.
• After making selections, click Push to Other Schools if the school-based settings should be be applied to any other schools. A pop-up window opens allowing you to select specific schools.
  
  

District Wide Settings ↑

Under New Year Rollover Settings - District Wide:

About Copying Custom SQL Modules ↑

• Custom SQL modules include objects defined in the sys.sql_modules system catalog, which includes objects such as functions, stored procedures, triggers, and views. 
• CLR objects and assemblies are not copied.
• Th Copy custom SQL modules option is not required in order to copy student-related custom tables that are identified in the CTD table. That happens automatically and includes table definition, primary key, foreign key, indexes, check constraints, triggers, and MS_Description extended properties where applicable. 
• If a custom View is located in the CTD table, the View definition is automatically copied, regardless of the Copy custom SQL modules setting.
• The Rollover will not create custom schemas. If any SQL modules belong to a custom schema or contain references to objects in custom schemas, the schema(s) and their objects must already be created in the next year database prior to starting the Rollover in order for those modules to be copied.
• The Rollover attempts to copy Extended Properties of custom SQL modules if they exist. Various factors outside Aeries' control can prevent certain modules from copying successfully. For example, if the module definition references a separate database or linked server that is not accessible at the time the script is executed, the module will not be created successfully.
• The Rollover ignores errors encountered while copying custom SQL modules. Aeries does not attempt to report these errors to the administrator running the Rollover.
• Aeries cannot guarantee that all custom SQL modules will be copied successfully. It is the responsibility of the database administrator to verify the existence of these modules in the next year database.

Inactive School Settings ↑

Under New Year Rollover Settings - Inactive School:

Students who are not rolled to a valid school will be added to the Inactive school with the spe Inactive School Code and Status Tag fields, unless Bypass the Copy to Inactive School Process is selected.

School Based Settings ↑

Under New Year Rollover Settings - School Based:

NOTES:

• Be sure that each school is updated with the appropriate rollover settings for that particular school.
• The Inactive school does not need special School Based Rollover settings configured, with the exception of the Only copy Student records under 25 years of age option. All other School Based settings are ignored when a student is copied to the Inactive school.

School Based Fields Tab ↑

The tab lists any fields that have been designated in the Code table (COD) as school-based, as indicated on Update Code Tables page. On Update Code Tables, the Use School-Based Codes for this field option is displayed for certain custom fields, including:

• User Code fields from school-based tables
• Text field in SUP
• Any text field in a school-based custom table

See Update Code Table.

When Use School-Based Codes for this field option is selected for a particular table-field, that field will be listed on the New Year Rollover > School Based Fields tab. Any student data in these fields will be cleared during the Rollover if the student's record is moved to a different school. 

• Under School Based Field Counts by Table, all tables that contain any school-based fields are listed with the count of school-based fields in each table.
• Under School Based Fields by Table, the school-based fields for each table are listed.

Processes Tab ↑

Once all prerequisite steps are completed, the Processes tab is used to run the Rollover. The tab provides the reports and processes necessary to run the Rollover and guides users through the steps.

Hosted Aeries customers will see the following page because most rollover steps are handled by the Aeries support team. Otherwise, see below.

Administrative Functions ↑

This section is only displayed for self-hosted clients, because this service is provided by the Aeries support team for hosted clients.

Under Administrative Functions, the dates on which maintenance functions were last run from the Administrative Functions page is displayed. Dates more than seven days old are red. 

Confirm that all necessary functions have been performed as needed. 

Pre-Rollover ↑

Under Pre-Rollover, the reports that must be run prior to the Rollover are listed, along with the date the report was last run.

• Pre-Rollover Audit Listing Report - Run in the current year database in order to locate errors in student records that could cause potential rollover issues. See Pre-Rollover Audit Listing Report.

• Table Record Counts (Pre) Report - Once all records are cleaned up, run the report in the current year database. The report displays a record count for every table in the Aeries database.
  
  Once the Rollover is completed, the report should be run again. (See the Post-Rollover section below.) Compare the two reports to determine if the appropriate counts of records were copied from the current year to the next year.

Rollover ↑

Under Rollover, the fields for setting up the process are displayed, as well as the Start Rollover button.

Indicate the following:

Start Rollover ↑

Click the Start Rollover button. 

• You are prompted to confirm that you want to start the Rollover. Click Yes to continue.
  • The page is refreshed, and the DBO user name and password are cleared. 
  • A message is displayed indicating that an email message will be sent when the Rollover has completed.
  • A message is displayed indicating the Rollover start time.
    
    
• When completed:
  • An email is sent to the admin once the Rollover has completed.
  • The completion date and time are displayed on the Processes tab.

Post-Rollover ↑

Under Post-Rollover, the reports that must be run upon completion of the Rollover are listed. The reports should be run from the outgoing current year database, after the Rollover is completed. These reports automatically look at the next year database as needed; this allows the reports to be generated even before the next year database has been added to the Aeries connections config file.

• Missing Students Report - Run the report to compare the next year database to the current year database and view a list of all students who are not in the next year database.
  
  If all students rolled from the current year database to the next year database, the report should have zero students listed. Review all students listed on the report and complete any steps needed to add these students to the next year database.
  
  NOTE: If Bypass the Copy to Inactive School Process option was selected when running the Rollover, the Missing Students Report may have many students listed.
  
  
• Table Record Counts (Post) - Once the Rollover is complete, run the report to obtain a record count for every table in the Aeries database. The counts should be compared to the Table Record Counts (Pre) report to determine if the appropriate counts of records were copied from the current year to the next year.
  

After the Rollover ↑

• Update the .config files. See Configure Aeries Database Connection.
  
  
• Consider how the Rollover and summer school could affect any third-party software that integrates with Aeries. For example, Clever has provided the following link to documentation on managing school-year rollover with Clever:
  https://support.clever.com/hc/en-us/articles/202118886
  
  
• Set up the next year school calendar and terms. See Create a Calendar and Build Terms.

  
  

• Adjust class calendars as needed. See Flex Scheduling - Class Calendars.
  
  
• On School Options, if removing grade levels at any school, update the Low Grade and High Grade fields accordingly.
  
  
• Set up and configure Weekly Progress Emails for Parents. See How to setup and configure Weekly Progress Emails for Parents.
  
  
• Delete records at the school for staff who are no longer employed at the school. See Fall 2 FAQs.
  
  
• Inactivate standards that will not be used in the next school year. See Standards.
  
  
• On Portal Options, if the Use eligibility guidelines for next year instead of this year option was selected before the Rollover, disable the setting. See Parent Data Confirmation Setup.
  
  
• If there is a need to hide scheduling and teacher information prior to the first day of school, set fields accordingly. See Hiding Gradebook, Class and Teacher Information Before the First Day of School.
  
  
• After summer school is complete and grades have been posted to transcripts, run the Copy Data from Summer School Information process. See Copy Data from Summer School Information.

Rollover Changes ↑

• The District Options Table (DPT) settings revert to pre-rollover settings.
  
  
• The School Supplemental (SUP) and District Supplemental (DSD) SQL definitions are copied.
  
  
• SQL definitions for student-related custom tables in the Custom Table Definitions (CTD) table are copied. This also occurs if the CTD record represents a View in SQL. For custom tables, the primary key, foreign key, indexes, check constraints, triggers, and MS_Description extended properties are copied if they exist.
  • When a table is defined in the CTD table, but does not actually exist on the SQL database, the rollover process bypasses the table.
• User-defined schemas, tables, views, and related objects will roll over to the new year. 
  • This includes additional schemas other than "dbo".
• Data in non-student-related tables (e.g., LOC, TCH, CRS, STF, COD and many others) is copied.
  • Some tables (e.g., DRA, REQ, STR, GBB, TFL, SFL, MST) have a specific Rollover setting that determines how that table is processed or if its records are copied at all.
  • Scheduling totals are cleared in the TCH and MST tables. These totals can be recomputed after the Rollover by running the Master Schedule report in the next year database. Scheduling totals for SMS are recomputed automatically during the Rollover.

    NOTE: Non-student-related custom tables are NOT copied. Both the table definitions and the data must be copied separately by the database administrator if these tables are needed in the next year database.
    
    

• Data in the Student ID Numbers (IDN) table and all tables related to IDN (except STU) is copied.
  NOTE: Data in custom tables that have a foreign key relationship to IDN is copied automatically. These must be defined in Custom Table Definitions (CTD). If the table should not be copied forward it should be dropped, or it should have the foreign key constraint to IDN removed and should not be defined in CTD at all.
  
  

• Student (STU) records and STU-related records (e.g., SSD, SUP) are rolled over based on the Rollover settings and in the following sequence:

  • All pre-enrolled students (status tag = *) are copied to the school in which they are pre-enrolled regardless of the Next School (STU.NS) value, and these students are activated, keeping their school-based Student Number (STU.SN), unless the Copy Pre-Enrolled Students from This School to their Next School is selected. Therefore, it is critical to manage pre-enrolled records effectively prior to initiating the Rollover.
    
    

  • All active students that are NOT moving to a different school are copied to their same school as long as their Next Grade (STU.NG) is valid for that school, keeping their school-based Student Number (STU.SN).
    
    NOTE: If a student has multiple active records (e.g., concurrent enrollment), it is possible for multiple records to be copied forward to different schools.
    
    

  • All active students who are moving to a different school are copied to their Next School (STU.NS) as long as their Next Grade (STU.NG) is valid for that school. A student is NOT copied to the same school more than once. If STU.NS is blank, the student is copied into their current school.
    
    

  • All students that have NOT yet been copied to any school are copied to the Inactive school unless the Bypass the Copy to Inactive School Process option was selected.
    
    NOTE: Students with Next Grade (STU.NG) = 13 are never copied (not even to the Inactive school). Students with Next Grade greater than the district High Grade (e.g., 8th grade completers in a K-8 district) also are not copied. However, students in the special grades 14-18 are exceptions and copy regardless of the district High Grade.
    
    NOTE: Data in custom tables that have a foreign key relationship to STU are copied automatically after each STU record is copied.
    
    

• If the option to Copy Custom SQL Modules was selected, those modules are copied next.
  
  

• Security is copied, including Aeries security (e.g., UGN, UGA, UGP, etc.) and SQL Server security (database users and roles).

  • The User and Group Name table (UGN) will bypass any user who has not logged in within the past calendar year; these users will not have an account in the new year.

  • Temporary substitute teacher accounts "teachersub" are bypassed.

• The Number of Bullying Incidents and Number of Cyber Bullying Incidents values will be cleared. 

• For schools converting to Flex Scheduling for the first time: On Scheduling Setup, if Use Staff-Section Association instead of Teacher Numbers(TN) with SMS sections is selected during the Rollover, the Use Staff in Sections field on School Options is enabled in the next year database.

• The Portal Options end dates for Parent Data Confirmation process are automatically set to the day before the rollover is run, effectively closing the year in the current year database. The Parent Portal will remain open in the new year database.
  
  

• (Texas only) On the Staff page, the TIA Cred Yr - TIA Creditable Year of Service field is cleared in the next year.
  
  

• (Texas only) On the Demographics page, Student Census Block and the Truancy Indicator field are cleared in the new year with the exception of students in the Inactive school.

• (Texas only) The Truant Date Met field on the Student Data 2 tab (STU.TDM) is cleared in the next year when the Truancy Indicator field was a 'Y' in the previous year.
  
  

• (California only) On the Courses page, California Specific Fields tab, the New State Course Code (CRS.NC3) is moved to State Course Code (CRS.C3) if populated. These fields are used when state course codes are transitioning from one school to the next.
  
  

TOP ↑