diff --git a/product-updates/img/error-reports/error-report.png b/product-updates/img/error-reports/error-report.png index bbb9594e9..79f96d81b 100644 Binary files a/product-updates/img/error-reports/error-report.png and b/product-updates/img/error-reports/error-report.png differ diff --git a/product-updates/knowledge-center/index.html b/product-updates/knowledge-center/index.html index 770593eb1..b0561bf2f 100644 --- a/product-updates/knowledge-center/index.html +++ b/product-updates/knowledge-center/index.html @@ -337,6 +337,99 @@

Use an existing Login.gov AccountWhat's new in TDP

+ +

October 10th 2024 (v 3.6.4)

+

Added:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Error TypePriorityImpactFile Status
File Pre-Check + High + + Some or all of the record(s) in the file are rejected + + Rejected or Partially Accepted with errors +
Case Consistency + High + + Record(s) rejected + + Partially accepted with errors +
Record Value Invalid + Low + + Record(s) accepted + + Accepted with errors +
Record Value Inconsistency + Low + + Record(s) accepted + + Accepted with errors +
+ + + + +
+ +

September 10th 2024 (v 3.6.0)

In Development:

@@ -565,13 +564,101 @@

Overview of the Error Report

TDP error report containing some of the error examples below opened in Excel + +
+

Interpreting Error Types

+
+

There are four error types which affect data submission differently. Unlike low priority errors, high priority errors will prevent some/all records in the file from being accepted into the TDP system's database. You may filter the report to display high-priority errors first. Low priority errors will not affect whether a record makes it into the data base, but we encourage you to refer to the coding instructions to make corrections for the most accurate data. Learn how to filter data here.

+
+

For users familiar with the legacy system, errors are equivalent to edits. File Pre-Check and Case Consistency errors are similar to fatal edits and Record Value Invalid and Record Value Inconsistency are similar to warnings.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Error TypeDescriptionPriorityImpactFile Status
File Pre-Check + Relate to the format of the records within a file (e.g. incorrect headers, incorrect record length). + + High + + Some or all of the record(s) in the file are rejected + Rejected or Partially Accepted with errors + +
Case Consistency + Relates to inconsistency across records (e.g. inconsistency across related person- and family-level records). + These errors are triggered by a series of checks that confirm that all the records for a family in a given month are related in a meaningful way. + High + + Record(s) rejected + + Partially accepted with errors +
Record Value Invalid + These errors involve unexpected values in the record (e.g. missing values or out-of-range values). + + Low + + Record(s) accepted + + Accepted with errors +
Record Value Inconsistency + These errors stem from inconsistencies in the record (e.g. conflicting data between items in the same record). + + Low + + Record(s) accepted + + Accepted with errors +
+
+ + +

Examples of Common Errors

Below are examples of error messages associated with common issues that may be listed in an error report.

- -

@@ -581,11 +668,10 @@

Examples of Common Errors

-

Errors related to header or trailer records:

+

File Pre-Check: Errors related to header or trailer records:

Header-related errors are often the result of submitting files for a fiscal period that is not consistent with the time period in the header record (e.g. trying to submit 2022 data for a 2024 submission). Other header or trailer errors may be related to how the file was generated (e.g. the file produced is missing a header or trailer record). Some examples of how these types of error may appear in your error report are included below:

-
Submitted reporting year: 2024, quarter: 1 doesn't match file reporting year 2022, quarter: 4. @@ -593,29 +679,31 @@

Errors related to header or trailer records:

Your file does not begin with a HEADER record.
- -

Please refer to the Transmission File Header Record definitions to compare your file's header or trailer to the expected layout.

-

Errors related to record length:

+

File Pre-Check: Errors related to record length:

Record length-related errors will be raised if the specified record is not aligned with the record layout requirements. For example, this kind of error may appear as follows in the report:

- - - - T6 record length is 409 characters but must be 379. +
+

Please refer to the Transmission File Layout documents to compare your records against their expected layouts.

-
-

Please refer to the Transmission File Layout documents to compare your records against their expected layouts.

+
+ +
+

Errors with inconsistent values across related records may require review of the coding instructions to determine the proper correction. In the example below, the error is communicating that a T1 (family) record was found in the file that did not have a corresponding T2 (adult) or T3 (child) record, which effectively means that person-level records associated with this family are missing from the file.

+
+ Every T1 record should have at least one corresponding T2 or T3 record with the same Report Month & Year and Case Number. + +
-

Errors related to invalid values for a specific item/data element:

+

Record Value Invalid: Errors related to invalid values for a specific item/data element:

Invalid value errors can come up when a specific item/data element has an unexpected value (e.g. a letter or a symbol was reported for the zip code field, such as: "462$1"):

@@ -630,32 +718,15 @@

Errors related to invalid values for a specific item/data element:

  • TANF (ACF-199) and SSP-MOE (ACF-209) Coding Instructions
  • -
    -

    Errors related to inconsistent values for related items/data elements in the same record:

    +

    Record Value Inconsistency: Errors related to inconsistent values for related items/data elements in the same record:

    Some errors may require review of the coding instructions for multiple items (and their respective values) to determine the proper correction. In the example below, the error is communicating that the value reported for Item 49 is in a conflict with the value for Item 30 in the same record. This message suggests a problem with either the value of Item 49 or the value of Item 30. Refer to the coding instructions and your own data to determine which value needs to be corrected.

    - - - -
    - If Item 30 (Family Affiliation) is 1 then Item 49 (Work Participation Status) must be in set of values [01, 02, 05, 07, 09, 15, 17, 18, 19, 99]. -
    - -
    - -
    -

    Errors with inconsistent values across related records may require review of the coding instructions to determine the proper correction. In the example below, the error is communicating that a T1 (family) record was found in the file that did not have a corresponding T2 (adult) or T3 (child) record, which effectively means that person-level records associated with this family are missing from the file.

    - - - -
    - Every T1 record should have at least one corresponding T2 or T3 record with the same Report Month & Year and Case Number. - +If Item 30 (Family Affiliation) is 1 then Item 49 (Work Participation Status) must be in set of values [01, 02, 05, 07, 09, 15, 17, 18, 19, 99]. + +
    - -