How to Decipher Data Validation Failure Results and Error Codes

Below are the results of two validations that failed. You would like to know how to interpret the validation failure data.

<invalid position=”39” error_code=”7” error=”invalid Data” />  

Answer

ERROR POSITION

To determine the location of the error (Error Position), count the number of digits from left to right, counting non-printable characters as one digit. The first digit will always be zero, then one, then two…

For example – for the data below, all the non-printable ASCII characters were replaced with an asterisk (*)

[)><0x1E>12<0x1D>CAG 75276<0x1D>PNO 56302-13159-023<0x1D>SEQ B3146-00015<0x1D>(MFR 1LFX2)<0x1E><0x04> 

Error Position: 53 In this example the error started at the 53rd character. 
Error Code: 6 (Invalid Text Element Identifier) The pair of parentheses should not be there.

The error position could indicate one of the following three scenarios:

1. Indicates the first invalid digit
2. Indicates the start of invalid section
3. Signals the following section as invalid

Examples:

[)><0x1E>12<0x1D>CAG 75276<0x1D>PNO 56302-13159-023<0x1D>SEQ B3146-00015<0x1D>(MFR 1LFX2)<0x1E><0x04>

Error Position: 53 
Error Code: 6 (Invalid Text Element Identifier) The pair of parentheses should not be there.

[)><0x1E>06<0x1D>17V12345<0x1D>1P234tyu<0x1D>S6789<0x1E><0x04>

Error Position: 18 
Error Code: 7 (Invalid Data) Lower case characters are invalid characters.  

[)><0x1E>12<0x1D>UID LDN41164 123 ABC<0x1E><0x04>

Error Position: 12 
Error Code: 7 (Invalid Data) The spaces should not be there.

[)><0x1E>12<0x1D>UIDLDN41164123ABC<0x1E><0x04>

Error Position: 7 
Error Code: 6 (Invalid Text Element Identifier) The qualifier “UID” needs a space after it.

[)><0x1E>12<0x1D>PNR 901-366-302-107<0x1E><0x04>

Error Position: 7 
Error Code: 13 (Invalid application field) You cannot have a PNR without first having a UID.
 

ERROR CODE

The Data Validation Fail error codes:

1. Invalid symbology identifier. The symbology identifier is the 3-character string that not only identifies the type of symbology used for encoding the data but also describes how to process the data. This string may be optionally passed as input to the tool in addition to the decoded data either as a separate entity or by prefixing it to the data stream.

   Example: For a UCC/EAN-128 symbol, the symbology identifier is ]C1. In some applications, this will be the only way to accurately and automatically differentiate between in-house or industry Code 128 and UCC/EAN-128 symbols (that encode EAN.UCC Application Identifiers). Without symbology identifiers, you wouldn't know how to process the data in the symbol.  

2. Pattern mismatch.
3. Invalid data qualifiers (AI, DI or TEI).
4. Invalid Application Identifier (AI).
5. Invalid Data Identifier (DI).
6. Invalid Text Element Identifier (TEI).
7. Invalid Data: if the data does not agree with the data qualifier in type, length or value.
8. Invalid field separator.
9. Not ISO/IEC 15434 compliant.
10. Unsupported formats (e.g. in DoD UID applications, formats other than 05, 06 or DD).
11. Invalid format code: format codes other than 00-99 and DD.
12. ISO/IEC 15434 not supported if ISO/IEC 15434 validation option is selected, but the decoded stream is not from a 2D symbol. It is possible to report this failure only if the symbology identifier is passed as input to the tool.
13. Invalid application field: a field that is not supported in the application.
14. Unsupported application field: a field that is supported in the application but not supported by the tool.

15. Invalid application data: if the data does not meet application-specific requirements.

    Example: DoD UID applications have the following requirements: The enterprise ID string of characters will not exceed 13 characters, excluding the data qualifier. The original part, lot or batch number string of characters (including permissible special characters) will not exceed 32 characters, excluding the data qualifier. The serial number string of characters (including permissible special characters) will not exceed 30 characters, excluding the data qualifier.

16. Presence of multiple formats in the same data stream (e.g. in DoD UID applications, more than one format cannot be present in the data stream).
17. Duplicate fields: multiple occurrences of the same data qualifier in the same symbol. Certain applications like the DoD UID applications do not allow duplicate fields in the same symbol.
18. Invalid UID: not all the fields required to construct a valid Construct #1 or Construct #2 UID are present.
19. Invalid Construct #1 UID: not all the fields required to construct a valid Construct #1 UID are present.
20. Invalid Construct #2 UID: not all the fields required to construct a valid Construct #2 UID are present.
21. Missing Format Trailer when checking for compliance to ISO 15434 syntax or DoD UID.
22. Missing Message Trailer when checking for compliance to ISO 15434 syntax or DoD UID.