SDEM0200

What this error actually means

CALPADS determined that at least one date associated with the submitted SDEM record falls outside the period during which the Reporting LEA was officially open. This may involve the record’s effective start date, an effective end date, or the staff member’s employment end date.

A reorganized LEA, obsolete CDS code, incorrect historical date, or source-system crosswalk can cause the mismatch. The correct Reporting LEA is the organization that actually employed and reported the staff member during the applicable period—not necessarily the organization that exists today.

Inclusive date-boundary tests

Fields and dates to review

• 7.04 — Effective Start Date
• 7.06 — Reporting LEA
• Effective End Date, when populated
• Staff Employment End Date, when populated
• Official Reporting LEA open and closed dates

Follow the value through the staff-data chain

Authoritative HR/personnel evidence → local HR or personnel system → SDEM export → CALPADS staging and ODS → SASS and CRSE relationships → Fall 2 reports

The date visible in the rejected CALPADS row may originate in an HR value, a local CDS crosswalk, an export transformation, a copied prior-year record, or the upload context.

Recommended correction path

1. 1

   Preserve the rejected transaction

   Record the submission ID, physical row number, SEID, Reporting LEA, Effective Start Date, Effective End Date, Employment End Date, and the exact SDEM values CALPADS evaluated.

2. 2

   Verify the official LEA operating period

   Resolve the submitted seven-digit Reporting LEA code to the correct organization and confirm its official open and closed dates. Account for reorganizations, mergers, charter changes, and successor LEAs.

3. 3

   Test every applicable date

   • Confirm the Effective Start Date falls within the LEA’s operating period.
   • If populated, confirm the Effective End Date falls within that period.
   • If populated, confirm the Staff Employment End Date also falls within that period.
   • Treat the LEA’s official open and closed dates as inclusive boundaries.
4. 4

   Verify the historical employing LEA

   Use employment records, contracts, payroll history, organizational records, and prior CALPADS submissions to determine which LEA actually employed and reported the staff member during the period. Do not substitute a successor LEA merely because the original LEA is now closed.

5. 5

   Distinguish record history from employment history

   If the staff member’s employment ended, correct the Employment End Date. Do not use the SDEM Effective End Date as a substitute for ending employment. Populate an Effective End Date only when the intended demographic-history workflow supports it.

6. 6

   Correct the authoritative source or mapping

   Correct the evidence-supported Reporting LEA or date in the HR/personnel system, local crosswalk, or export process. If the file was vendor-generated, repair the repeatable mapping rather than hand-editing only the rejected row.

7. 7

   Resubmit and reconcile downstream records

   Confirm that the SDEM transaction posts under the intended SEID and Reporting LEA. Review Staff Profile Report 4.4 and the applicable Fall 2 staff reports, then determine whether the same LEA or date mapping affected other SDEM records, SASS assignments, or CRSE sections.

Before closing the correction

• The Reporting LEA was officially open on every applicable submitted date.
• The Effective Start Date and any populated end dates are supported by authoritative records.
• The Record Effective End Date is not being used as an Employment End Date.
• The SDEM row posts successfully under the correct SEID and Reporting LEA.
• Related SASS, CRSE, and Fall 2 staff reports remain consistent.