FRMT0001

What a field-length failure looks like

Count the characters in the exported SENR value, not only what appears on the SIS screen. Spaces, punctuation, spreadsheet-added decimals, and descriptive text appended to a code all count.

Length is only the first gate: A value can have the correct number of characters and still fail a code-set, format, combination, chronology, or accuracy rule. For example, a one-character gender value that is not in the current Gender Code Set is not made valid merely because its length is one.

Version 18.0 SENR field-length reference

Use the field number to match the rejected value to its position in the SENR layout. CS means coded or character string; DT means date. “Maximum” is the largest permitted character count, not permission to ignore required formats or code sets.

Source: CALPADS File Specifications Version 18.0, Table 3-1, SSID Enrollment File Format. For coded values and valid combinations, also consult the current CALPADS Code Sets and Valid Code Combinations.

How this record moves through CALPADS

Upload reminder: A file can upload successfully while individual records reject. Correct the source or extract when the next file would reproduce the error.

Choose the diagnostic pathway

• SIS, extract, and CALPADS reconciliation
  • Is the authoritative SIS record correct?
  • Did the extract transform or omit a value?
  • Does CALPADS contain an older or conflicting enrollment?
  • Will the next extract reproduce the error?
• SSID and student identity
  • Does the student have the correct SSID?
  • Does the local record point to a retired or replaced SSID?
  • Are staff reviewing the intended student before changing enrollment history?
• LEA, school, and enrollment ownership
  • Which LEA and school own the enrollment?
  • Is the school authorized under the Reporting LEA?
  • Is the enrollment primary, secondary, short-term, or non-ADA?
• Enrollment dates and chronology
  • When did the student actually begin attending?
  • Is the enrollment still open, or should it have an exit?
  • Does another enrollment overlap or continue this record?
  • Do the SIS and CALPADS histories tell the same story?
• Enrollment exit and completion
  • Is the enrollment still open?
  • When and why did the student leave?
  • Did the student complete school?
  • Was another enrollment expected?
  • Do Exit Reason and Completion Status describe the same event?
• E150 and continuing enrollment
  • Was E150 used for a midyear update rather than a departure?
  • Was the continuing enrollment created for the next calendar day?
  • Did grade, transfer status, or geographic residence actually change?
• Downstream student-record effects
  • Does SINF overlap the qualifying enrollment?
  • Could SPRG or SELA depend on these dates?
  • Could the change affect attendance, assessment, course, cohort, dropout, or special-education reporting?

Read the enrollment sequence

1. 1
   SourceConfirm actual enrollment.
2. 2
   SISInspect the authoritative record.
3. 3
   ExtractReview the submitted value.
4. 4
   CALPADSCompare ODS history.
5. 5
   VerifyConfirm the corrected result.

Recommended correction path

1. 1

   Preserve the rejected row

   Capture the submission ID, row number, export date, exact delimited row, and CALPADS error details before editing.

2. 2

   Match the row to fields 1.01–1.35

   Use the Version 18.0 SENR layout to identify each column. Do not shift values left when an optional field is blank.

3. 3

   Count the exported characters

   Check the actual file value for spaces, punctuation, decimals, descriptive labels, or date separators that are not obvious on the SIS screen.

4. 4

   Compare with a correctly accepted row

   Use a row from the same extract when possible. A missing delimiter or quotation problem earlier in the row can make a later value appear overlength.

5. 5

   Reconstruct what actually occurred

   Confirm the intended student, school, enrollment dates, status, grade, and exit information from authoritative local records.

6. 6

   Trace the value to its source

   Determine whether the SIS field, report definition, integration, spreadsheet step, or vendor extract produced the extra characters.

7. 7

   Correct the repeatable rule

   Repair the owning system or export mapping. Avoid a one-time file edit that the next extract will reproduce.

8. 8

   Regenerate, submit, and regression-check

   Confirm FRMT0001 clears, verify the accepted enrollment history, and inspect other records produced by the same field or extract rule.

Before closing the issue

• Confirm FRMT0001 no longer appears for the intended enrollment.
• Verify the complete accepted enrollment history in CALPADS.
• Document source evidence, owner, correction location, and broader extract impact.
• Review downstream student records and reports affected by the correction.