Skip to main content

CALPADS error brief · GERR

GERR0007

Code submitted outside the Effective Date Range
Severity Fatal
Error type Input Validation
Record type GERR

Official CALPADS rule

What CALPADS is rejecting

Code must be submitted with an Academic Year ID that overlaps, on at least one day, the CALPADS effective date range for the code.

Focus fields

Fields validated

19.01 Record Type Code 19.02 Transaction Type Code 19.06 Academic Year ID 19.12 Student Gender Code 19.14 Incident Result Code 19.15 Incident Result Authority Code 19.17 Incident Result Modification Code

Recommended correction path

Suggested resolution

CALPADS SIRS correction guide · Fatal input validation

GERR0007: Code submitted outside the Effective Date Range

Code must be submitted with an Academic Year ID that overlaps, on at least one day, the CALPADS effective date range for the code.

Rule and fields to check

Severity: Fatal   Type: Input Validation

  • 19.01 Record Type Code
  • 19.02 Transaction Type Code
  • 19.06 Academic Year ID
  • 19.12 Student Gender Code
  • 19.14 Incident Result Code
  • 19.15 Incident Result Authority Code
  • 19.17 Incident Result Modification Code

Basic resolution

  1. 1

    Confirm the intended record

    Match the student, school, academic year, Incident ID Local, and Reporting LEA to the source discipline record.

  2. 2

    Check the failed rule

    Compare every validated field below with the current file specifications, code sets, enrollment history, and organization relationships.

  3. 3

    Correct the source dependency

    Repair the authoritative SIS value, enrollment record, organization setting, code mapping, or duplicate—not merely the rejected upload row.

  4. 4

    Resubmit and verify

    Upload a scoped correction and confirm that the intended SIRS record appears once under the correct student and incident.

Before closing the correction

  • Confirm the accepted SIRS record under the intended student and Incident ID Local.
  • Reconcile the related SINC parent and any applicable SOFF records.
  • Check whether the same source value or mapping affected other incidents.

Official references