Rule library
FatalField 11.000Subject

UAD1680 — The type of functional issue must be included. Select 'None' if there are no functional issues.

Where this rule lives in the report

Functional Obsolescence
Functional Issues

Report Section as the GSEs define them — the black tab and grey bar you already read on the URAR.

Severity
Fatal — this blocks your UCDP submission and must be fixed before delivery.
Triggered when
at least one instance of FUNCTIONAL_ISSUE is not provided or FunctionalIssueType is not provided in a given instance of FUNCTIONAL_ISSUE
Data Point Name
FunctionalIssueType
Unique ID
3600.0002
Report Field ID
11.000
What this field means
A value from a MISMO prescribed list that represents an apparent functional issue observed.

How to fix UAD1680

UAD1680 is a Fatal UAD 3.6 edit, so clear it before the appraisal report goes to UCDP.

  1. 01Open the Functional Obsolescence › Functional Issues area of the URAR and find Functional Issues.
  2. 02Check the condition that triggers UAD1680: at least one instance of FUNCTIONAL_ISSUE is not provided or FunctionalIssueType is not provided in a given instance of FUNCTIONAL_ISSUE.
  3. 03Correct the missing, invalid, duplicate, or inconsistent value before submitting to UCDP.
  4. 04Use the official Single-family (SF1) sample value on this page as a reference pattern, then re-run validation.

This fix guidance is derived from the published rule message, trigger logic, report location, field definition, and official sample data available for this rule.

Seen in the sample reports

How this field is populated in the official UAD 3.6 sample scenarios.

More rules in “Functional Obsolescence”

UAD1681Provide a description when 'Functional Issues' = 'Other'.
Fatal