Skip to main content

CALPADS error brief · FRMT

FRMT0006

Wrong format for Incident Result Duration Days
Severity Fatal
Error type Input Validation
Record type FRMT

Official CALPADS rule

What CALPADS is rejecting

Format for Incident Result Duration Days must match CALPADS File Specifications (CFS)

Focus fields

Fields validated

19.16 Incident Result Duration Days

Recommended correction path

Suggested resolution

SIRS • Fatal input validation

FRMT0006: Wrong Format for Incident Result Duration Days

Field 19.16 is not in a numeric format allowed by the Version 18 CALPADS File Specifications. Preserve the documented disciplinary result, correct the source value or export transformation, and verify the SIRS row remains aligned with the related incident and offense records.

Official validation

Incident Result Duration Days must use one to three digits, optionally followed by a decimal point and one or two decimal digits.

  • Allowed patterns: #, #.#, #.##, ##, ##.#, ##.##, ###, ###.#, or ###.##
  • Field validated: 19.16 — Incident Result Duration Days
  • Submission: SIRS
  • Severity: Fatal
  • Type: Input Validation

Separate format from factual duration

Structurally valid examples

  • 1
  • 2.5
  • 10.25
  • 100
  • 999.99

Each value must still equal the supported duration for the student’s actual result.

Common invalid formats

  • 2 days or other text
  • 2,5 using a comma
  • 2.125 with three decimal places
  • .5 without a leading digit
  • A value shifted into the wrong column

Check the connected result rules

  • Field 19.16 may be populated only for Incident Result Codes 100 (suspension), 110 (in-school suspension), or 200 (expulsion).
  • If Incident Result Duration Days equals 0, Incident Result Modification Code must be 100 (Enforcement Suspended) or 200 (Shortened).
  • The duration must belong to the same student, Incident ID Local, and disciplinary result as the submitted SIRS row.
  • The SIRS result must remain reconciled with its SINC parent and any required SOFF records.

Recommended resolution

  1. Preserve the rejected row

    Capture the submission ID, SSID, school, Academic Year ID, Incident ID Local, raw SIRS row, and exact value transmitted in field 19.16.

  2. Confirm the documented result

    Match the row to the correct incident, student, result code, authorization, modification, and duration in the behavior-management or student-information system.

  3. Compare source and extract

    Determine whether the source value is invalid or whether the export introduced text, commas, excessive precision, blank-space characters, or a column shift.

  4. Correct the owning source or transformation

    Enter the supported duration in an allowed numeric format or repair the extract rule that formats the value. Avoid a one-time file edit that the next export will recreate.

  5. Validate result dependencies

    Confirm the duration is permitted for the Incident Result Code and that any zero duration has the required modification code.

  6. Regenerate and inspect

    Check the complete SIRS row for correct field order, delimiters, column count, decimal value, and incident operational key.

  7. Submit and reconcile

    Confirm FRMT0006 clears, the accepted result matches the authorized action, and the SINC, SIRS, and any required SOFF records describe the same incident.

  8. Review the affected population

    Check other incidents sharing the same duration unit, decimal conversion, behavior-system interface, or extraction rule.

Close only after verification

  • The duration equals the supported disciplinary result without unapproved rounding or alteration.
  • Field 19.16 matches one of the Version 18 numeric patterns.
  • The Incident Result Code and Modification Code permit the submitted duration.
  • The source system, regenerated SIRS row, and accepted CALPADS record agree.
  • Related SINC and SOFF records and other shared extracts have been checked.

Official CALPADS FRMT0006 troubleshooting page  |  Current CALPADS File Specifications and code sets