Skip to main content

CALPADS error brief · GERR

GERR0005

LEA does not have ownership of student to make the Special Education Services (SERV Record) update
Severity
FATAL error — Must be corrected to post the record or certify the data.
Error type SERV — Student Services
Record type GERR

Official CALPADS rule

What CALPADS is rejecting

The Reporting LEA does not own the SERV record.

Focus fields

Fields validated

SSRV Data 25.04 - Reporting LEA 25.07 - SSID 25.16 - Plan Effective Start Date SENR Data 1.04 - Reporting LEA 1.22 - Enrollment Start Date 1.23 - Enrollment Status Code 1.25 - Enrollment Exit Date

Recommended correction path

Suggested resolution

Current fields and records involved

  • SERV 25.04 Reporting LEA
  • SERV 25.07 SSID
  • SERV 25.17 Plan Effective Start Date
  • SENR 1.04 Reporting LEA
  • SENR 1.22 Enrollment Start Date
  • SENR 1.23 Enrollment Status Code
  • SENR 1.25 Enrollment Exit Date

The official page still says “SSRV Data” and displays pre-Version 18 SERV field numbers. Use the current SERV numbers above.

The dependency path

1. SENR ownershipCorrect SSID, Reporting LEA, status, and enrollment dates post first
2. PLAN eventThe responsible LEA/SELPA establishes the operative plan date
3. SERV recordThe service attaches to that student and Plan Effective Start Date
4. ODS verificationEnrollment, plan, and service histories tell one story

Does the SENR enrollment contain the plan date?

For a qualifying enrollment, the ordinary test is:

Enrollment Start Date ≤ Plan Effective Start Date ≤ Enrollment Exit Date
If Enrollment Exit Date is blank, the enrollment remains open.

SituationOwnership resultWhat to verify
Plan date falls inside an enrollmentOrdinarily supportedSSID and Reporting LEA must also agree.
Plan date precedes Start Date or follows Exit DateNot supportedDetermine whether SENR dates, plan date, or LEA is wrong.
Status 20 SecondaryDoes not establish the ownership required by this ruleDo not convert the status merely to pass validation; identify the actual responsible enrollment.
Plan date is in June, July, or AugustSummer exception may applyConfirm the authentic plan date and responsibility; the exception is not permission to invent enrollment.

What commonly causes GERR0005

  • The SENR row rejected, was never posted, or was exited too early.
  • The SERV row contains the wrong SSID or Reporting LEA.
  • The Plan Effective Start Date belongs to a different plan or was mistyped.
  • A transfer occurred, but PLAN and SERV ownership were not aligned to the responsible LEA/SELPA.
  • The upload relies only on a secondary enrollment.
  • A summer plan was treated either as automatically invalid or automatically exempt without verifying the actual circumstances.

Do not add a fictitious SENR record to manufacture ownership. Correct the first inaccurate link: student identity, enrollment history, responsible organization, PLAN event, or SERV date.

Recommended correction path

  1. 1

    Preserve the rejected SERV row

    Capture the submission, SSID, Reporting LEA, Plan Effective Start Date, and untouched source values.

  2. 2

    Open the student’s CALPADS enrollment history

    Find every SENR segment for the Reporting LEA, including open, exited, secondary, and summer-adjacent records.

  3. 3

    Test the date relationship

    Determine whether the plan date falls within a qualifying enrollment or the documented summer exception.

  4. 4

    Verify the authoritative PLAN

    Confirm student, effective date, Reporting LEA, Reporting SELPA, and the underlying IEP, IFSP, or ISP event.

  5. 5

    Correct the owning record first

    Post a legitimate missing SENR record, correct inaccurate enrollment history, repair the PLAN relationship, or correct SERV—whichever evidence proves wrong.

  6. 6

    Resubmit in dependency order

    Confirm SENR and PLAN are accepted before resending SERV, then verify the resulting ODS histories.

Official SERV GERR0005 page · Current SERV details