SENR0167

The current-year boundary controls Replace

The CALPADS current academic year is determined by processing context. Verify the active CALPADS year and current specifications before constructing the correction; do not assume that “current school year” means the year selected in a local SIS screen.

What the transaction codes actually do

The SENR operational key determines what is found

If only a non-key field is changing, the delete and add rows generally use the same operational key. If School or Start Date is changing, the delete row must identify the old key and the Add/Update row must contain the new key.

Build the correct D + Add/Update pattern

Same file does not eliminate sequencing risk

The official guidance recommends a Delete row and an Add row in the same file for this historical correction. CALPADS specifications state that mixed transaction types post in the order Delete, Add/Update, then Replace; however, validation processing is not necessarily ordered the same way. Therefore:

• Review the delete and add as a matched pair before upload.
• Do not include unrelated destructive transactions in the correction batch.
• Ensure the Add/Update row is independently complete and valid.
• After processing, verify both row results—not merely the overall file status.
• Confirm the old record is gone and the corrected record exists before closing the issue.

Preflight the historical replacement

What commonly produces SENR0167

Choose the diagnostic pathway

• Confirm the academic-year boundary
  • What Enrollment Start Date is on the existing ODS record?
  • Which academic year does CALPADS treat as current at processing time?
  • Is the local SIS displaying a selected year that differs from CALPADS processing context?
  • Is the Start Date itself supported by attendance and enrollment evidence?
• Confirm the intended correction
  • Which exact field is wrong?
  • Is it part of the operational key?
  • Should a corrected record replace the old one, or should the old record simply be deleted?
  • What should the complete enrollment history look like afterward?
  • Does the correction affect later enrollment segments?
• Build the old operational key
  • What School of Attendance is currently stored?
  • What verified SSID is on the record?
  • What old Enrollment Start Date is stored?
  • Do all three delete-key values match the ODS exactly?
  • Did a spreadsheet alter code or identifier formatting?
• Build the complete corrected record
  • Does the Add/Update row contain every required SENR field?
  • Are dates chronological and codes current?
  • Do Grade, Exit Reason, Completion Status, transfer, and residence fields form valid combinations?
  • Will the corrected record create a gap, overlap, or duplicate?
  • Can the row pass validation independently if processed after the delete?
• Perform postflight verification
  • Did the Delete row post?
  • Did the Add/Update row post?
  • Is the old operational key absent?
  • Is the complete corrected enrollment present?
  • Were unrelated historical records preserved?
  • Will the next extract reproduce the accepted history?

Replace a historical record safely

1. 1
   Before-statePreserve ODS history.
2. 2
   Old keyBuild Delete row.
3. 3
   New recordBuild complete Add.
4. 4
   ProcessingSubmit controlled pair.
5. 5
   After-stateVerify exact history.

Recommended correction path

1. 1

   Stop the invalid Replace batch

   Do not move historical dates or repeatedly resubmit R transactions.

2. 2

   Preserve the before-state

   Capture submission ID, rejected row, full ODS enrollment history, and existing target record.

3. 3

   Verify student and historical evidence

   Confirm SSID, school, dates, attendance, status, exit, and intended correction.

4. 4

   Confirm the record is prior-year

   Compare the existing Start Date with the current CALPADS academic-year boundary.

5. 5

   Build the Delete row

   Use D with the exact old School of Attendance, verified SSID, and old Start Date.

6. 6

   Build the complete Add/Update row

   Use blank/space/A with every supported corrected field and the intended operational key.

7. 7

   Preflight the matched pair

   Validate scope, identity, keys, chronology, code combinations, completeness, and recovery evidence.

8. 8

   Submit and postflight

   Confirm both rows’ results, removal of the old record, addition of the corrected record, and preservation of unrelated history.

9. 9

   Repair the recurring workflow

   Find other prior-year R rows and correct the SIS/vendor/extract logic that assigned the invalid method.

Before closing the issue

• Confirm no historical Start Date was altered merely to satisfy R.
• Verify the Delete row used the exact old operational key.
• Confirm the Add/Update row contains the complete supported enrollment.
• Ensure both transaction results were reviewed individually.
• Verify the old record is absent and the corrected record is present.
• Confirm the SIS and next extract reproduce the accepted history.
• Review enrollment, attendance, program, assessment, cohort, funding, and special-education effects.