Skip to main content

CALPADS error brief · SDEM

SDEM0218

All associated Staff Assignment and/or Course Section records must be deleted before deleting the last remaining Staff Demographic record for SEID xxxxxxxxxx" (x’s represent the SEID number)
Severity Fatal
Error type Data Discrepancy
Record type SDEM

Official CALPADS rule

What CALPADS is rejecting

All associated Staff Assignment and Course Section records must be deleted before deleting the last remaining Staff Demographic record

Focus fields

Fields validated

7.06 Reporting LEA 7.08 SEID Related SASS Staff Assignment and CRSE Course Section records

Recommended correction path

Suggested resolution

What this error actually means

SDEM is the staff identity foundation. Removing its last record would leave assignments or course sections pointing to an educator with no demographic history.

Valid, invalid, and unsafe responses

SituationValue or conditionInterpretation
Keep SDEMSASS/CRSE are valid and still belong to this educatorCancel the deletion or replace/correct SDEM history.
Delete dependencies firstSASS/CRSE are proven erroneous or must be removedDelete in dependency order, then delete final SDEM if supported.
Wrong SEIDAssignments belong to another educatorCorrect dependent records carefully before touching SDEM.
Unsafe shortcutDelete valid assignments merely to clear SDEM0218Preserve Fall 2 instructional history.

Dependency-aware correction order

SDEM identity → SASS assignment → CRSE course-section staffing → Fall 2 certification

For creation, establish the correct SDEM identity before downstream records. For a supported final deletion, unwind dependent CRSE/SASS relationships before removing the final SDEM record.

Fields and records evaluated

  • 7.06 Reporting LEA
  • 7.08 SEID
  • Associated SASS staff-assignment records
  • Associated CRSE course-section staffing records

Recommended correction path

  1. 1

    Preserve the rejected evidence

    Capture the submission, row, field values, Reporting LEA, masked SEID, effective dates, and related SASS/CRSE identifiers before editing.

  2. 2

    Confirm the person and business key

    Use authorized evidence to match the educator, Reporting LEA, SEID, and effective period. Do not include SSNs in ordinary working notes.

  3. 3

    Test the exact rule

    • List every SASS and CRSE record associated with the Reporting LEA and SEID.
    • Determine why the final SDEM deletion was requested.
    • Verify whether dependencies are valid, obsolete, duplicated, or assigned to the wrong SEID.
    • Preserve evidence and coordinate HR, CALPADS, credential, scheduling, and course staff.
  4. 4

    Find the first divergence

    Determine whether the problem began in authorized personnel evidence, HR/SIS entry, a local crosswalk, an integration, file generation, or CALPADS history.

  5. 5

    Make the supported correction

    If the SDEM record should remain, withdraw the deletion and correct/replace its history. If the identity truly must be removed, correct or delete only the unsupported CRSE and SASS dependencies first, then process the final SDEM deletion.

  6. 6

    Regenerate and reconcile

    Confirm the accepted SDEM history under the intended Reporting LEA and SEID. Review Report 4.4 and applicable Reports 4.1–4.5, then inspect other staff affected by the same mapping or workflow.

Official SDEM0218 guidance · CALPADS Staff Demographics guidance · Report 4.4 Staff Profile List · Current specifications and code sets