Incident Offender Infraction Template
PIMS Incident Offender Infraction Template Specifications
INCIDENT_OFFNDR_INFRACTION
Note
- All discipline incidents resulting in disciplinary action codes
S3
-S9
must be submitted in the Discipline Domain PIMS submission, regardless of the special education status of the student. - If an infraction resulting in a suspension or expulsion does not align to one of the 46 numeric safe schools' infraction codes (ending with infraction code 54), it shall be aligned to either an A - Academic Code of Conduct or a C - Student Code of Conduct discipline infraction type.
Template Description
This template connects an incident and the offender to an infraction. If multiple infractions apply to the incident/offender submit multiple records; use one record per infraction.
Template Specifications
1 - SUBMITTING AUN
The unique, 9-digit AUN assigned by the PDE.
Sample Value
123456789
2 - INCIDENT ID
An identifier assigned by the LEA to the incident; this identifier must be unique within each LEA per school year.
Sample Value
9801
3 - OFFENDER ID
An identifier for the offender involved in an incident. Must be the same value used in Field 2 (PERSON ID) within the Person Template.
Sample Value
887
4 - INFRACTION CODE
The code of the infraction for the offender.
See Appendix Z in Volume 2 of the PIMS User Manual for a complete list of valid values.
5 - SCHOOL YEAR DATE
A single date (June 30), the last day of the current school year indicating the whole school year.
Sample Value
2026-06-30
6 🛇
Field not collected. Must be delimited in template file.
7 - INFRACTION COMMENT
A comment regarding the nature of the infraction.
Business Rules
Required if INFRACTION CODE = 16.
Rules
See the Rules Section of the Template Domain for rules consistent throughout all templates.