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 submitted outside the effective date range

Focus fields

Fields validated

All SENR fields in the CALPADS Code Sets document

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: Code submitted outside the effective date range

Severity: Fatal   Type: Input Validation

Fields validated: All SENR fields identified in the CALPADS Code Sets document.

Diagnose the right kind of code problem

Why the error number changes the investigation
FindingWhat it usually meansBest first move
Value is absent from the field’s code setThe value may be a local label, misspelling, wrong field’s code, or damaged export value.Treat it as a reference-set or alignment problem, commonly associated with GERR0002.
Value exists, but its end date has passedThe code is retired for the date CALPADS is evaluating.Research the code’s definition and effective window, then establish the accurate current circumstance.
Value was valid on the historical event dateThe record may represent legitimate history, but the transaction, correction method, or controlling date needs review.Do not modernize the history automatically; verify the accepted historical-correction procedure.
Many records fail on the same codeAn outdated SIS crosswalk, report constant, or vendor release is likely still producing the retired value.Correct the shared mapping and regenerate the population.

Real retired SENR-related examples from Code Sets Version 18

These examples show how a value can be genuine CALPADS history and still be unusable for a later date. They are diagnostic examples—not a replacement-code table.

Examples and published effective windows
Code set and valuePublished meaningEffective windowWhat the date tells you
Enrollment Status 40Receiving specialized services onlyJuly 1, 1990–June 30, 2019A current extract must not keep producing this old enrollment-status mapping.
Grade Level TDToddlersJuly 1, 1990–June 30, 2023Confirm the student’s actual program and the current grade-level reporting rule.
Grade Level UE / USUngraded Elementary / Ungraded SecondaryJuly 1, 1990–June 30, 2018Do not preserve an obsolete “ungraded” crosswalk solely because the SIS still displays it.
Completion Status 104Completed requirements, failed CAHSEEJuly 1, 1990–August 15, 2014The definition belongs to an earlier CAHSEE-era reporting context.
Completion Status 106 / 108CAHSEE modification/waiver or exemption pathwaysEnded August 15, 2015Verify the historical completion record and applicable correction procedure before changing it.
Exit Reason T167Transfer to alternative school/programJuly 1, 2010–June 30, 2026This recently retired code may remain in a vendor crosswalk after the 2026 transition.
Exit Reason T168Alternative/independent-study school dischargeJuly 1, 2021–June 30, 2026Investigate the actual exit and the Version 18 rule now governing that circumstance.
Birth Country ANNetherlands AntillesJuly 1, 1990–December 15, 2010Confirm the documented birthplace and the current geopolitical code; do not guess from the old label.

Retired does not mean “historically false.” A code may accurately describe an older event even though it cannot be submitted for a later effective period. Preserve the original evidence and determine which date CALPADS is validating before changing a historical enrollment, exit, or completion record.

Find the date mismatch—not merely the old code

Common paths to GERR0007
Failure patternWhat it looks likeDurable correction
Retired crosswalk remains activeThe SIS still maps a local selection to a code whose end date has passed.Replace the mapping prospectively after confirming the current official definition and local circumstance.
Vendor release is behind the code-set versionMany LEAs or records begin failing after a new CALPADS year or code-set release.Confirm the vendor’s Version 18 readiness, release notes, configuration, and effective date.
Old template or spreadsheet reusedA manually maintained lookup table continues supplying a retired value.Retire the local template, update the controlled crosswalk, and test other records produced from it.
Incorrect event dateThe code and event might each be reasonable, but the SENR date places the code outside its window.Verify the enrollment, exit, or completion date from authoritative records; never move a date simply to make the code pass.
Historical correction submitted as currentA correction to old history is processed with a date or transaction approach that invokes current rules.Confirm the CALPADS historical-maintenance method and preserve the event’s true chronology.
Nearest current code substitutedThe error disappears, but the new value does not match the student’s actual event.Return to the published definitions and evidence; passing validation is not proof of factual accuracy.

Resolve the code through time and meaning

1. Rejected valueCapture the exact field, code, row, and submission.
2. Published windowFind the code’s start date, end date, and definition.
3. Governing eventVerify the real enrollment, exit, completion, or demographic fact and date.
4. Current productionRepair the source, crosswalk, report, or vendor configuration.

Choose the diagnostic pathway

  • Exact field, code, and effective window
    • Which SENR field and literal value does the error identify?
    • Which code set is assigned to that field?
    • What start and end dates appear for that exact value?
    • Which record date or reporting condition is CALPADS evaluating?
  • Historical record or current transaction
    • Did the real event occur while the code was active?
    • Is this a correction to historical data or a newly occurring event?
    • Does the submitted date match the cumulative file, enrollment record, transcript, or exit evidence?
    • What official maintenance procedure applies to the historical correction?
  • Recently retired code
    • Did the error begin after July 1 or a code-set update?
    • Does the Version 18 Explorer show the code as retired?
    • Did CDE revise, consolidate, or replace the underlying reporting concept?
    • Has the local crosswalk been reviewed by the program and data owners?
  • Exit and completion meaning
    • What actually happened to the student, and on what date?
    • What documentation supports the exit or completion outcome?
    • Does another enrollment or completion record alter the interpretation?
    • Does the current code’s complete definition—not just its label—fit the event?
  • Crosswalk, extract, and vendor
    • Which local value produced the retired code?
    • Where is that translation maintained?
    • Which CALPADS code-set version does the configuration implement?
    • How many other students, schools, years, and file types use the same mapping?
    • Will the next scheduled extract reproduce the error?

Primary participants for this error

  • CALPADS coordinator
  • Registrar or enrollment staff
  • Counselor, graduation, or cohort staff when applicable
  • SIS system owner
  • Extract, integration, or vendor support

Choose the owner from the pattern

  • One student: verify the event, date, and evidence.
  • One retired code: inspect its local crosswalk.
  • Many records after July 1: inspect annual code-set updates.
  • Historical correction: involve the CALPADS coordinator before rewriting history.

Recommended correction path

  1. Preserve the rejected row and error details

    Capture the submission ID, row number, exact field, rejected code, relevant dates, export time, and untouched source file.

  2. Confirm the row is structurally aligned

    Verify all 35 SENR positions remain intact so that the retired code truly belongs to the field CALPADS identified.

  3. Find the exact code in the SDLA Explorer

    Select the affected code set, include retired values, and record the value’s definition, status, start date, and end date.

  4. Identify the date CALPADS is evaluating

    Determine the enrollment, exit, completion, demographic, or other record date governing the field; do not assume the upload date is the only relevant date.

  5. Establish the real student circumstance

    Use authorized records to confirm what occurred and when. Preserve historically accurate facts even when reporting rules have changed.

  6. Determine the supported correction

    Apply the current code whose full definition matches the event, or follow the official historical-maintenance method. Never select a code solely because it clears the error.

  7. Repair the repeatable source

    Update the SIS value, controlled crosswalk, report, integration, spreadsheet, or vendor configuration responsible for producing the retired code.

  8. Regenerate, submit, and regression-test

    Confirm GERR0007 clears, then review the affected population and connected chronology, valid-combination, exit, completion, cohort, and enrollment rules.

Official CALPADS guidance

Understanding the error: Values submitted in a field must be effective in CALPADS. The submitted file contains values that are no longer accepted.

Things to check for in submission: Determine whether the code value is retired.

Operational expansion: Review the applicable CALPADS code set and its effective dates. If an SIS or integration produced the code, identify the responsible mapping and consult the vendor or technical owner as needed.

Before closing the issue

  • Confirm GERR0007 no longer appears for the intended student and enrollment.
  • Verify the submitted value is effective for the date and circumstance CALPADS evaluates.
  • Confirm authorized evidence supports both the code meaning and the event date.
  • Review connected chronology, valid-combination, exit, completion, cohort, and enrollment rules.
  • Test other records produced by the same retired mapping.
  • Document the old code, effective window, evidence, approved correction, owner, affected population, and regression test.

Explore current and retired CALPADS Version 18 codes with SDLA  |  Official GERR0007 troubleshooting page  |  Official CALPADS system documents

What SENR does—and does not do

SENR answers enrollment and SSID-context questions such as:

  • Does this student have an SSID?
  • Which LEA and school own this enrollment record?
  • When did the enrollment begin?
  • Is the enrollment primary, secondary, short-term, or non-ADA?
  • What grade level applies?
  • If the enrollment ended, when and why?
  • Did the student complete school?
  • Was an authorized transfer category involved?

Review official CALPADS SENR guidance

SENR participant directory

Engage only the roles needed for the specific field, event, effective-date conflict, or mapping defect.

  • CALPADS coordinator
  • Registrar or enrollment staff
  • School-site office staff
  • Attendance staff
  • Counselor or student-records staff
  • Graduation or cohort-data staff
  • District student-services administrator
  • Special education data staff
  • SIS system owner
  • Extract, integration, or vendor support