SIS Error Help

2019-20 Version 1.0

Error Codes & Message

The following error code definitions describe error messages that may be received after processing data which have been generated from the SIS (Student Information System) data submission.

001-99

001, 002 Student Profile ADD or UPDATE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD OR UPDATE a student at this time.

003, 004, 005 Enrollment Add, Update, or Delete not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE an enrollment for a student at this time.

009, 010 Class Schedule ADD or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD or DELETE Class Schedules at this time.

011, 012, 13 Address ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE student address data at this time.

014, 015, 016 504 Student ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE 504 student data at this time.

017, 018, 019 Event ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE Event data at this time.

020, 021, 022 Perpetrator ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE Perpetrator data at this time.

023, 024, 025 Action ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE Actions and Interventions data at this time.

026, 027, 028 Victim ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE Victim data at this time.

032 Student secure ID not reassigned

Cause:	Reassignment did not pass validation against eScholar.
Solution:	The PII in eScholar and SIS do not match for the LASIDs you are trying to reassign.

033, 034, 035 K3 Assessment ADD, UPDATE or DELETE not allowed

Cause:	Function is restricted by administrative settings.
Solution:	You cannot ADD, UPDATE or DELETE K‐3 Assessment data at this time.

Top of Page

100-199

100 Invalid record length

Cause:	One or more records in the upload file are not the correct length.
Solution:	Verify and correct the record layouts within the upload file. Beginning 2015‐16, ensures the record conforms to the non‐PII format.

• A row in the file is missing one or more characters causing the record to be an incorrect length.

101 Invalid Record Type

Cause:	A record in the upload file contains an invalid Record Type Code.
Solution:	For each record type within the upload file, verify and correct the Record Type Code.

102 Invalid System Indicator

Cause:	A record in the upload file contains an invalid System Indicator code.
Solution:	For each record type within the upload file, verify the System Indicator is "SIS",then correct and resubmit as necessary.

103 Invalid LEA Code

Cause:	A record in the upload file contains an invalid three‐digit LEA code.
Solution:	Verify and correct the three digit LEA code.

• Check "Use SIS School for Reporting" on the setup box for LA SIS Export File for students that have been assigned a SIS School.

104 Invalid School Session Year

Cause:	A record in the upload file contains an invalid School Session.
Solution:	Verify the School Session is expressed in two valid, consecutive years (Example: 20152016), then, correct and then resubmit as necessary.

Top of Page

U01-U99

U01 Invalid Secure ID

Cause:	An attempt was made to process a student’s record that contained an invalid LASID.
Solution:	Verify a valid 10‐digit numeric Louisiana Secure Id (LASID) has been entered and exists for the student in the eScholar Louisiana Secure ID system.

U02 Secure ID does not exist

Cause:	For the LEA and/or Site Code, an attempt was made to submit record(s) for a student who has not been assigned a LASID.
Solution:	For the LEA and Site Code, ensure the student has been submitted and assigned a LASID by the eScholar Louisiana Secure ID system.

• Send student file back through eScholar by using LA Student UID Mass Export File and the LA UID Mass Import File.

U03 Student’s First Name not matched

Cause:	An attempt was made to process a student’s record with a Partial First Name that does not match the student’s Partial First Name in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s Partial First Name is the same as submitted to the eScholar Louisiana Secure ID system.

U04 Student’s Last Name not matched

Cause:	An attempt was made to process a student’s record with a Partial Last Name that does not match the student’s Partial Last Name in the eScholar Louisiana Secure ID System.
Solution:	Verify the student's Partial Last Name is the same as submitted to the eScholar Louisiana Secure ID system.

U05 Student’s Local ID not matched

Cause:	An attempt was made to process a student’s record with a Local ID that does not match the student’s Local ID in the eScholar Louisiana Secure ID System.
Solution:	Verify the student's Local ID is the same as submitted to the eScholar Louisiana Secure ID system.

U06 Student’s Day of Birth not matched

Cause:	An attempt was made to process a student’s record which contained a Day of Birth that does not match the student’s Day of Birth in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s Day of Birth is valid and is the same as submitted to the eScholar Louisiana Secure ID system.

U07 Student’s Ethnicity not matched

Cause:	An attempt was made to process a student’s record that contained an Ethnic Code that does not match the student’s Ethnic Code in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s Ethnic Code is correct and is the same as submitted to the eScholar Louisiana Secure ID System.

U08 Student’s Gender not matched

Cause:	An attempt was made to process a student’s record that contained a Sex Code that does not match the student’s gender in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s Sex Code is correct and is the same as submitted for the student to the eScholar Louisiana Secure ID System.

U09 Residing Parish of Student’s Address not matched

Cause:	An attempt was made to process a student’s record that contained a Residing Parish that does not match the student’s Residing Parish in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s 2‐digit Residing Parish is correct and is the same as submitted for the student to the eScholar Louisiana Secure ID System.

U10 Zip code of Student’s Address not matched

Cause:	An attempt was made to process a student’s record that contained a Zip Code that does not match the student’s Zip Code in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s 5‐digit Zip Code is correct and is the same as submitted for the student to the eScholar Louisiana Secure ID System.

U11 Retired Secure ID (please use Active ID xxxxxxxxxx)

Cause:	An attempt was made to process a student’s record that contained a retired LASID.
Solution:	Verify an active 10‐digit numeric Louisiana Secure Id (LASID) has been entered.

U13 No eScholar submission found for current year

Cause:	An attempt was made to process a student’s record that was not submitted by the LEA in the current school year.
Solution:	Submit the student in eScholar in this school year.

Top of Page

200-299

200 Secure ID exists for another student in LEA

Cause:	Upload: More than one Demographic Record (010) using the same LASID was found in your upload file. Online: The Secure ID (LASID) already exists in eScholar Louisiana Secure ID System.
Solution:	Verify the student’s LASID is correct.

201 Another student with same Reassign Secure ID exists

Cause:	Online: The LASID already exists in the eScholar Louisiana Secure ID System.
Solution:	Verify the student’s LASID is correct.

212 Reassign Secure ID equal to Secure ID

Cause:	Online: The LASID and the Reassignment LASID contain the same number.
Solution:	Verify the student’s LASID is correct.

213 Matching Secure ID required for Matching Sponsor

Cause:	Matching Sponsor cannot be entered without Matching ID
Solution:	Enter a valid LASID in Matching ID field.

214 Matching Sponsor required for Matching Secure ID

Cause:	ONLINE: An attempt was made to enter Matching LASID without a Matching Sponsor
Solution:	Enter a valid LEA Code in Matching Sponsor field.

216 Matching Secure ID equal to Secure ID

Cause:	ONLINE: An attempt was made to enter a Matching LASID that equals the LASID.
Solution:	Verify the Matching LASID and reenter.

217 Matching Sponsor cannot be your own

Cause:	An attempt was made to enter a matching Sponsor Code that equals your own Sponsor Code
Solution:	Verify the Matching Sponsor Code and reenter

220 Invalid Partial Last Name

Cause:	First 3 characters of student’s Last name are required.
Solution:	Verify the student’s Partial Last Name and resubmit as necessary

221 Invalid Partial First Name

Cause:	First character of student’s First name is required.
Solution:	Verify the student’s correct Partial First Name and resubmit as necessary

240 Invalid Day of Birth

Cause:	Must be a valid day and month combination
Solution:	Verify the student’s correct Day of Birth and resubmit as necessary

250 Invalid Sex Code

Cause:	A Demographic Record (010)contained an invalid value in the Sex Code field
Solution:	Verify and correct the student’s Sex Code (“Y” or “N”).

261 Only ‘Y’ or ‘N’ is acceptable for Ethnicity/Race.

Cause:	A Demographic Record (010) contained an invalid value in the Ethnicity/Race Flag field.
Solution:	Verify and correct the student’s Ethnicity/Race Flag (“Y” or “N”).

262 At least one Ethnicity/Race Flag must be a ‘Y’

Cause:	A Demographic Record (010) does not contain a “y” in at least one of the Ethnicity/Race Flag fields.
Solution:	Verify and correct the student’s Ethnicity/Race Flag At least one of the fields must contain a ‘Y’

266 Invalid Birth Country

Cause:	A Demographic Record (010) contained an invalid Country of Birth Code.
Solution:	Verify and correct the student’s Country of Birth Code.

268 First Entry Date into U.S. is missing

Cause:	A Demographic Record (010) contained an invalid First Entry Into U.S date since the student’s Country of birth is not “US”.
Solution:	Verify and submit the student’s First Entry Into U.S. date if not a naturally born U.S. citizen or change student’s country of birth code to “US” NOTE: When not in use, this field must be filled with spaces (not zeros).

• Fill in the country and date of entry to the Country Entry on the Student Master.

269 First Entry Date into U.S. not allowed

Cause:	A Demographic Record (010) contained the student’s Country of Birth as “US”. If born in U.S., then, a First Entry Date is not allowed.
Solution:	Verify and correct the student’s Country of Birth.

270 First Entry Date into U.S. > Entry Date

Cause:	A Demographic Record (010) contained the student’s First Entry Date in US after the enrollment date.
Solution:	Verify and correct the student’s First Entry Date.

Top of Page

300-349

300 No Enrollments for Student Secure ID

Cause:	No Enrollment Record (040)was transmitted for the LASID indicated, but there was a Demographic Record(010) and/or Discipline Record(s) included.
Solution:	Add the student's Enrollment/Exit Record (040) and resubmit the entire upload file. Each student must have one Demographic (010) and at least one Enrollment/Exit Record (040).

302 Overlapping Enrollments

Cause:	An attempt was made to process an Enrollment/Exit Record (040) with two active Enrollment records; that is, the student appears to be actively enrolled in more than one school at the same time.
Solution:	Verify the correct entry and exit dates for each Enrollment/Exit Record (040) and then resubmit as necessary. Note: Entry date of record with overlapping date will be displayed in error message.

303 Calendar Code required

Cause:	An Enrollment/Exit Record (040) contains a blank Calendar Code.
Solution:	Verify and correct Calendar Code for the student.

304 Invalid Calendar Code

Cause:	An Enrollment/Exit Record (040) contains an invalid Calendar Code for the LEA.
Solution:	Verify the Calendar Code exists in the School Calendar System for the LEA and the particular site at which the student is enrolled.

• Make sure to upload updated calendars before submitting to SIS. Also, if the school site offers the T9 grade level in their Calendar Editor, go to the Calendar program on LEADS and add the T9 grade level to each uploaded calendar that requires it.

310 Invalid Entry Date

Cause:	An Enrollment/Exit Record 040) contains an invalid Entry Date.
Solution:	Verify the Entry Date.is correct for this student (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900).

311 Entry Date greater than Current date

Cause:	Entry Date cannot be greater than "run date" as noted at the top of the Error Report.
Solution:	Correct the student's Date. On the Enrollment/Exit Record (040).

312 Entry Date less than Beginning of School Year

Cause:	An Enrollment/Exit Record (040) for a student contains an Entry Date which is prior to the first day of school for the specified School Session.
Solution:	Verify that the LEA Code, School/Site Code, School Session year and Entry Date are correct. In addition, verify that the school calendar has been entered correctly for this school. Entry Date cannot be prior to the first day of school as entered on school calendar.

• On the setup box of LA SIS Export File, check "Try to Fix Errors" to have the program change the entry date to the first day of school and the code to E1 (Original enrollment within same district) in the file being built.
• Have "Submit SIS Batch Files" checked off on the Demographics tab of Sponsor Site Editor program. Check this item if data for this site is submitted in SIS to the Louisiana Department of Education. This is needed for remote schools (ex: Charter school, etc.) when it is time for state reporting. Otherwise the remote schools would use the 700 calendar code therefore causing an error.

313 Entry Date greater than End of School Year

Cause:	An Enrollment/Exit Record (040) for a student contains an Entry Date which is after the last day of school.
Solution:	Verify that the LEA code, School/Site Code, School Session and Entry Date are correct for this file. Entry Date cannot exceed date of the last day of school as entered on school calendar.

314 Entry Date less than Date School was opened

Cause:	An Enrollment/Exit Record (040) for a student contains a School/Site Code which, when compared against the Sponsor Site Database, was found to be a site which was not yet opened as of the Entry Date entered on the
Solution:	Verify the correct Entry Date. (Direct questions to SystemSupport@la.gov).

315 Entry Date greater than Date School was closed

Cause:	An attempt was made to process an Enrollment/Exit Record (040) for a student whose school has permanently closed, and this closing date precedes the student's Entry Date.
Solution:	Verify that the LEA code, School/Site Code, School Session and Entry Date are correct. The School Closing Date as entered on the Sponsor Site Database cannot precede the Entry Date. (Direct questions to SystemSupport@la.gov).

316 Entry Date not equal first day of school

Cause:	An attempt was made to process and Enrollment/Exit Record (040) with an Entry Reason Code of E1 (Original Enrollment) and an Entry Date > or < the first day of school. (Applies to grades 1‐12,T9.)
Solution:	Verify the Entry Reason Code and Entry Date and resubmit. If the Entry Reason Code is E1, then the Entry Date must equal the first day of school for grades 1‐12, T9.

317 Entry Date Prior to Student’s Birth Date

Cause:	The student’s Entry Date is prior to the students Birth Date.
Solution:	Verify the correct Entry Date.If correct, verify and correct the student’s Date of Birth in the Secure ID System.

319 Entry Date does not fall on instructional day

Cause:	The Entry Date on an Enrollment/Exit Record (040) does not occur on an instructional day as submitted on the calendar(s) provided by the district.
Solution:	Verify and correct Entry Date.

320 Invalid Entry Reason.

Cause:	An Enrollment/Exit Record (040) has an invalid school Entry Reason Code.
Solution:	Verify and correct the school Entry Reason Code.

321 E1 Entry Reason Required for Exit Reason 18

Cause:	An Enrollment/Exit record (040) has an Exit Reason Code 18 (No Show) with an Entry Reason Code other than E1.
Solution:	Verify and correct the Entry Reason Code or Exit reason Code.

322 Improper Entry Reason: Prior Year Enrollment

Cause:	Entry Reason Code A1 or A2 was not used on a rollover student who was enrolled with A1 or A2 during the prior year in the same school.
Solution:	Verify and correct the Entry Reason Code.

323 Incorrect Entry Reason: Prior Year Enrollment

Cause:	Entry Reason Code other than E1, A1, or A2 was used on a rollover student. This student was enrolled during the prior year in same LEA, and did not exit. Only applies to entry dates on first day of school, grades 1 – 12.
Solution:	Verify and correct the Entry Reason Code.

• The wrong entry code was used in the current year that does not concur with the previous year's entry code. Set the student's entry's code back to what is was in the prior year.

324 Entry Reason E1 used on student not a Rollover.

Cause:	Entry Reason Code E1 was used for a student with no prior year enrollment. E1 is reserved for rollover students (prior year enrollment in same LEA without exiting).
Solution:	Verify and correct the Entry Reason Code.

• This usually means either the student was exited last year (typically last day) or the escholar ID is not matching between years. If the student was exited last day of school (which we always say don't do) then you will need to change the enrollment code to a E0 (C7 Gain Entry or Other not meeting other criteria) in the 2021 year. You will also need to verify in the LEADS portal that the student does not have a exit date.

• Students were dropped in state system last year but not matching in JCampus so the drops in state are erroneous and need removing. Fix the drop information in state for former year EOY to fix this error.
• Code E1 (Original enrollment within the same district - EX:Kindergarten) is usually reserved for students first entering a school.
• On the setup box of LA SIS Export File, check "Try to Fix Errors".

Example: If there is a C5, etc and there is no exit date from the previous year, it will change the the code to E1 (Original enrollment within same district) and the entry date to the first day of school in the file being built. Or undo the student's exit date (except SPED students) at the end of the previous year if the student returned to school the current year.

Or for some students, you will need to remove the option for `Fix errors` so that the C7 entry code would be sent, not an E1.

• Check the student's name in the state's information (LEADS) for a name change and/or a SASID change from the previous year to the current year. If needed, make the changes in LEADS.
• Make sure that a student does not have a schedule start/end date that is after the student's exit date.
• A student needs to be checked at the state if they were marked as a graduate the former year. Usually the student was given a grade reassignment to a new grade level. If the new enrollment does not have a SBLC code for the the end of the former school year, they would look like a graduate. The user may have to adjust the state site to not exit the student as a graduate and then re-submit.

326 Grade is not offered in School/Site indicated

Cause:	An attempt was made to process an Enrollment/Exit record (040) in which the Grade Placement did not match the grade configuration noted on the Sponsor Site database.
Solution:	Verify the correct Grade Placement and School/Site Code. (Direct questions to SystemSupport@la.gov) and to verify the grade configuration for the site indicated on the Sponsor Site database.

• If the error is generated from JCampus errors, then check the grade levels on the Sponsor Site Editor to make sure the student's grade levels are checked. If this is an error after submitting to the state DOE LEADS website, then their Sponsor Site will need to be checked with the student's correct grade levels.

327 Incorrect Institution Type for Grade

Cause:	An attempt was made to process an Enrollment/Exit record (040) in which the Grade Placement (PK‐12, T9) is not allowed for school/site code with Institution Type other than 01(school) or 07 (education site—not a school) on Sponsor Site Database.
Solution:	Verify the correct Grade Placement of student. (Direct questions to SystemSupport@la.gov) to verify the Institution Type for the site indicated on the Sponsor Site database. You cannot report students in grades PK‐12, T9 at Central Office Sites (XXX700 or XXX000.)

330 Invalid Enrollment School/Site

Cause:	An attempt was made to process a Record with an incorrect Sponsor Site Database school/site code.
Solution:	Verify the correct school/site code. (Direct questions about the school/site codes to SystemSupport@la.gov).

331 Enrollment School/Site not allowed on SIS

Cause:	An attempt was made to process an Enrollment/Exit record (040) with a School/Site that is not included on the Sponsor Site Database (SPS), or the SIS ‘flag’ is not ‘yes’ in SPS.
Solution:	Verify that the LEA code, School/Site Code and School Session are correct for this file. The School/Site Code on the file must correspond to a school listed on the Sponsor Site Database. (Direct questions about the school/site codes to SystemSupport@la.gov).

332 First 3 positions of Enrollment Site not = LEA

Cause:	An attempt was made to process an Enrollment/Exit record (040) in which the first three positions of the School/Site Code did not match the LEA Code.
Solution:	Verify that the correct School/Site Code has been entered. The first three digits of the School/Site Code must match the LEA Code.

345 Invalid Free/Reduced Lunch

Cause:	An attempt was made to process a Record with an incorrect Free or Reduced Price Lunch/Breakfast Eligibility code
Solution:	Verify that the correct Free or Reduced Price Lunch/Breakfast Eligibility code is used.

Top of Page

350-399

351 Days Absent must be whole or half days

Cause:	A number other than "0" or "5" was sent in the last field of the absences field.
Solution:	Verify that the correct number was entered in the Absences field. An implied decimal exists; for example, if a student is absent five and a half days, this field should contain 0055.

352 Days Absent must be numeric

Cause:	An attempt was made to process a Record with a combination of numeric and non‐numeric data in the absent field.
Solution:	An attempt was made to process a Record with a combination of numeric and non‐numeric data in the absences field.

353 Days Absent exceeds enrollment days

Cause:	An attempt was made to process a Record with more absences than possible days enrolled at that site.
Solution:	Verify the number of absences at that site and resubmit.

354 Days Absent less than Days Suspended

Cause:	The total number of absences for this enrollment is less than the number of days student was suspended out of school.
Solution:	Correct the number of absences so they are at least equal to number of school days student was suspended out‐of‐school. Note: If student was suspended out of school more than once, the total must equal combined number of days suspended.

• Absent days do not match suspended days. The user may need to check the Calendar Editor.

355 Invalid Pre‐Kindergarten Funding Source

Cause:	An attempt was made to process a Record with an invalid Pre‐Kindergarten Funding Source Code.
Solution:	Verify that the Pre‐ Kindergarten Funding Source Code is correct.

356 Pre‐K Funding Source Required for Grade

Cause:	An attempt was made to process a Record that did not contain a Pre‐K Funding Source Code for a student with a grade code of 24 (Pre‐ Kindergarten).
Solution:	Verify the correct grade code for the student. If grade code 24 is correct, provide an appropriate Pre‐K Funding Source Code for that student.

357 Pre‐K Funding Source not allowed for Grade

Cause:	An attempt was made to process a Record that contained a Pre‐K Funding Source code for a student whose Grade Placement is not coded 24 (Pre‐ Kindergarten) or 20 (Preschool).
Solution:	Verify the correct Grade Placement code for the student's record.

358 Grade Placement Invalid for Exit Reason 35

Cause:

An Exit Reason Code 35 (Transferred to LEA monitored Adult Ed) was transmitted with a Grade Placement code other than grade placement represented in a previous enrollment record with the exit reason code 35.

Solution:

Verify that the Exit Reason Code and Grade Placement codes are correct. If a student has been exited with exit reason code 35 in a previous enrollment record, the Grade Placement code of current enrollment record must be equal to the grade level represented in that previous enrollment record. Districts must keep the student enrolled in the same grade level when reporting him as still enrolled across the years.

360 Invalid Exit Date

Cause:	An attempt was made to process an Enrollment/Exit record (040) that contained an invalid date in the Exit Date field.
Solution:	Verify that the Exit Date is correct for this student. Verify that the Exit Date is a valid date (Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900). In addition, verify that the Exit Date is greater than or equal to the student's Entry Date.

361 Exit Date Prior to Entry Date

Cause:	An attempt was made to process an Enrollment/Exit record (040) with an invalid Exit Date.
Solution:	Verify that the Student ID, LEA Code, Site Code, School Session, and Exit Date are correct for this student. Also, verify that the student has been successfully enrolled in this school. If not, resubmit the student's entire file. Exit Date cannot precede the student's Enrollment Date.

362 Exit Date greater than Current Date

Cause:	The Exit Date cannot be greater than "run date" as noted at the top of the Error Report.
Solution:	Correct the student's Exit Date on the Enrollment/Exit Record (040) and resubmit

363 Exit Date less than Beginning of School Year

Cause:	An attempt was made to process an Enrollment/Exit record (040) for a student whose Exit Date is prior to the first day of school for the specified session.
Solution:	Verify that the LEA Code, School/Site Code, School Session year, and Exit Date are correct for this record. In addition, verify that the school calendar has been entered correctly for this school. Exit Date cannot be prior to date of first day of school as entered on the school calendar.

364 Exit Date greater than End of School Year

Cause:	An attempt was made to process an Enrollment/Exit record (040) for a student who’s Exit Date exceeds the date of the last day of school
Solution:	Verify that the LEA code, School/Site Code, School Session and Exit Date are correct for this record. Exit Date cannot exceed date of the last day of school as entered on school calendar.

365 Exit Date less than Date School was Opened.

Cause:	An Enrollment/Exit record (040) has an Exit Date less than the date the school was opened, as noted on the Sponsor Site Database.
Solution:	Verify the correct Exit Date and resubmit.

366 Exit Date greater than Date School was Closed

Cause:	An Enrollment/Exit record (040) has an Exit Date after the permanently closed date for the School/Site Code.
Solution:	Verify that the LEA Code, School/Site Code, School Session, and Exit Date are correct for this Record. The School Closing Date as entered on the Sponsor Site Database cannot precede the Exit Date.

367 Exit Date invalid for Exit Reason code 18

Cause:	An Enrollment/Exit record (040) has an invalid Exit Date for Exit Reason Code 18.
Solution:	Determine whether the correct Exit Reason Code was submitted. If Exit Reason 18 is used correctly, the Exit Date must be on or before October 1 (or September 30, or October 2, depending on which day of the week October 1 falls).

368 Exit Date required for Closed School/Site

Cause:	An Enrollment/Exit record (040) contains a School/Site that has a closed date on the Sponsor Site database.
Solution:	Confirm the correct a School/Site and its closing date. If the school/site is closed, resubmit the student records with an Exit Date and appropriate Exit Reason Code. (Direct questions about the school/site codes to SystemSupport@la.gov).for questions regarding school/site codes.

369 Exit Date does not fall on Instructional Day

Cause:	The Exit Date on an Enrollment/Exit record (040) does not occur on an instructional day as submitted on the calendar(s) provided by the district.
Solution:	Verify and correct the Exit date.

370 Invalid Exit Reason

Cause:	An Enrollment/Exit record (040) contains an invalid Exit Reason Code.
Solution:	Verify and correct the Exit Reason Code.

371 Absences not allowed with Exit Reason 18

Cause:	An Enrollment/Exit record (040) with Exit Reason Code 18 (No show) has absences recorded.
Solution:	Make sure the absences field is blank for a student exited with Exit Reason Code 18 (No Show).

373 No valid Discipline Type for Exit Reason 01

Cause:	If Exit Reason Code is 01 (Expelled) on the Enrollment/Exit record (040), then the corresponding Disciplinary Type on the Discipline record must be 3 (Expulsion/Out‐of‐School).
Solution:	If a student has been exited with Exit Reason Code is 01(Expelled), ensure the submitted Discipline record contains a Disciplinary Type Code of 3 (Expulsion/Out‐of‐School).

374 Grade Placement Invalid for Exit Reason 04

Cause:	An Exit Reason Code 04 (Diploma) on the Enrollment/Exit record (040), was submitted with a Grade Placement Code other than 11 or 12.
Solution:	Verify that the Exit Reason Code and Grade Placement Code are correct. If a student has graduated, the Grade Placement code must be 11 or 12.

375 Invalid Dropout Reason

Cause:	An Enrollment/Exit record (040) contains an invalid value for the Dropout Reason Code .
Solution:	A Dropout Reason Code should only be provided for: 􀁸 Exit Reason Code=02 (Dropped Out), or 􀁸 Exit Reason Code=11 (Transferred to Adult Education), or 􀁸 Exit Reason Code=13 (Transferred to Vocational Technical School). Verify that Dropout Reason Code is correct for this student. Otherwise leave blank.

376 Dropout Reason required for Exit Reason 02

Cause:	An Enrollment/Exit record (040) that contains an Exit Reason Code of 02 (Dropped Out) without the accompanying Dropout Reason Code.
Solution:	If Exit Reason Code 02 Dropped Out) is valid, submit a valid Dropout Reason Code.

377 Dropout Reason Not Allowed for Exit Reason

Cause:	An Enrollment/Exit record (040) contains an invalid value for the Dropout Reason Code
Solution:	A Dropout Reason Code should only be provided for: 􀁸 Exit Reason Code=02 (Dropped Out), or 􀁸 Exit Reason Code=11 (Transferred to Adult Education), or 􀁸 Exit Reason Code=13 (Transferred to Vocational Technical School). Verify the Student ID, LEA Code, Site Code, School Session, and Exit Reason Code are correct.

378 Entry & Exit Date Must = 1st day School for Exit Reason

Cause:	An Enrollment/Exit record (040) with Exit Reason Code 18 (No Show) contains an entry date and exit date not which are not both the first day of school.
Solution:	Verify and correct Entry Date and Exit Date.

379 No matching Enrollment with Grade Reassignment

Cause:	An attempt was made to process an Enrollment/Exit record (040) with Exit reason Code 15 (exit from one grade for reassignment to another grade) without a corresponding Enrollment/Exit Record (040) to re‐enroll the student.
Solution:	Verify that a corresponding Enrollment/Exit Record (040) is submitted with Entry date equal to the same day or next day as the Exit Date on the Enrollment/Exit Record (040) with Exit reason Code 15.

380 Language required

Cause:	An Enrollment/Exit record (040) contains a blank Language Code.
Solution:	Verify and correct the Language Code.

381 English Proficiency required

Cause:	An Enrollment/Exit record (040) contains a blank English Proficiency Code.
Solution:	Verify and include the English Proficiency Code.

• LEP is only determined in our program by the English Proficiency field in Student Master, Country Entry. SIS requires that any student denoted as LEP to have a language code other than English.

382 EL Funding Source required.

Cause:	An attempt was made to process an Enrollment/Exit record (040) for a student with no EL Funding Source Code when the English Learner code is set to 02. The EL Funding Source Code is required if the English Proficiency Code is 02.
Solution:	Include the EL Funding Source Code in all records for which English Proficiency Code is 02.

• LEP is only determined in our program by the English Proficiency field in Student Master, Country Entry. SIS requires that any student denoted as LEP to have a language code other than English and also requires student to have a funding source. So, if the user does not send a language other than English for a LEP student, SIS error 395 will occur. If the user does not choose a LEP Funding Source for English Proficiency code 02 then this SIS error will occur. Other English Proficiency codes do not require a Funding Source. To submit a student correctly in SIS, the user will need to have all three fields correctly populated which are Language Code, English Proficiency, and Funding Source. Also, for SIS, Country of Origin is not a requirement for LEP.

383 Invalid Language

Cause:	An Enrollment/Exit record (040) contains an invalid Language Code
Solution:	Verify and correct the Language Code.

384 Invalid English Proficiency

Cause:	An Enrollment/Exit record (040) contains an invalid English Proficiency Code.
Solution:	Verify and correct the English Proficiency Code and resubmit.

385 Invalid EL Funding

Cause:	An Enrollment/Exit record (040) contains an invalid EL Funding Source Code.
Solution:	Verify and correct the EL Funding Source Code.

386 Invalid Option

Cause:	An Enrollment/Exit record (040) contains an invalid Option Code.
Solution:	Verify and correct the Option Code.

389 Grade Disagrees with Option

Cause:	An Enrollment/Exit record (040) contains a Code that is not valid for the Grade Placement.
Solution:	Verify Option Code andGrade Placement for this student’s enrollment.

392 EL Funding invalid if fully English proficient

Cause:	An attempt was made to process an Enrollment/Exit record (040) with a EL Funding Source Code when the English Proficiency code is set to 01. The EL Funding Source Code must be blank if student is fully English proficient.
Solution:	Change the EL Funding Source Code to blank or change the English Proficiency code to 02.

• The user will need to either add or delete information in Country Entry in Student Master. Example: Remove the Funding Source.

393 Invalid Truancy Flag

Cause:	An Enrollment/Exit record (040) contains a Truancy Flag with a value other than a ‘Y’ or ‘N’.
Solution:	Determine whether the child is truant for the given enrollment record and send either a ‘Y’ or ‘N’

394 Invalid Homeless Indicator

Cause:	An Enrollment/Exit record (040) contains an invalid Homeless Indicator Code. Must be 1, 2, 3, or 4 if a student is homeless, otherwise blank.
Solution:	Verify and correct the Homeless Indicator Code.

395 English Proficiency not = 01, Language = English

Cause:	For a student to be considered English Learner (EL) (English Proficiency code of 02) their primary language code cannot be code 034, English.
Solution:	If a student has qualified for EL determine what their true primary language code is and end this. If the student is not EL then send in an English Proficiency code of 01 Fully English Proficient.

• LEP (EL) is only determined in our program by the English Proficiency field in Student Master, Country Entry. SIS requires that any student denoted as LEP to have a language code other than English. So, if the user does not send a language other than English for a LEP student, this SIS error will occur. If the user does not choose a LEP Funding Source for English Proficiency code 02 then SIS error 382 will occur. Other English Proficiency codes do not require a Funding Source. To submit a student correctly in SIS, the user will need to have all three fields correctly populated which are Language Code, English Proficiency, and Funding Source. Also, for SIS, Country of Origin is not a requirement for LEP.

396 Home Base Site required for alternative sites

Cause:	A student attends an alternative school (based on this school’s classification in SPS) and you must supply a Home Based Site Code to route the student’s information to their home based school.
Solution:	Send a Home Based Site Code to route the student’s information to the school that actually sent a student to the alternative school or Options 3 program (prior to 2011/2012). If your school was incorrectly flagged as an alternative school you may have the school designation changed on SPS.

398 Invalid Home Base Site

Cause:	A Home Based Site Code was sent to route a student’s information to an invalid or ineligible site. School may not be flagged to allow SIS data on SPS.
Solution:	If data in error is Site Code, then, home based school is closed or is an alternative school (based on this school’s classification in SPS). You may have to get the school designations changed on SPS.

399 Home Base Site not allowed

Cause:

The student is not eligible to be routed using the Home Based Site Code because he does not attend an alternative school (based on this school’s classification in SPS) or because he is not enrolled in an Options 3 Pre‐ GED/Skills program (prior to 2011/2012).

Solution:

Remove the Home Based Site Code from this student’s record if not enrolled in an Options 3 Pre‐GED/Skills program (prior to 2011/2012) or alternative school. If he should be listed in an Options 3 Pre‐GED/Skills program (prior to 2011/2012), you will need to make sure this code is being sent on the enrollment record. If the school they attend should be classified as an alternative school, the school’s classification must be changed on Sponsor Site (SPS).

Top of Page

39A-39T

39A Home Base Site is an alternative site

Cause:	A Home Based Site Code was sent to route a student’s information to an alternative site based on the school’s classification on SPS.
Solution:	Verify the correct Home Based Site Code or ask to have the school designation changed on SPS and resubmit.

39B Home Base Site is closed

Cause:	A Home Based Site Code was sent to route a student’s information to a school that is closed on the Sponsor Site Database.
Solution:	Verify the Home Based Site Code or route the student to the LEA level routing site code of xxx999 where the “xxx” represents your 3‐digit LEA code.

39E Unaccompanied Youth Flag is required

Cause:	Unaccompanied Youth Flag is required if Homeless code is not blank.
Solution:	Verify the correct Homeless code designation or add the appropriate Unaccompanied Youth Flag and resubmit.

39F Unaccompanied Youth Flag not allowed

Cause:	Unaccompanied Youth Flag not allowed if Homeless code is blank.
Solution:	Verify the correct Homeless code designation or remove the Unaccompanied Youth Flag and resubmit.

39G Homeless Reason Code is required

Cause:	Homeless Reason Code is required if Homeless code is not blank.
Solution:	Verify the correct Homeless code designation or add the appropriate Homeless Reason code and resubmit.

39H Homeless Reason Code not allowed

Cause:	Homeless Reason Code not allowed if Homeless code is blank.
Solution:	Verify the correct Homeless code designation or remove the Homeless Reason code and resubmit.

39I Invalid Homeless Reason Code

Cause:	The Homeless Reason Code must 01 – 07, 99, or blank if a student is homeless for a given enrollment.
Solution:	Send a valid code value or leave field blank if student was not homeless.

39J Services Provided Flag is required

Cause:	Services Provided Flag is required if Homeless code is not blank.
Solution:	Verify the correct Homeless code designation or add the appropriate Services Provided Flag and resubmit.

39K Services Provided Flag not allowed

Cause:	Services Provided Flag not allowed if Homeless code is blank.
Solution:	Verify the correct Homeless code designation or remove the Services Provided Flag and resubmit.

39L Invalid Services Provided Flag

Cause:	The Services Provided Flag contains something other than a ‘Y’ or ‘N’.
Solution:	Send either a ‘Y’ or ‘N’ for the Services Provided Flag field.

39M Invalid Prior Education Experience to Kindergarten Code

Cause:	The Prior Education Experience to Kindergarten Code must be 01 – 07 or blank if a student is not in Kindergarten for a given enrollment.
Solution:	Send a valid code value or leave field blank if student was not a Kindergartner.

39N Grade not = Kindergarten for Prior Experience to Kindergarten Code

Cause:	An attempt was made to process an Enrollment/Exit Record (040) with Prior Education Experience to Kindergarten Code and grade not Kindergarten.
Solution:	Verify grade, send a valid code value or leave field blank if student was not a Kindergartner, and resubmit.

39S Awaiting Foster Care Placement Flag required

Cause:	Awaiting Foster Care Placement Flag required if Homeless Indicator is not blank.
Solution:	Verify the correct Homeless Indicator designation or add the appropriate Awaiting Foster Care Placement Flag and resubmit.

39T Awaiting Foster Care Placement Flag not allowed

Cause:	On an Enrollment/Exit Record (040) the Awaiting Foster Care Placement Flag not allowed if Homeless Indicator is blank.
Solution:	Verify the correct Homeless Indicator designation or remove the Awaiting Foster Care Placement Flag and resubmit.

Top of Page

500-599

501 Invalid Class Code

Cause:	Class Code does not exist on the CUR database or Class Code = Spaces.
Solution:	Modify Class Code on SIS Class Schedule Record (110) as needed. Modify Class Code on CUR if needed.

• Rerun a partial CUR for the class codes that have the error.

502 Class Data is required

Cause:	Student was enrolled as of Oct. 1 and no Class Schedule Record (110) were submitted. If ‘Class Schedules Only’ selected, then Class Schedule data must not match database.
Solution:	Submit at least one Class Schedule Record (110) for any student enrolled as of Oct. 1.

• Check the schedule start dates of the students as they should be the first day of school.

504 SIS Entry Date > Class End Date

Cause:	The entry date on an Enrollment Record (040) was later than the Class End Date on a corresponding CUR Class Schedule Record associated with this student. This association is based on the Class Code on the student’s Class Schedule Record (110) and Class Code on the CUR record.
Solution:	Either modify the Enrollment Date or Class End Date on the CUR Class Schedule Record or remove the SIS Class Schedule Record (110) from this student’s record set.

505 Duplicate Class Records

Cause:	Duplicate SIS Class Schedule Record (110) records were submitted.
Solution:	Send only one Class Schedule Record (110) record for each class taken.

507 Class Schedule records are not allowed

Cause:	Class Schedule Record (110) records were submitted during an invalid data collection period.
Solution:	Only submit Class Schedule Record (110) records during the Oct. 1 CLASS data collection (Processing Period 2).

509 No open enrollment exists or class record

Cause:	Class Schedule Record (110) records were sent in for a student that had an enrollment entry date = to the enrollment exit date on the SIS database or the Enrollment Record (040)was missing from the upload file.
Solution:	You must resubmit file with a valid open enrollment for each student along with the Class Schedule Records (110).

530 Invalid Class School/Site

Cause:	An attempt was made to process a Class Schedule Record (110) with a site code not found on the Sponsor Site Database.
Solution:	Verify the correct school/site code. (Direct questions about the school/site codes to SystemSupport@la.gov).

550 Invalid K3 Literacy Screener Exception Code

Cause:	An attempt was made to enter an invalid literacy screener exception code.
Solution:	Verify the literacy screener exception code and resubmit.

551 Invalid Grade for K3 Assessment Record

Cause:	An attempt was made to enter a K‐3 assessment record for a student not in grades K‐3.
Solution:	Verify the student’s grade and the necessity of the K‐3 assessment record.

552 Invalid K3 Literacy Screener Test Type Code

Cause:	An attempt was made to enter an invalid literacy screener test type code.
Solution:	Verify the literacy screener test type code and resubmit.

553 Invalid K3 Literacy Score

Cause:	An attempt was made to enter an invalid literacy screener score.
Solution:	Verify the literacy screener score and resubmit. Score value must be 00‐99.

554 Invalid K Entry Assessment Exception Code

Cause:	An attempt was made to enter an invalid K‐3 assessment exception code.
Solution:	Verify the K‐3 assessment exception code and resubmit.

555 Invalid K Entry Assessment Exception for a Grade

Cause:	An attempt was made to enter an invalid K‐3 assessment exception code.
Solution:	Verify the K‐3 assessment exception code and resubmit.

556 Invalid K Entry Assessment Code

Cause:	An attempt was made to enter an invalid K entry assessment code.
Solution:	Verify the invalid K entry assessment code and resubmit. Code value must be 1‐6.

557 Invalid K Entry Assessment for Grade

Cause:	An attempt was made to enter a K entry assessment for a student not in Kindergarten.
Solution:	Verify the student’s grade and the necessity of the Kindergarten entry assessment data.

558 No open enrollment exists

Cause:	K‐3 Assessment Record (140) records were sent in for a student that had an enrollment entry date = to the enrollment exit date on the SIS database or the Enrollment Record (040) was missing from the upload file.
Solution:	You must resubmit the file with a valid open enrollment for each students along with the K‐3 Assessment record (140)

559 Incomplete KEA Assessment

Cause:	A K entry assessment field is blank.
Solution:	Record must contain valid values for all assessment fields.

560 Invalid KEA Assessment

Cause:	A K entry assessment field is populated on a record that contains a K entry assessment exception code.
Solution:	Verify K entry assessment fields are blank when exceptions exist.

561 Incomplete Literacy Data

Cause:	A literacy screener field is blank.
Solution:	Record must contain valid values for all literacy screener fields.

562 Invalid Literacy Data

Cause:	A literacy screener field is populated on a record that contains a literacy screener exception code.
Solution:	Verify literacy screener fields are blank when exceptions exist.

563 Duplicate K‐3 Assessment Record

Cause:	An attempt was made to enter a duplicate K‐3 assessment record.
Solution:	Ensure only one K‐3 assessment record per student and resubmit.

Top of Page

600-699

612 Physical Zip Code Address missing

Cause:	Physical Zip Code Address is required for these students and this record is not complete.
Solution:	Submit a complete Address Record (120) for the student.

613 State missing

Cause:	State Address is required for these students and this record is not complete.
Solution:	Submit a completed Address Record (120) for the student.

614 State Code not entered in upper case

Cause:	An Address Record was submitted for the student in which the State Code was not in upper case.
Solution:	Submit a complete Address Record (120) for the student with the State Code in upper case.

616 Residing Parish Code missing

Cause:	Residing Parish Code is required for these students and this record is not complete.
Solution:	Submit a complete Address Record (120) for the student.

617 Invalid Residing Parish Code

Cause:	An attempt was made to process a Record with an invalid Residing Parish Code.
Solution:	Verify and correct the Residing Parish Code and resubmit.

620 Address Record Type 120 required

Cause:	An attempt was made to process student’s records and an Address Record (120) was not submitted.
Solution:	Submit the required Address Record (120).

• If the user has an address entered, then the issue is out of our control. Contact the state to have this corrected.

621 Address Record Type 120 not allowed

Cause:	An attempt was made to process a Record that contained an Address Record (120).
Solution:	Address Record (120) type not allowed for this LEA. Verify, correct file, and resubmit as necessary.

622 Zip Code must be numeric

Cause:	An Address Record (120) was submitted for the student in which the zip code was not numeric.
Solution:	Submit an Address Record (120) for the student with a numeric zip code.

623 Residing Parish Code not valid for non‐LA address

Cause:	An Address Record (120) was submitted for the student in which the address was located outside LA.
Solution:	Submit an Address Record (120) for the student with Residing Parish Code set to spaces.

624 Invalid Military Base Reside Flag

Cause:	An Address Record (120) was submitted for the student in which the Military Base Reside Flag was something other than ‘Y’ or ‘N’ which is the only 2 valid options for this required field.
Solution:	Determine whether the student resides on a military base for the given record and send either a ‘Y’ or “N’.

625 Zip Code is not a valid length

Cause:	An Address Record (120) was submitted for the student in which the zip code was invalid.
Solution:	Submit an Address Record (120) for the student with a valid zip code.

626 Zip Code is Invalid For the Current District Code

Cause:	An Address Record (120) was submitted for the student in which the zip code was invalid for the current district.
Solution:	Verify the Zip Code on the Address Record (120). If the Zip Code is correct, direct questions regarding the zip code to SystemSupport@la.gov.

628 Invalid Non‐District Funding Site Flag

Cause:	An Address Record (120) was submitted for the student in which the non‐district building flag was invalid.
Solution:	Correct the non‐district funding site flag and resubmit.

Top of Page

700-799

710 Invalid Disability

Cause:	An attempt was made to process a Record with an invalid Section 504 Disability Category Code.
Solution:	Verify and correct the Disability Category Code and resubmit.

711 First Disability required

Cause:	An attempt was made to process a Record without Disability Category Code.
Solution:	Verify and submit Section 504 Record (130) with the Disability Category Code. At least one disability is required for 504 student.

712 Not Used Disabilities must be entered sequentially

Cause:	An attempt was made to process a Record with Disability Category Codes in non‐sequential fields.
Solution:	Verify and submit Section 504 Record (130) with the Disability Category Codes in sequential field order.

713 Invalid IAP Review Date

Cause:	An attempt was made to process a Record that contained an invalid value in the student's IAP Review Date field.
Solution:	Verify that the IAP Review Date provided is a valid date (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900). In addition, verify that the IAP Review Date provided is before the current date. IAP Review Date should be in the format MMDDYYYY.

714 Invalid Last 504 Evaluation Date

Cause:	An attempt was made to process a Record that contained an invalid value in the student's Last 504 Evaluation Date field.
Solution:	Verify that the Last 504 Evaluation Date provided is a valid date (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900). In addition, verify that the Last 504 Evaluation Date provided is before the current date. Last 504 Evaluation Date should be in the format MMDDYYYY.

• Make sure the last evaluation date is not blank.

715 Last 504 Evaluation Date is missing

Cause:	The student’s Section 504 Record (130) does not include Last 504 Evaluation Date. This is a required field for 504 students.
Solution:	Fill in the student’s Last 504 Evaluation Date and resubmit file.

716 IAP Review Date Prior to Student’s Birth Date

Cause:	An attempt was made to process a Record that contained a birth date after the student’s IAP Review Date.
Solution:	Verify the student’s birth date in the eScholar Louisiana Secure ID System and/or IAP Review Date and resubmit if needed.

717 Last 504 Evaluation Date prior to Student’s Birth Date

Cause:	An attempt was made to process a Record that contained a birth date after the student’s Last 504 Evaluation Date.
Solution:	Verify the student’s birth date in eScholar Louisiana Secure ID System and/or Last 504 Evaluation Date and resubmit if needed.

719 Duplicated Disability not allowed

Cause:	An attempt was made to process a Record that contained duplicate Disability Category Codes. Disability cannot be duplicated within the 7 occurrences.
Solution:	Verify Disability Category Codes, correct file and resubmit as necessary.

720 Disabilities must be entered in numeric order

Cause:	An attempt was made to process a Record that contained Disability Category Codes that were not in numeric order. Disability Category Codes must be entered in numeric order (least to greatest).
Solution:	Verify Disability Category Codes, correct file and resubmit as necessary.

721 Invalid 504 Services Exit Date

Cause:	An attempt was made to process a Record that contained an invalid value in the student's 504 Services Exit Date field.
Solution:	Verify that the 504 Services Exit Date is correct for this student (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900).

722 504 Services Exit Date prior to Student’s Birth Date

Cause:	An attempt was made to process a Record that contained a birth date after the student’s 504 Services Exit Date.
Solution:	Verify the student’s birth date in the eScholar Louisiana Secure ID System and/or 504 Services Exit Date and resubmit if needed.

723 504 Services Exit Date greater than Current Date

Cause:	The 504 Services Exit Date cannot be greater than "run date" as noted at the top of the Error Report.
Solution:	Correct the student's 504 Services Exit Date on the Section 504 Record (130) and resubmit.

724 504 Services Exit Date prior to Last 504 Evaluation Date

Cause:	An attempt was made to process a Record that contained a Last 504 Evaluation Date after the student’s 504 Services Exit Date.
Solution:	Verify the correct Last 504 Evaluation Date and/or 504 Services Exit Date and resubmit.

725 504 Services Exit Date prior to IAP Review Date

Cause:	An attempt was made to process a Record that contained an IAP Review Date after the student’s 504 Services Exit Date.
Solution:	Verify the correct IAP Review Date and/or 504 Services Exit Date and resubmit.

• In the 504 tab of Student Master, compare the exit date against the IAP review date.

726 Invalid Section 504 Services Exit Reason Code

Cause:	An attempt was made to process a Section 504 Record (130) that contained an invalid value in the 504 Services Exit Reason Code field.
Solution:	Verify that the 504 Services Exit Reason Code is correct for this student. 504 Services Exit Reason Code must be a valid code.

727 Invalid Section 504 Accommodation Flag

Cause:	An attempt was made to process a Section 504 Record (130) that contained an invalid value in the one of the 9 Section 504 accommodation fields.
Solution:	Verify that the Section 504 Accommodation fields contain a valid code.

750 Invalid Program Code

Cause:	An attempt was made to process a Program Record (050) that contained an invalid value in the Program Code field.
Solution:	Verify that the Program Code is correct for this student. Program Code must be a valid code.

751 Invalid Program School/Site

Cause:	An attempt was made to process a Program Record (050) that contained an incorrect Sponsor Site Database school/site code.
Solution:	Verify the correct school/site code. (Direct questions about the school/site codes to SystemSupport@la.gov).

752 Invalid Grade for Program Code

Cause:	An attempt was made to process a Program Record (050) that contained an invalid Grade for the Program
Solution:	The Connections Program Code only applies to grade 8. Other Program Codes apply to grades 9‐12.

753 Invalid Program Start Date

Cause:	An attempt was made to process a Program Record (050) that contained an invalid Start Date for the Program.
Solution:	Verify the Program Start Date for this record (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900) in MMDDYYYY format. Correct the Program Start Date for this record and resubmit.

754 No Open Enrollment Exists for Program

Cause:	An attempt was made to process a Program Record (050) for a student that contained an invalid Start Date for the Program Code.
Solution:	Verify the Program Start Date for this record falls between the student’s enrollment entry date and exit date. Correct the Program Start Date for this record and resubmit.

755 Duplicate Program Records not allowed

Cause:	An attempt was made to process a Program Record (050) that contains the same Program Code as an existing record for a specific student.
Solution:	Send only one Program Record (050) for each Program Code in which the student is enrolled. Remove duplicate Program Records.

756 Entry Reason ‘C9’ Required for Program ‘DRP001’

Cause:	An attempt was made to process a Record that contained an invalid Program Entry Reason.
Solution:	For Program ‘DRP001”, the Entry Reason should be ‘C9’.

Top of Page

800-849

800 Perpetrator/Action data not allowed for Exit Reason 18

Cause:	An attempt was made to process a student Perpetrator/Action Record for Exit Reason Code 18 (No Show).
Solution:	Verify the correct Exit Reason Code and resubmit.

801 Event ID required

Cause:	An attempt was made to process a Record with spaces in the Event ID field.
Solution:	Event ID is required on all Event; Perpetrator and instance; Actions and Interventions; and Victim records. Include the correct Event ID and resubmit.

• On the LEADS website, go to the Event tab first and submit the Event file. Then go to the SIS tab and submit the SIS file.

802 Invalid Event Site Code

Cause:	An attempt was made to process an Event Record (007) with an incorrect Sponsor Site Database school/site code.
Solution:	Verify the correct school/site code. (Direct questions about the school/site codes toSystemSupport@la.gov).

803 Invalid Event Date

Cause:	An attempt was made to process an Event Record (007) that contained an invalid value in the Event DateFirst_Entry field.
Solution:	Verify that the Event Date is correct for this record (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900) in MMDDYYYY format and correct Event Date.

804 Event Date greater than current date

Cause:	Event Date cannot be greater than "run date" as noted at the top of the Error Report.
Solution:	Correct the Event Date on the Event Record (007) and resubmit.

805 Event Date less than Beginning of Event Reporting Year

Cause:	An attempt was made to process an Event Record (007) for an Event where the Event Date is prior to the first day of the Event Reporting Year for the specified School Session Year. Event Reporting Year begins on July 1 of a given School Session Year and ends on June 30 of the next calendar year.
Solution:	Verify that the LEA Code, School/Site Code, School Session year and Event Date are correct for this file.

806 Event Date greater than Event Reporting Year

Cause:	An attempt was made to process an Event Record (007) for an Event where the Event Date exceeds the last day of the Event Reporting Year for the specified School Session Year. Event Reporting Year begins on July 1 of a given School Session Year and ends on June 30 of the next calendar year.
Solution:	Verify that the LEA Code, School/Site Code, School Session year and Event Date are correct for this file.

807 Event Date less than date the school was opened

Cause:	An attempt was made to process an Event Record (007) where the Event Date was before the date the school was opened.
Solution:	Correct the Event Date and resubmit.

808 Event Date greater than date the school was closed

Cause:	An attempt was made to process an Event Record (007) where the Event Date was after the date the school was closed.
Solution:	Correct the Event Date and resubmit.

809 Invalid Time Code

Cause:	An attempt was made to process an Event Record (007) that contained an invalid value in the Time Code field.
Solution:	Verify that the Time Code is correct for this Event. Time Code must be a valid code.

810 Invalid Location Code

Cause:	An attempt was made to process an Event Record (007) that contained an invalid value in the Location Code field.
Solution:	Verify that the Location Code is correct for this Event. Location Code must be a valid code.

811 Invalid Event Primary Reason Code

Cause:	An attempt was made to process an Event Record (007) that contained an invalid value in the Event Primary Reason Code field.
Solution:	Verify that the Primary Reason Code is correct for this Event. Primary Reason Code must be a valid code.

812 Invalid Perpetrator ID

Cause:	An attempt was made to process a Perpetrator and Instance Record that did not contain a valid Perpetrator ID Number according to Perpetrator Type Code.
Solution:	Enter a valid Perpetrator ID Number for the Perpetrator and Instance Record. If Perpetrator is a student enrolled in your LEA, you must send the Student ID. If Perpetrator is a non‐student or a student not enrolled in your LEA, you must send a P******** number and must be tracked by LEA.

813 Invalid Perpetrator Site Code

Cause:	An attempt was made to process a Perpetrator and Instance Record with an incorrect Sponsor Site Database school/site code.
Solution:	Verify the correct school/site code. If you feel the data is correct, direct questions to SystemSupport@la.gov to verify the school/site code.

814 Invalid Perpetrator Site Code for Perpetrator Type

Cause:	An attempt was made to process a Perpetrator and Instance Record with an incorrect Sponsor Site Database school/site code for a perpetrator who is not an employee and not a student.
Solution:	Verify the correct Perpetrator Type Code or correct site code. You will use the XXX999 site code to indicate the incident took place in your LEA but that the perpetrator was not associated with a specific site as an employee or a student.

815 Invalid Perpetrator Type Code

Cause:	An attempt was made to process a Perpetrator and Instance Record that contained an invalid value in the Perpetrator Type Code field. An attempt was made to process a Perpetrator and Instance Record that contained an invalid value in the Perpetrator Type Code field. An attempt was made to process a Perpetrator and Instance Record that contained an invalid value in the Perpetrator Type Code field.
Solution:	Verify that the Perpetrator Type Code is correct for this Perpetrator. Perpetrator Type Code must be a valid code.

816 Invalid Perpetrator Primary Reason Code

Cause:	An attempt was made to process a Perpetrator and Instance Record that contained an invalid value in the Perpetrator Primary Reason Code field.
Solution:	Verify that the Perpetrator Primary Reason Code is correct for this Perpetrator. Perpetrator Primary Reason Code must be a valid code.

817 Invalid Firearms and Explosives Weapons Code

Cause:	An attempt was made to process a Perpetrator and Instance Record with an invalid Firearms and Explosives Weapons Code.
Solution:	Verify and correct the Firearms and Explosives Weapons Code and resubmit. Verify and correct the Firearms and Explosives Weapons Code and resubmit.

818 Firearms and Explosives Weapons Code required

Cause:	Perpetrator Primary Reason Code 13 or 30 was submitted without including a Firearms and Explosives Weapon Code.
Solution:	Include the correct Firearms and Explosives Weapons Code and resubmit.

819 Firearms and Explosives Weapons Code not allowed

Cause:	An attempt was made to process a Perpetrator and Instance Record with a Firearms and Explosives Weapon Code included with a Perpetrator Primary Reason Code other than 13 or 30.
Solution:	Firearms and Explosives Weapons Code may be included only when Perpetrator Primary Reason Code 13 or 30 is submitted. Verify the correct Perpetrator Primary Reason Code and resubmit.

820 Invalid Other Weapons Code

Cause:	An attempt was made to process a Perpetrator and Instance Record with an invalid Other Weapons Code.
Solution:	Verify and correct the Other Weapons Code and resubmit.

821 Other Weapons Code required

Cause:	Perpetrator Primary Reason Code 14, 15 or 31 was submitted without including an Other Weapons Code.
Solution:	Include the correct Other Weapons Code and resubmit.

822 Other Weapons Code not allowed

Cause:	An attempt was made to process a Perpetrator and Instance Record with an Other Weapons Code included with a Perpetrator Primary Reason Code other than 14, 15, or 31.
Solution:	Other Weapons Code may be included only when Perpetrator Primary Reason Code 14, 15 or 31 is submitted. Verify the correct Perpetrator Primary Reason Code and resubmit.

824 Drug Related Flag of 'Y' is required

Cause:	NOTE: This error was not in the most current guides but listed here anyway.
Solution:

• Add a check for "Drugs" on the Discipline Posting Admin page, "Event Related To" area.

827 Invalid Bullying Code

Cause:	An attempt was made to process a Perpetrator and Instance Record that contained an invalid value in the Bullying Code field. Current codes are 01‐04 and this field may be blank, but may not be anything else.
Solution:	Verify that the Bullying Code is correct for this Perpetrator. Bullying Code must be a valid code or leave field blank if Perpetrator Primary Reason Code is not 35Bullying or 36 Cyberbullying.

828 Bullying Code 04 is required

Cause:	Bullying Code 04 – Cyberbullying is required if Perpetrator Primary Reason Code is 36 Cyberbullying
Solution:	Verify the correct Perpetrator Primary Reason Code designation or add the appropriate Bullying Code and resubmit.

829 Bullying Code 04 not allowed

Cause:	Bullying Code of 04 not allowed if Perpetrator Primary Reason Code is not 36 Cyberbullying.
Solution:	Verify the correct Perpetrator Primary Reason Code designation or add the appropriate Bullying Code and resubmit.

830 Bullying Code 01‐03 is required

Cause:	Bullying Code is required if Perpetrator Primary Reason Code is 35 Bullying.
Solution:	Verify the correct Perpetrator Primary Reason Code designation or add the appropriate Bullying Code and resubmit.

831 Bullying Code 01‐03 not allowed

Cause:	Bullying Code of 01 – Harassment, 02 – intimidation or 03 – Bullying not allowed if Perpetrator Primary Reason Code is not 35 Bullying.
Solution:	Verify the correct Perpetrator Primary Reason Code designation or add the appropriate Bullying Code and resubmit.

832 Invalid Aggression Flag

Cause:	Aggression Flag of ‘Y’ or ‘N’ is required if Perpetrator Primary Reason Code is 35 Bullying or 36 Cyberbullying.
Solution:	Verify the correct Perpetrator Primary Reason Code designation or add the appropriate Aggression Flag and resubmit.

833 Aggression Flag not allowed

Cause:	Aggression Flag not allowed if Perpetrator Primary Reason Code is not 35 Bullying or 36 Cyberbullying.
Solution:	Verify the correct Perpetrator Primary Reason Code designation or remove the Aggression Flag and resubmit.

834 Electronic Aggression Flag is required

Cause:	Electronic Aggression Flag of ‘Y’ is required if Perpetrator Primary Reason Code is 36 [Cyberbullying].
Solution:	Verify the correct Perpetrator Primary Reason Code designation or submit Electronic Aggression Flag of ‘Y’ and resubmit.

835 Electronic Aggression Flag not allowed

Cause:	Electronic Aggression Flag is not allowed if Perpetrator Primary Reason Code is not 36 Cyberbullying.
Solution:	Verify the correct Perpetrator Primary Reason Code designation or submit Electronic Aggression Flag of ‘N’ and resubmit.

• Example: Change 45 Bullying to 77 Cyber Bullying.

836 At least one Aggression Flag must be a ‘Y’

Cause:	An attempt was made to process a Perpetrator and Instance Record that contained all ‘N’s in the Aggression Flag fields for record with Perpetrator Primary Reason Code of 35 Bullying or 36 Cyberbullying.
Solution:	Verify the correct Aggression Flags, ‘Y’ or ‘N’. At least one of the 4 new aggression flag fields must contain a ‘Y’.

• Add an Aggression flag for the SIS incident of code "35 Bullying" This will show on page 1 and 3 of the referral. Don't use "Electronic Aggression" codes with code "35 Bullying".
• If "77 Cyber Bullying" is chosen, then use one of the "Electronic Aggression" codes ONLY.
• Note to NOT use "99 Other" code in the "Motivations" field.

837 Witness Count must be numeric

Cause:	An attempt was made to process a Perpetrator and Instance Record with a combination of numeric and non‐numeric data in the Witness Count field.
Solution:	If no witnesses exist, this field must be filled with zeros (00). Witness Count must be numeric (00 or greater).

838 Invalid Physical Evidence Code

Cause:	An attempt was made to process a Perpetrator and Instance Record that contained an invalid value in the Physical Evidence Code field.
Solution:	Verify that the Physical Evidence Code is correct for this Perpetrator. Physical Evidence Code must be a valid code.

839 Invalid Action/Intervention Code for Crimes of Violence

Cause:	An invalid Action /Intervention Code was used for reporting a crime of violence.
Solution:	Correct the Action /Intervention Code and resubmit.

844 Invalid Perpetrator Parent Contacted Flag

Cause:	The Perpetrator Parent Contacted Flag field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the parent was contacted regarding Event for the given record and send either a ‘Y’ or ‘N’.

845 Invalid Reported to Law Enforcement Flag

Cause:	The Reported to Law Enforcement Flag field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Event was reported to Law Enforcement for the given record and send either a ‘Y’ or ‘N’.

846 Invalid Arrest Resulted Flag

Cause:	The Arrest Resulted Flag field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Event resulted in arrest of Perpetrator for the given record and send either a ‘Y’ or ‘N’.

847 Invalid Serious Injury Resulted Flag

Cause:	The Serious Injury Resulted Flag field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Event resulted in Serious Injury to Perpetrator for the given record and send either a ‘Y’ or ‘N’.

848 Invalid Perpetrator Medical Treatment Flag

Cause:	The Perpetrator Medical Treatment Flag field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Perpetrator required offsite medical treatment for the given record and send either a ‘Y’ or ‘N’.

Top of Page

850-899

850 Action = No action, other data not allowed

Cause:	An attempt was made to process an Actions and Interventions Record (092) with Action/Intervention Code of 000 – No Action with data entered at position(s) 49 through 120
Solution:	Verify Action/Intervention Code and remove data. Other data not allowed for Action/Intervention Code of 000 – No Action.

• Check the action record versus the enrollment dates.

851 Action Record had no matching Enrollment Record

Cause:

An attempt was made to process an Actions and Interventions Record (092) for a student who had an Entry Date on the Enrollment/Exit Record (040) that occurs after the Discipline Start Date and/or an Exit Date that occurs before the Discipline Start Date. Entry/exit dates and site codes must correspond on enrollment, exit, and Action and Intervention records. For example, if a student has an Entry Date of 9/16, yet a Disciplinary Start Date is stated to be 9/2, there is an error because the student was not enrolled on that date.

Solution:

Confirm and correct the dates as necessary and resubmit.

• A user posted a discipline record for a student that was not enrolled in the school on the discipline record date.

852 Invalid Action/Intervention Code

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Action/Intervention Code field.
Solution:	Verify that the Action/Intervention Code is correct for this Event. Action/Intervention Code must be a valid code

853 No valid Action/Intervention Code for Exit Reason 01 (expelled)

Cause:	If Exit Reason Code is 01 (Expelled) on the Enrollment/Exit record (040), then the corresponding Action/Intervention Code on the Actions and Interventions record must be 003 (Expulsion/Out‐of‐School).
Solution:	If a student has been exited as expelled, ensure that the submitted Actions and Interventions record contains an Action/Intervention Code of 003.

• In the Discipline Posting on the Admin page, Code, Action Taken By Aministation, chose/Add 30-003 Expulsion Out Of School and then Save.

854 No Exit Reason of 01 (Expelled) for Action Expulsion

Cause:	An attempt was made to process an Actions and interventions Record (092) with an Action/Intervention Code =003 [Expulsion‐Out‐of‐ School] without an accompanying Enrollment/Exit Record (040) with an Exit Reason Code of 01 (Expelled).
Solution:	Confirm and correct the Exit Reason and/or Action/Intervention Codes and resubmit. Note: For an Out‐of‐School Expulsion (Action/Intervention Code 003), the Discipline Start Date must be the same date as the Exit Date.

855 Overlapping Suspension/Expulsion Records

Cause:

An attempt was made to process a file with more than one Action and Intervention Record (092) with Discipline Start Dates that overlap. Exceptions:

Solution:

An Action/Intervention Code 002, suspension or 003, expulsion (Out‐of‐School) can overlap with a 004, 005, 006, or 007 Note: Should occur on or after the start date if it overlaps another suspension or expulsion. An Action/Intervention Code 004, suspension or 005, expulsion (In‐School) can overlap with a 002, 003, 006, or 007 Note: Must occur on or before the start date of the Action/Intervention Code 002 or 003 discipline it overlaps An Action/Intervention Code 006, suspension or 007, expulsion (Alternate Site) can overlap with a 002, 003, 004, or 005 Note: Must occur on or before the start date of the Action/Intervention Code 002 or 003 discipline it overlaps Confirm the correct Discipline Start Dates and Action/Intervention Codes and resubmit.

• Referrals can have overlapping dates but only for certain codes.
• Referrals can overlap administrative actions if the admin code translates to state code 002 (OSS) or 003 (Expulsion). These codes can overlap an existing discipline suspension/expulsion record IF the other record is state code 004,005,006 or 007 and the existing record has a start date on or before the new record.
• Referrals can overlap administrative actions if the admin code translates to state code 004 (ISS) or 005 (In School Expulsion). These codes can overlap an existing discipline suspension/expulsion record IF the other record is state code 002,003,006 or 007. The existing record has to have a start date on or after the new record if code is 002 or 003. Codes 006 and 007 do not matter for dates.
• Referrals can overlap administrative actions if the admin code translates to state code 006 (ALT Suspension) or 007 (ALT Expulsion). These codes can overlap an existing discipline suspension/expulsion record IF the other record is state code 002,003,004 or 005. The existing record has to have a start date on or after the new record if code is 002 or 003. Codes 004 and 005 do not matter for dates.

856 Invalid Discipline Start Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Discipline Start DateFirst_Entry field.
Solution:	Verify that the Discipline Start Date is correct for this record (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900) in MMDDYYYY format and correct Discipline Start Date.

857 Discipline Start Date greater than current date + 1 month

Cause:	Discipline Start Date cannot be greater than "run date" as noted at the top of the Error Report + 1 month.
Solution:	Correct the Discipline Start Date on the Actions and Interventions Record (092) and resubmit.

• The discipline date was at the end of the school year and into the summer. Move to the beginning of the next school year.

858 Discipline Start Date less than Beginning of School Year

Cause:

An attempt was made to process an Actions and interventions Record (092) for an Action/Intervention where the Discipline Start Date is prior to the first day of school for the specified School Session Year.

Solution:

Verify that the LEA Code, School/Site Code, School Session year and Discipline Start Date are correct for this file. In addition, verify that the school calendar has been entered correctly for this school. Discipline Start Date cannot be prior to date of first day of school as entered on school calendar table. (Direct questions about the dates recorded on the school calendar to SystemSupport@la.gov).

859 Discipline Start Date greater than End of School Year

Cause:	An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention where the Discipline Start Date exceeds the date of the last day of school.
Solution:	Verify that the LEA code, School/Site Code, School Session year and Discipline Start Date are correct for this file. Discipline Start Date cannot exceed date of the last day of school as entered on school calendar table.

860 Discipline Start Date less than Date School was opened

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a School/Site Code which, when compared against the Sponsor Site Database, was found to be a site which was not yet opened as of the Discipline Start Date entered on the student record.
Solution:	Verify the correct Discipline Start Date. (Direct questions about the opening date for the school/site to SystemSupport@la.gov).

861 Discipline Start Date greater than Date School was closed

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a School/Site Code which, when compared against the Sponsor Sitedatabase, was found to be a site which has permanently closed; and this closing date precedes the student's Discipline Start Date.
Solution:	Verify that the LEA code, School/Site Code, School Session year and Discipline Start Date are correct for this file. The School Closing Date as entered on the Sponsor Site Database cannot precede the Discipline Start Date. (Direct questions regarding closing dates to SystemSupport@la.gov.)

862 Invalid Discipline Return Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Discipline Return Date field.
Solution:	Verify that the Discipline Return Date is correct for this record (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900) in MMDDYYYY format and correct Discipline Return Date.

863 Discipline Return Date <= Disc Start Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a Discipline Return Date that is before or the same as the Discipline Start Date.
Solution:	A Discipline Return Date cannot occur before the Discipline Start Date or on the same day. Confirm the correct dates and resubmit.

• The Start and End Dates must have at least one day difference. Also, for the last day of school add one day.

864 Discipline Return Date < Begin School Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a Discipline Return Date that is before the beginning of the school year.
Solution:	Confirm the correct dates and resubmit.

865 Discipline Return Date < Open School Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a Discipline Return Date less than the date the school was opened, as noted on the Sponsor Site database.
Solution:	Confirm the correct Discipline Return Date. If the date the school was opened appears to be incorrect on the Sponsor Site database, direct questions to SystemSupport@la.gov).

866 Discipline Return Date > End School Date + 1

Cause:	An attempt was made to process an Actions and Interventions Record (092) (Action/Intervention Code 002, 004, or 006) with a Discipline Return Date greater than the last day of school +1.
Solution:	Confirm the correct Discipline Return Date and resubmit.

867 Discipline Return Date > Discipline Start Date + 3 years

Cause:	An attempt was made to process an Actions and Interventions Record (092) (Action/Intervention Code 003, 005, or 007) with a Discipline Return Date greater than the Discipline Start Date + 3 years.
Solution:	Confirm the correct Discipline Return Date and resubmit.

868 Invalid Discipline Administered Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Discipline Administered Date field.
Solution:	Verify that the Discipline Administered Date is correct or this record (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900) in MMDDYYYY format and correct Discipline Administered Date.

869 Discipline Administered Date greater than current date

Cause:	Discipline Administered Date cannot be greater than "run date" as noted at the top of the Error Report.
Solution:	Correct the Discipline Administered Date on the Actions and Interventions Record (092) and resubmit.

• In Discipline Posting, on the Admin page, correct the "Action Taken By School Administration - Date" column to a date not greater than the current run date as noted at the top of the Error Report .

870 Alternate Site Code is Required

Cause:	An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention with no Alternate Site Code
Solution:	Alternate Site Code is required for Action Type = “006’, “007”, “010.

871 Alternate Site Code is required for Action

Cause:	An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention with an Alternate Site Code.
Solution:	Alternate Site Code not allowed if Action Type is not = “006’, “007”, “010. Alternate Site Code must be blank.

872 Discipline Administered Date less than Beginning of School Year

Cause:

An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention where the Discipline Administered Date is prior to the first day of school for the specified School Session.

Solution:

Verify that the LEA Code, School/Site Code, School Session year and Discipline Administered Date are correct for this file. In addition, verify that the school calendar has been entered correctly for this school. Discipline Administered Date cannot be prior to date of first day of school as entered on school calendar table. To verify whether the correct dates are recorded on the school calendar direct questions to SystemSupport@la.gov).

873 Discipline Administered Date greater than End of School Year

Cause:	An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention where the Discipline Administered Date exceeds the date of the last day of school.
Solution:	Verify that the LEA code, School/Site Code, School Session year and Discipline Administered Date are correct for this file. Discipline Administered Date cannot exceed date of the last day of school as entered on school calendar table.

874 Discipline Administered Date less than Date School was opened

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a School/Site Code which, when compared against the Sponsor Site Database, was found to be a site which was not yet opened as of the Discipline Administered Date entered on the student record.
Solution:	Verify the correct Discipline Administered Date. (Direct questions about the opening date for a school/site to SystemSupport@la.gov.)

875 Discipline Administered Date greater than Date School was closed

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a School/Site Code which, when compared against the Sponsor Site database, was found to be a site which has permanently closed, and this closing date precedes the student's Discipline Administered Date.
Solution:	Verify that the LEA code, School/Site Code, School Session year and Discipline Administered Date are correct for this file. The School Closing Date as entered on the Sponsor Site Database cannot precede the Discipline Administered Date. (Direct questions about the school/site codes closing date to SystemSupport@la.gov).

876 Corporal Punishment Directly Authorized by Uninvolved Third Party Flag is required

Cause:	Corporal Punishment Directly Authorized by Uninvolved Third Party Flag of ‘Y’ or ‘N’ is required if Action/Intervention Code is 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or add the appropriate Corporal Punishment Directly Authorized by Uninvolved Third Party Flag and resubmit.

877 Corporal Punishment Directly Authorized by Uninvolved Third Party not allowed

Cause:	Corporal Punishment Directly Authorized by Uninvolved Third Party Flag not allowed if Action/Intervention Code is not 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or remove the Corporal Punishment Directly Authorized by Uninvolved Third Party Flag and resubmit.

878 Invalid Administrator Type Code

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Administrator Type Code field. Current codes are 01‐10, 99 and this field may be blank but may not be anything else.
Solution:	Verify that the Administrator Type Code is correct for this Event. Administrator Type Code must be a valid code or leave field blank if Action/Intervention Code is not 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.

879 Administrator Type Code is required

Cause:	Administrator Type Code is required if Action/Intervention Code is 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or add the appropriate Administrator Type Code and resubmit.

880 Administrator Type Code not allowed

Cause:	Administrator Type Code not allowed if Action/Intervention Code is not 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or remove the Administrator Type Code and resubmit.

881 Invalid Administrator’s Last Name

Cause:

An attempt was made to process an Actions and Interventions Record (092) with an invalid Administrator Last Name. The first character the Last Name must not be blank and positions 2‐16 must be A‐Z, dash, period, apostrophe or space. Any name ending with space will result in an error. Last Name has to be at least characters and not greater than 20 characters. For example, if administrator’s name is X, data has to be entered as X‐.

Solution:

Verify the Administrator’s correct Last Name and resubmit as necessary.

882 Administrator’s Last Name is required

Cause:	Administrator’s Last Name is required if Action/Intervention Code is 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or add the appropriate Administrator’s Last Name and resubmit.

883 Administrator’s Last Name is not allowed

Cause:	Administrator’s Last Name is not allowed if Action/Intervention Code is not 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or remove the Administrator’s Last Name and resubmit.

884 Invalid Administrator’s First Name

Cause:	An attempt was made to process an Actions and Interventions Record (092) with an invalid Administrator First Name. The first character of the First Name must not be a space and each character in positions 2‐16 must be A‐Z, dash, period, apostrophe or space. Any name ending with space will result in an error.
Solution:	Verify the Administrator’s correct First Name and resubmit as necessary.

885 Administrator’s First Name is required

Cause:	Administrator’s First Name is required if Action/Intervention Code is 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or add the appropriate Administrator’s First Name and resubmit.

886 Administrator’s First Name is not allowed

Cause:	Administrator’s First Name is not allowed if Action/Intervention Code is not 090 Physical Restraint, 095 Mechanical Restraints, 100 Confinement with seclusion or 180 Corporal Punishment.
Solution:	Verify the correct Action/Intervention Code designation or remove the Administrator’s First Name and resubmit.

887 Invalid Manifestation Hearing Date

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Manifestation Hearing Date First_Entry field.
Solution:	Verify that the Manifestation Hearing Date is correct for this record (i.e., Month > 0 and < 13, Day > 0 and < the maximum number of days in the month entered, and Year > 1900) in MMDDYYYY format and correct Manifestation Hearing Date.

888 Manifestation Hearing Date greater than current date

Cause:	Manifestation Hearing Date cannot be greater than "run date" as noted at the top of the Error Report.
Solution:	Correct the Manifestation Hearing Date on the Actions and Interventions Record (092) and resubmit.

889 Manifestation Hearing Date less than Beginning of School Year

Cause:

An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention where the Manifestation Hearing Date is prior to the first day of school for the specified School Session.

Solution:

Verify that the LEA Code, School/Site Code, School Session year and Manifestation Hearing Date are correct for this file. In addition, verify that the school calendar has been entered correctly for this school. Manifestation Hearing Date cannot be prior to date of first day of school as entered on school calendar table. (To verify whether the correct dates are recorded on the school calendar, direct questions to SystemSupport@la.gov.)

890 Manifestation Hearing Date greater than End of School Year

Cause:	An attempt was made to process an Actions and Interventions Record (092) for an Action/Intervention where the Manifestation Hearing Date exceeds the date of the last day of school.
Solution:	Verify that the LEA code, School/Site Code, School Session year and Manifestation Hearing Date are correct for this file. Manifestation Hearing Date cannot exceed date of the last day of school as entered on school calendar table.

891 Manifestation Hearing Date less than Date School was opened

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a School/Site Code which, when compared against the Sponsor Site Database, was found to be a site which was not yet opened as of the Manifestation Hearing Date entered on the student record.
Solution:	Verify the correct Manifestation Hearing Date. Questions about the opening date for a school/site may be directed to SystemSupport@la.gov.

892 Manifestation Hearing Date greater than Date School was closed

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a School/Site Code which, when compared against the Sponsor Site database, was found to be a site which has permanently closed, and this closing date precedes the student's Manifestation Hearing Date.
Solution:	Verify that the LEA code, School/Site Code, School Session year and Manifestation Hearing Date are correct for this file. The School Closing Date as entered on the Sponsor Site Database cannot precede the Manifestation Hearing Date. (Direct questions about the school/site codes closing date to SystemSupport@la.gov).

893 Invalid Disability‐Related Flag

Cause:	An attempt was made to process an Actions and Interventions Record (092) that contained an invalid value in the Disability‐Related Flag field.
Solution:	Verify the correct Disability‐ Related Flag. Current values are ‘Y’ or ‘N’.

894 Disability‐Related Flag of ‘Y’ is not allowed

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a Disability‐Related Flag of ‘Y’ and no Manifestation Hearing Date.
Solution:	Verify Manifestation Hearing Date and Disability‐Related Flag. Disability‐Related Flag can only be “Y” if Manifestation Hearing Date is supplied.

895 Minutes Removed must be numeric

Cause:	An attempt was made to process an Actions and Interventions Record (092) with a combination of numeric and non‐numeric data in the Minutes Removed field.
Solution:	If student was not removed from class from their regular setting, this field must be filled with zeros (000000). If student was removed, the data must be entirely numeric.

896 Invalid Anonymous ID (Victim)

Cause:	An attempt was made to process a Victim Record (093) with an incorrect Anonymous ID.
Solution:	Verify the Anonymous ID. The Anonymous ID cannot include the student’s/employee’s State ID or SSN.

897 Invalid Victim Site Code

Cause:	An attempt was made to process a Victim Record (093) with an incorrect Sponsor Site Database school/site code.
Solution:	Verify the correct school/site code. If the data appear to be correct, direct questions to SystemSupport@la.gov).

898 Victim Site Code invalid for non‐student\non‐employee

Cause:	An attempt was made to process a Victim Record (093) with an incorrect Sponsor Site Database school/site code for a victim who is not an employee or is not a student.
Solution:	Verify the correct Victim Type Code or correct site code. You will use the XXX999 site code to indicate incident took place in your LEA but that the victim was not associated with a specific site as an employee or student. If the data appear to be correct direct questions to SystemSupport@la.gov).

899 Invalid Victim Type Code

Cause:	An attempt was made to process a Victim Record (093) that contained an invalid value in the Victim Type Code field.
Solution:	Verify that the Victim Type Code is correct for this Victim. Victim Type Code must be a valid code.

Top of Page

89A-89Z

89A Age at Incident Date must be numeric

Cause:	An attempt was made to process a Victim Record (093) with a combination of numeric and non‐numeric data in the Age at Incident Date field.
Solution:	Verify the correct Age at Incident Date and resubmit. The data must be entirely numeric. If victim was less than one, round up to 001.

89B Invalid Victim Gender

Cause:	An attempt was made to process a Victim Record (093) that contained an invalid value in the Gender (Victim) field.
Solution:	Verify the correct Gender Code for the victim. Gender Code must be either 'M' or 'F'.

89C Invalid Grade Level at Incident Date

Cause:	An attempt was made to process a Victim Record (093) that contained an invalid value in the current Grade Level at Incident Date field.
Solution:	Verify the correct Grade Level at Incident Date and resubmit. Also, you must enter 00 if Victim was not a student.

89D Invalid Ethnicity Flag

Cause:	An attempt was made to process a Victim Record (093) that contained an invalid value in the Ethnicity/Race Flag fields.
Solution:	Verify the correct Ethnicity/Race Flags, ‘Y’ or ‘N’.

89E Invalid Race Flag

Cause:	An attempt was made to process a Victim Record (093) that contained an invalid value in the Ethnicity/Race Flag fields.
Solution:	Verify the correct Ethnicity/Race Flags, and submit ‘Y’ or ‘N’.

89F At least one Ethnicity/Race Flag must be a ‘Y’

Cause:	An attempt was made to process a Victim Record (093) that contained all ‘N’s in the Ethnicity/Race Flag fields.
Solution:	Verify the correct Ethnicity/Race Flags, ‘Y’ or ‘N’. At least one of the 6 new ethnicity/race flag fields must contain a ‘Y’.

89G Invalid Parent Contacted Flag (Victim) Flag

Cause:	The Parent Contacted Flag (Victim) field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the parent was contacted regarding Event for the given record and send either a ‘Y’ or ‘N’.

89H Invalid Counseling Flag (Victim)

Cause:	The Counseling Flag (Victim) field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Victim was provided counseling by the LEA to cope with the Event for the given record and send either a ‘Y’ or ‘N’.

89I Invalid Other Support Flag

Cause:	The Other Support Flag field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Victim received some other measure of support from the LEA to cope with or address the Event for the given record and send either a ‘Y’ or ‘N’.

89J Invalid Injury Code

Cause:	An attempt was made to process a Victim Record (093) that contained an invalid value in the Injury Code field.
Solution:	Verify that the Injury Code is correct for this Victim. Injury Code must be a valid code.

89K Invalid Victim Medical Treatment Flag

Cause:	The Medical Treatment Flag (Victim) field in your submission file contains something other than a ‘Y’ or ‘N’ which is the only two valid options for this required field.
Solution:	Determine whether the Victim required off site medical treatment for the given record and send either a ‘Y’ or ‘N’.

89L Invalid Perpetrator Type for Event Upload

Cause:	An attempt was made to process a Student Perpetrator and Instance Record (091) through Event Upload section of SIS Web.
Solution:	Verify and re‐submit. Student Perpetrators may only be submitted through Student Upload section of SIS Web.

89M Invalid Perpetrator Type for Student Upload

Cause:	An attempt was made to process a Non‐Student Perpetrator and Instance Record (094) through Student Upload section of SIS Web ‐‐OR‐‐ The Student Perpetrator and Instance Record (091) have an invalid Perpetrator Type Code.
Solution:	Verify and re‐submit. Non‐ Student Perpetrators may only be submitted through Event Upload section of SIS Web. ‐‐OR‐‐ Correct the Perpetrator Type Code for the student.

89N Event ID Does Not Exist

Cause:	An attempt was made to process a Student Perpetrator and Instance Record (091) through Student Upload prior to uploading an Event record through the Event upload.
Solution:	For the same data collection period, an Event (007) record with the Event ID must be uploaded first before submitting student perpetrator records referencing that Event ID. Upload the Event Record (007). and then re‐submit the Student Perpetrator and Instance Records (091).

• The user will need to upload the Event file, using the Event tab, first. Then the user will need to upload the SIS file, using the SIS tab.

89O Start Date/Return Date and Admin Date Not Allowed

Cause:	An attempt was made to process an Action/Intervention Record (092), with a Discipline Start Date, Discipline Return Date and Discipline Administered Date for the supplied Action Intervention Code. Start Date/Return Date cannot be used in conjunction with Admin Date for supplied Action Code (This is for case where Date‐Duration is “Either”…but not both)
Solution:	Verify and re‐submit.

89P Start Date/Return Date or Agminate is Required

Cause:	An attempt was made to process an Action/Intervention Record (092), with no Discipline Start Date, Discipline Return Date or Discipline Administered Date for Action Intervention Code. Start Date/Return Date or Admin Date is required for supplied Action Code (case “Either”…but at least one field group has value(s).)
Solution:	Verify the correct Action/Intervention Code designation and add the Discipline Start Date/ Return Date or Admin Date and resubmit.

• In Discipline Posting, an Action Taken By School Administration was chosen but no information was chosen in the OSS field and pop up window fields.

89Q Discipline Start Date is required for Action Code

Cause:	An attempt was made to process an Action/Intervention Record (092), with no Discipline Start Date for the supplied Action Intervention Code. Discipline Start Date is required for the supplied Action Intervention Code.
Solution:	Verify the correct Action/Intervention Code designation or add the Discipline Start Date and resubmit.

89R Discipline Start Date is not allowed for Action Code

Cause:	An attempt was made to process an Action/Intervention Record (092), with a Discipline Start Date for the supplied Action Intervention Code. Discipline Start Date is not allowed for this Action Intervention Code.
Solution:	Verify and re‐submit.

89S Discipline Return Date is required for Action Code

Cause:	An attempt was made to process an Action/Intervention Record (092), with no Discipline Return Date for the supplied Action Intervention Code. Discipline Return Date is required for the supplied Action Intervention Code.
Solution:	Verify the correct Action/Intervention Code designation or add the Discipline Return Date and resubmit.

89T Discipline Return Date not allowed for Action Code

Cause:	An attempt was made to process an Action/Intervention Record (092), with a Discipline Return Date for the supplied Action Intervention Code. Discipline Return Date is not allowed for this Action Intervention Code.
Solution:	Verify and re‐submit.

89U Discipline Administered Dt is required for Action Cd

Cause:	An attempt was made to process an Action/Intervention Record (092), with no Discipline Administered Date for the supplied Action Intervention Code. Discipline Administered Date is required for the supplied Action Intervention Code.
Solution:	Verify the correct Action/Intervention Code designation or add the Discipline Administered Date and resubmit.

• In Discipline Posting on the Admin Page, the user must have dates in the Date column of each row of the Action Taken By School Administration. Click in the field and add a date.

89V Discipline Administered Dt not allowed for Action Cd

Cause:	An attempt was made to process an Action/Intervention Record (092), with a Discipline Administered Date for the supplied Action Intervention Code. Discipline Administered Date is not allowed for this Action Intervention Code.
Solution:	Verify and re‐submit.

89W Missing Action/Intervention Record for Perpetrator Record

Cause:	An attempt was made to process a Perpetrator and Instance Record without a corresponding Action/Intervention Record (092).
Solution:	Each Perpetrator and Instance record must have at least one associated Action/Intervention record. Confirm that at least one Action/Intervention record exists for each Perpetrator and Instance record.

89X Duplicate Action/Intervention Record not Allowed

Cause:	An attempt was made to process an Action/Intervention Record (092) that matches an existing Action/Intervention record for a specific student and event.
Solution:	Remove duplicate Action/Intervention records.

89Y Victim Record Type 093 Required

Cause:	An attempt was made to process an Event Record (007) with a Primary Reason Code of either 35 or 36 without a coinciding Victim Record.
Solution:	Verify Primary Reason Code and submit Victim Record. Victim Records are required for Primary Reason Codes of either 35[Bullying] or 36[Cyberbullying]

89Z Victim Record not Allowed

Cause:	An attempt was made to process an Event Record (007) with a Primary Reason Code that does not allow a Victim Record (093).
Solution:	Verify Primary Reason Code and remove Victim Record (093).

Top of Page

8A1-8A2

8A1 Alternate Site is Closed

Cause:	An attempt was made to process an Action/Intervention Record (092) that specified an Alternate Site that is closed in SPS.
Solution:	Verity Site Code in SPS. Correct and resubmit.

8A2 Alternate Site must have program code “03” in SPS

Cause:	An attempt was made to process an Action/Intervention Record (092) that specified an Alternate Site with a Program Code other than “03” (Alternative Program).
Solution:	Verify Program Code for the Alternate site in SPS. Correct and resubmit

• Note: SPS is Sponsor Site Editor. In the LEA State system, add an 03 to the alternate site.

Top of Page