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

20.01 Record Type Code 20.02 Transaction Type Code 20.12 Student Gender Code 20.14 Student Offense Code 20.15 Weapon Category Code

Recommended correction path

Suggested resolution

CALPADS SOFF 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.

Official CALPADS rule

Severity: Fatal   Type: Input Validation

Fields validated:

  • 20.01 Record Type Code
  • 20.02 Transaction Type Code
  • 20.12 Student Gender Code
  • 20.14 Student Offense Code
  • 20.15 Weapon Category Code

Recommended correction path

  1. 1

    Re-read the incident evidence

    Review the contemporaneous incident record, investigation findings, applicable Education Code basis, and the local offense selected. Do not infer a weapon type from a broad narrative alone.

  2. 2

    Validate both complete fields

    Compare 20.14 Student Offense Code and 20.15 Weapon Category Code with current CALPADS code sets, effective dates, and valid-code combinations.

  3. 3

    Check the local translation

    Inspect the SIS discipline-offense and weapon mappings. Confirm that a precise local value is translated to the intended state code and that required weapon detail is not dropped.

  4. 4

    Resolve with the responsible team

    Include the site administrator or discipline designee, CALPADS coordinator, SIS owner, and legal or student-services staff when the statutory classification itself is uncertain.

  5. 5

    Correct, post, and scan for pattern

    Update the authoritative record or mapping, regenerate SOFF, reconcile SINC/SIRS, and identify other incidents using the same local code combination.

Where this correction sits in the 2026–27 calendar

Capture throughout the yearKeep incident IDs, offenses, results, statutory-offense decisions, weapon details, and special-education safeguards aligned while evidence is fresh.
EOY 1 submission window opens; Student Incidents are part of the consolidated EOY 1 collection.
CDE’s recommended date for reaching zero EOY 1 errors.
EOY 1 amendment window closes; required SELPA approval must be complete.

Dates are from the current CDE CALPADS 2026–27 calendar. Verify the official calendar before acting because dates can change.

Before closing the ticket

  • Confirm the corrected SOFF record under the intended student and Incident ID Local in CALPADS.
  • Reconcile the related SINC parent and every applicable SIRS/SOFF child record.
  • Document whether the defect arose in source evidence, coding, translation, enrollment, configuration, or extract logic.
  • Check other incidents affected by the same local rule before EOY 1 certification.

Official references and practical support

SIS, discipline, and extract support

Begin with your vendor’s current California/CALPADS documentation. Incident models, local offense codes, weapon mappings, and SINC/SIRS/SOFF extract paths vary by product and configuration. Inclusion is not an endorsement; some resources require customer access.