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

7.01 Record Type Code 7.02 Transaction Type Code 7.03 Local Record ID 7.04 Effective Start Date 7.05 Effective End Date 7.06 Reporting LEA 7.07 Academic Year ID 7.08 SEID 7.09 Local Staff ID 7.10 Staff Legal First Name 7.11 Staff Legal Middle Name 7.12 Staff Legal Last Name 7.13 Staff Alias First Name 7.14 Staff Alias Middle Name 7.15 Staff Alias Last Name 7.16 Staff Birth Date 7.17 Staff Gender Code 7.18 Staff Hispanic Ethnicity Indicator 7.19 Staff Ethnicity Missing Indicator 7.20 Staff Race 1 Code 7.21 Staff Race 2 Code 7.22 Staff Race 3 Code 7.23 Staff Race 4 Code 7.24 Staff Race 5 Code 7.25 Staff Race Missing Indicator 7.26 Staff Highest Degree Code 7.27 Staff Employment Status Code 7.28 Staff Employment Start Date 7.29 Staff Employment End Date 7.30 Staff Service Years LEA 7.31 Staff Service Years Total

Recommended correction path

Suggested resolution

What this error actually means

This differs from GERR0002: the code is recognized, but its valid-from/valid-through window does not include the record’s effective date.

Valid versus invalid

ExampleSubmitted value or conditionInterpretation
ValidCurrent code + date inside its effective windowThe code and event date agree.
InvalidRetired code + later effective dateUse the supported successor only if it describes the staff fact.
InvalidFuture code + earlier effective dateDo not apply a code before its official start.
Possible date defectCorrect code + incorrect Effective Start DateCorrect the date rather than replacing the code.

Fields validated

  • The SDEM code field identified in submission detail plus 7.04 Effective Start Date

Recommended correction path

  1. 1

    Open the rejected submission detail

    Locate the exact physical row, field number, submitted value, Reporting LEA, SEID, Academic Year, and effective dates.

  2. 2

    Read the raw exported value

    Do not rely only on the formatted HR or SIS screen. Inspect spaces, delimiters, zero padding, dates, and local code translations.

  3. 3

    Test this rule

    • Identify the code field and exact effective date used by the rule.
    • Review the code’s start and end dates in the current code set.
    • Determine whether the code or the SDEM effective date is wrong.
    • Check vendor crosswalks for retired local mappings.
  4. 4

    Confirm correction authority

    HR/personnel staff own authoritative employment and demographic facts; technical staff own mappings and export behavior; the CALPADS operator verifies the submitted representation. Protect confidential personnel data throughout the review.

  5. 5

    Correct the responsible source

    Correct whichever value is unsupported—the code, the effective date, or both—while preserving the actual historical event.

  6. 6

    Resubmit and reconcile downstream records

    Confirm the row posts under the intended SEID and Reporting LEA. Review Staff Profile Report 4.4 and relevant Reports 4.1–4.5; then check whether the same mapping affected other staff, SASS assignments, or CRSE sections.

Official GERR0007 guidance · CALPADS Staff Demographics guidance · Fall 2 Reporting Roadmap · Report 4.4 Staff Profile List · Current CALPADS specifications and code sets