FRMT0002

Valid versus invalid date examples

The date shown on an SIS screen may be correct for a person to read while the exported value is wrong for CALPADS. Inspect the actual SENR file value.

Format is not accuracy: 20110507 has the correct shape, but it is not necessarily the student’s correct birth date. Likewise, 20260230 has eight digits but is not a real calendar date. Clearing FRMT0002 does not establish that the value is accurate, chronologically possible, or valid under other CALPADS rules.

What to verify for each of the three fields

Blank Exit Date: Enrollment Exit Date is not required for every open enrollment. Do not invent an exit date merely to fill the field. When it is populated, however, its exported form must be CCYYMMDD and it must represent the actual exit event.

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 generated file would reproduce the error.

Choose the diagnostic pathway

• SIS display versus exported file
  • What exact characters appear in the rejected SENR row?
  • Did the extract export slashes, hyphens, a timestamp, spaces, or a two-digit year?
  • Did spreadsheet software automatically reformat the date?
  • Does a correctly accepted row from the same extract use CCYYMMDD?
• Student Birth Date and identity evidence
  • Does the SIS date agree with the student’s cumulative record?
  • When authorized and available, does it agree with the birth certificate or other accepted identity documentation?
  • Is the submitted row connected to the intended student and SSID?
  • If the underlying birth date is wrong, has the authorized SINF or local demographic-correction process been followed?
• Enrollment Start Date
  • When was the student first expected to attend?
  • Does registration and attendance evidence support that date?
  • Could a rollover, pre-enrollment, or import process have supplied the wrong year?
  • Does the date fit the surrounding CALPADS enrollment sequence?
• Enrollment Exit Date
  • Is the enrollment still open and therefore appropriately blank?
  • If it ended, what was the last date the student was expected to attend?
  • Do withdrawal, transfer, attendance, and completion records agree?
  • Are Exit Date, Exit Reason, and any completion status describing the same event?
• Repeatable extract or integration defect
  • Are multiple rejected rows produced by the same field mapping?
  • Did a report, integration, CSV editor, or spreadsheet step change the representation?
  • Will the next scheduled extract reproduce the defect?
  • Can the source mapping be corrected and regression-tested?
• Downstream student-record effects
  • Could a corrected birth date affect identity matching or age-based validations?
  • Could corrected enrollment dates affect SINF, SPRG, SELA, attendance, assessment, course, cohort, or special-education reporting?
  • Does CALPADS contain an older or conflicting enrollment that also requires review?

Read the date from evidence to acceptance

1. 1
   EvidenceConfirm the real date.
2. 2
   SISVerify the stored value.
3. 3
   ExtractInspect all eight characters.
4. 4
   CALPADSReview the accepted history.
5. 5
   ReconcileCheck connected records.

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 opening or resaving the file in software that may reformat dates.

2. 2

   Identify which of the three dates failed

   Map the rejected row to 1.17 Birth Date, 1.22 Enrollment Start Date, and 1.25 Enrollment Exit Date. Do not shift columns when Exit Date or another optional field is blank.

3. 3

   Inspect the literal exported value

   Confirm that each populated date contains exactly eight digits in CCYYMMDD order, without separators, spaces, text, or a time component.

4. 4

   Confirm the date is real and chronologically possible

   Check month and day validity, four-digit year, birth-before-enrollment chronology, start/exit sequence, and the surrounding enrollment history. A structurally correct value may still fail a different validation.

5. 5

   Double-check the authoritative evidence

   For Birth Date, compare the cumulative file and, when authorized and available, the birth certificate or other locally accepted identity document. For enrollment dates, compare registration, attendance, withdrawal, transfer, and completion evidence as applicable.

6. 6

   Trace the first divergence

   Determine whether the incorrect representation or value originated in the source record, SIS configuration, report definition, integration, spreadsheet process, or vendor extract.

7. 7

   Correct the owning system and process

   Use the authorized demographic or enrollment correction procedure. Repair a repeatable mapping or transformation instead of hand-editing only one upload row.

8. 8

   Regenerate, submit, and regression-check

   Confirm FRMT0002 clears, inspect the accepted enrollment history, and test other records produced by the same date field, mapping, or extract rule.

Before closing the issue

• Confirm FRMT0002 no longer appears for the intended enrollment.
• Verify all three submitted date positions and the complete accepted enrollment history in CALPADS.
• Confirm the corrected value agrees with authorized source evidence—not merely the required format.
• Document the evidence reviewed, correction owner, correction location, and broader extract impact.
• Review connected student records and reports affected by a changed birth, start, or exit date.