CALPADS error brief · SELA

SELA0326

ELAS Start Date already exists for Student

Severity Fatal

Error type Input Validation

Record type SELA

Official CALPADS rule

What CALPADS is rejecting

A student must not have more than one SELA record with the same ELAS Start Date

Focus fields

12.04 Reporting LEA 12.07 SSID 12.13 English Language Acquisition Status Code 12.14 English Language Acquisition Status Start Date

Recommended correction path

CALPADS SELA correction guide

A student may not have more than one SELA record with the same ELAS start date. The duplicate may be inside the upload or already stored in the ODS.

Focus fields: Reporting LEA (12.04), SSID (12.07), ELAS Code (12.13), and ELAS Start Date (12.14)

1
Search both possible duplicate locations
Check the current submission for repeated SSID/date rows, then inspect the student’s existing SELA history in CALPADS.
2
Compare more than the date
Review the status code, reporting LEA, and supporting event. Two different statuses on one date usually indicate a source-system or correction-workflow problem.
3
Preserve the authoritative record
If CALPADS already contains the correct event, remove the redundant transaction and align the SIS with the ODS. Do not delete good history merely to accept a new row.
4
Resolve conflicting records carefully
Use the actual HLS, assessment, or reclassification evidence to determine the correct status. Coordinate with the owning LEA or CALPADS Support when necessary.
5
Deduplicate the pipeline
Correct the export query or integration that generated repeated rows, resubmit, and verify one—and only one—ELAS event for that date.

Save the rejected-record details and the evidence used for the correction.
Confirm the fix in CALPADS—not only in the SIS export preview.
When ELPAC eligibility is affected, coordinate directly with the LEA ELPAC coordinator and verify TOMS after the normal data exchange.