Skip to main content

CALPADS error brief · SENR

SENR0032

Missing SSID Enrollment Record Operational Key
Severity Fatal
Error type Input Validation
Record type SENR

Official CALPADS rule

What CALPADS is rejecting

If Transaction Type Code = D or Transaction Type Code = R Then SSID must be populated

Focus fields

Fields validated

1.02 - Transaction Type Code 1.08 - SSID

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: If Transaction Type Code equals D or R, SSID must be populated.

Severity: Fatal   Type: Input Validation

Fields validated:

  • 1.02 Transaction Type Code
  • 1.08 SSID

This is not permission to insert any SSID. First identify the exact enrollment already in CALPADS using the student, School of Attendance, SSID, and Enrollment Start Date. Then reproduce that verified operational key in the delete or replace row.

The three-field SENR operational key

CALPADS uses all three values to locate the SSID Enrollment record
Operational-key fieldWhat must matchCommon mistake
1.05 School of AttendanceThe school on the existing CALPADS enrollment being modified.Using the student’s current school when correcting a prior-school segment.
1.08 SSIDThe verified 10-digit CALPADS identifier belonging to the intended student.Leaving it blank, losing a leading/format-preserving value in a spreadsheet, or copying another student’s SSID.
1.22 Enrollment Start DateThe Start Date on the existing enrollment record.Putting the desired corrected Start Date in a delete row instead of the old key value CALPADS must locate.

Think of the key as an address: School tells CALPADS where to look, SSID identifies whose enrollment it is, and Start Date identifies which enrollment segment. A missing or altered component points to a different record—or no record at all.

Choose the transaction intentionally

Version 18 transaction behavior for SENR
TransactionWhat CALPADS doesSSID implication
Blank, space, or A Add/UpdateUses the operational key to insert a new record or update non-key fields on a matching record.SSID is part of the key even though SENR0032 specifically fires on D/R.
D DeleteUses the submitted operational key to locate and delete the matching ODS enrollment.The row must contain the verified SSID and the existing key values.
R ReplaceReplaces matching current-academic-year SENR records identified through the operational key; it may insert when no matching record exists.The SSID is essential to identifying which student’s record set is being replaced.

CALPADS permits different transaction types in one file, but the Version 18 specifications do not recommend mixing more than one transaction type per submission because posting order and validation behavior can be difficult to interpret. Separate, controlled files make review and rollback clearer.

Operational examples

Identify the intended result before editing the transaction row
SituationCorrect constructionUnsafe shortcut
Delete a duplicate enrollmentUse D with the exact existing school, verified SSID, and Start Date of the duplicate after confirming it is unsupported.Delete the row that merely “looks duplicated” without comparing ODS history.
Correct Exit Date or Exit ReasonUse Add/Update with the unchanged operational key and corrected non-key fields, following the applicable transaction workflow.Delete and recreate the enrollment when only a non-key value needs correction.
Correct Enrollment Start DateDelete the old-key record, then add the complete record with the supported new Start Date.Put the new date into the delete row; CALPADS will not locate the old record.
Replace current-year enrollment setUse R only after constructing and reviewing the complete intended set with the verified SSID.Assume Replace changes a single visible cell without affecting the matching record set.
SSID is unknownResolve student identity through authorized CALPADS/SSID procedures before submitting D or R.Guess, pad, fabricate, or copy an SSID from another record.
SSID exists in SIS but is blank in fileRepair the extract mapping, datatype, formatting, or column alignment and regenerate the row.Hand-edit only the rejected file while leaving the recurring defect.

What commonly produces SENR0032

Symptoms, likely causes, and durable corrections
What you findLikely causeDurable correction
SSID blank in SIS transaction screenThe delete/replace workflow did not inherit student identity.Correct the transaction-generation workflow and require an SSID before export.
SSID exists in SIS; blank in exported rowReport mapping, query join, filter, or datatype conversion failed.Repair the extract and test all D/R rows.
Values shifted one columnA missing delimiter or malformed earlier field displaced SSID.Repair file construction and validate column count/positions before upload.
Spreadsheet shows scientific notation or shortened digitsSSID was treated as a numeric display value rather than a fixed identifier.Preserve SSID as a 10-character string through export and QA.
Delete row was built from a blank templateStaff entered only the fields they wanted removed rather than the existing operational key.Generate corrections from the verified ODS/SIS enrollment record.
Replace file contains students not found in source joinAn outer/failed join produced transaction rows without identity values.Reject orphan rows during file generation and repair the join keys.
Manual file edit clears the error onceThe SIS/export remains defective.Correct the authoritative system and regenerate a reproducible submission.

Preflight every delete or replace file

A five-minute preflight can prevent a destructive mistake
CheckPass conditionStop condition
Transaction scopeEvery row is intentionally D or R and belongs in this controlled batch.Unexpected Add/Update rows or mixed transaction types appear.
SSID completenessEvery affected row contains a verified 10-digit SSID belonging to the intended student.Blank, malformed, duplicated-across-students, or unverified values appear.
Operational-key matchSchool, SSID, and existing Start Date match the targeted ODS record.The delete/replace key does not exist or points to another segment.
Expected resultA before/after list identifies exactly what will remain after processing.The team cannot explain the intended ODS history for each student.
Recovery evidenceUntouched source rows, ODS history, submission file, owner, and correction plan are preserved.No reliable way exists to reconstruct a mistakenly removed enrollment.

Choose the diagnostic pathway

  • Confirm the intended transaction
    • Should this row add/update, delete, or replace?
    • What exact ODS record or set should change?
    • Is the transaction necessary, or can a non-key field be updated?
    • Does the requested action belong to the current academic year when Replace is used?
    • Has a reviewer approved the destructive scope?
  • Verify student identity and SSID
    • Does the SSID belong to the intended student?
    • Is it exactly 10 digits with a valid CALPADS format/check digit?
    • Does the local student record link to the current SSID?
    • Could a merge, replacement, duplicate SSID, or wrong-student link be involved?
    • Never construct an SSID from memory.
  • Match the operational key
    • What School of Attendance is on the existing ODS record?
    • What SSID is on that record?
    • What is its existing Enrollment Start Date?
    • Do all three values match the submitted delete/replace row?
    • If Start Date is changing, did you retain the old value in the delete row?
  • Inspect file construction
    • Is SSID in field 1.08 rather than shifted by a delimiter error?
    • Did a spreadsheet or export convert, truncate, or blank the identifier?
    • Did a database join fail to return the SSID?
    • Are all D/R rows complete?
    • Will regeneration reproduce the corrected value?
  • Verify post-processing history
    • Did the intended enrollment disappear, update, or become the correct replacement set?
    • Were unrelated enrollment segments preserved?
    • Did a Start Date correction create a gap, duplicate, or overlap?
    • Do SINF, SPRG, SELA, attendance, assessment, cohort, and special-education dependencies remain coherent?

Build a controlled transaction

  1. TargetIdentify ODS record.
  2. IdentityVerify SSID.
  3. KeyMatch all three fields.
  4. TransactionSubmit controlled action.
  5. PostflightVerify exact history.

Primary participants

  • CALPADS coordinator
  • Registrar or enrollment staff
  • Student records/SSID staff
  • SIS system owner
  • Extract or integration developer
  • Vendor support when needed

Evidence to preserve

  • Untouched rejected row and submission ID
  • Existing ODS enrollment history
  • Verified student/SSID evidence
  • Before-and-after operational keys
  • Approved transaction scope
  • Accepted postflight history

Recommended correction path

  1. Stop the destructive batch

    Do not upload or rerun related delete/replace rows until scope, identity, and key completeness are verified.

  2. Preserve the rejected row

    Capture submission ID, Transaction Type, School, Start Date, blank field 1.08, and untouched source file.

  3. Identify the intended ODS enrollment

    Locate the exact student and segment in CALPADS Enrollment History.

  4. Verify the SSID

    Confirm the current 10-digit identifier belongs to that student; do not infer it from the file.

  5. Reconstruct the operational key

    Match existing School of Attendance, verified SSID, and existing Enrollment Start Date.

  6. Confirm D versus R

    Ensure the selected transaction produces the intended record-level or replacement result.

  7. Repair the source/extract

    Correct the SIS workflow, join, delimiter, column mapping, or identifier formatting that omitted SSID.

  8. Submit and postflight

    Confirm SENR0032 clears and compare exact ODS history before and after processing.

  9. Review the full transaction population

    Find every D/R row sharing the same workflow, missing SSID, failed join, or malformed column structure.

Before closing the issue

  • Confirm the verified SSID belongs to the intended student.
  • Verify School, SSID, and existing Start Date identify the targeted ODS enrollment.
  • Confirm the transaction type matches the intended result.
  • Ensure no unrelated enrollment was deleted or replaced.
  • Verify the SIS and regenerated extract preserve the complete key.
  • Review downstream enrollment, attendance, program, assessment, cohort, and special-education effects.

Official SENR0032 troubleshooting page  |  Current CALPADS File Specifications and enrollment procedures  |  SDLA CALPADS Code Sets V.18