Skip to main content
Skip table of contents

Discipline Data Entry

On this page:

This section of the documentation will review the correct data entry methods for Discipline Incidents that need to be reported in the Discipline Domain or the Location Fact template.

If a Discipline Incident is a Safe Schools incident, it will be reported in the PIMS Discipline Domain templates. Incidents that violate your District's Academic Code or Code of Conduct and result in Suspension or Expulsion and Truancy incidents will be reported in the Location Fact template. Incidents will only be reported in one area, not both. 

Discipline Incident Reporting Overview

The Incident state equiv code is found in the Incident/Offense Codes (Discipline) validation table. The Action state equiv code is found in the Offense Actions (Discipline) validation table.

Any single discipline incident will only fall into one of these 3 categories for a PIMS Submission:

Discipline/Safe School Incidents

PIMS Download > Discipline (DSC) incidents, a.k.a. "Safe School" incidents 

  • These are incidents where the Incident state equiv code = 01-52.
  • Safe School incidents must also have an Offense Action code with a state code equiv beginning with the letter S.

One record will be created per incident in the table PA_INCIDENT_DOWN. Additional, corresponding PIMS Discipline tables may also be populated. 

If there are no PIMS Discipline incidents for the building and date range with a state code equiv of 01-52, then there will be no PA_INCIDENT_DOWN records. Instead, a Location Fact "zero" record for category=INCIDENTS will be created for that building in the table PA_LOC_FACT_DOWN.

Location Fact (LF) Incidents

PIMS Download > Location Fact (LF) incidents. These are incidents where either:

  • The Incident/Offense state equiv code = TRUANT
  • The Incident/Offense state equiv code = A or C  and the Action state equiv code = S4-S7.

The incidents are tallied into three categories: TRUANCY, SUSPENSION, and EXPULSION (2.A, 2.B, and 2.C below). At least one record for each of these categories should always be created for the building in the Location Fact table PA_LOC_FACT_DOWN.   In other words, the building should always have 3 PA_LOC_FACT_DOWN records per submission. Each record will either contain Counts > 0 if there are incidents that meet the criteria, or Counts = 0 (a.k.a. a "zero" record) if there are no incidents that meet the criteria.

  • TRUANCY: This record gives a count of how many incidents have Incident/Offense state equiv code = TRUANT for the building and date range. If there are none, then a "zero" record should be built with Counts = 0. (In the Incident Codes table, there must be at least one action with state equiv = TRUANT in order for the "zero" record to be created.)
  • SUSPENSION: This record gives a count of how many incidents have Incident state equiv code = A or C  and Action state equiv code = S4 for the building and date range. If there are none, then a "zero" record should be built with Counts = 0.
  • EXPULSION: This record gives a count of how many incidents have Incident state equiv code = A or C  and Action state equiv code = S5-S7 for the building and date range. If there are none, then a "zero" record should be built with Counts = 0.
  • INCIDENTS: This record will only be created if there are no PIMS Discipline incidents for the building and date range (meaning there are no incidents in PA_INCIDENT_DOWN). If there are any PIMS Discipline records for the building and date range (meaning if there are any incidents in PA_INCIDENT_DOWN), then the Location Facts "INCIDENTS" record will not be created.

Incidents not included in the PIMS Download  

These are incidents:

  • Without state equiv codes
  • With state equiv codes = A or C, but without Offense Action state equiv codes of S4-S7.

These incidents do not influence either the Discipline (DSC) or Location Fact (LF) records and not counted for PIMS.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.