Interpreting validation error codes
Use the Validate Document Structure option to enforce document schema adherence. Recognition of the inbound documents can fail when they do not adhere to the underlying schema. If there are violations, the transaction summary captures them as validation errors. Each of the error corresponds to an error code.
Important: Examine these validation errors in the output of the
convertEDIMessagetoDocument operation in webMethods Integration.The following table describes the validation error codes:
| Error Code | Description |
|---|---|
| 1 | In the EDI document schema, the Mandatory drop-down menu is set to true for this element, but the element does not occur in the EDI document. |
| 2 | Reserved for future use. |
| 3 | Unexpected element. This field is not allowed in the record or composite in which it appears. |
| 4 | In the EDI document schema, a length validator is specified in the Validator property for this field. The value in the EDI document exceeds the maximum length specified. |
| 5 | In the EDI document schema, a length validator is specified in the Validator property for this field. The value in the EDI document did not meet the minimum length specified. |
| 6 | Reserved for future use. |
| 7 | In the EDI document schema, a code list validator is specified in the Validator property for this field. The value in the EDI document is not listed in the EDI schema as a valid value. |
| 8 | Reserved for future use. |
| 9 | Reserved for future use. |
| 10 | In the EDI document schema, a conditional validator is specified in the
Validator property for this composite or record. The contents of this
composite or record does not meet the conditional requirements. Note: The
errorMessage variable in the convertEDIMessagetoDocument operation
contains the number of the condition that failed. If you have a validation string of C010203R0405
and both conditions fail, the error message states that rules 0 and 1 are violated. If only the
second is violated, it states that the rule 1 is violated. |
| 11 | The record is not defined anywhere in the EDI document schema. This error appears only when you do not specify a Default Record or selected Allow Undefined Data where this record appears in the document. If you specify either of these properties, you do not receive this error. |
| 12 | The record is defined in this EDI document schema, but it occurs in the document in a location prohibited by the EDI document schema. |
| 13 | Reserved for future use. |
| 14 | In the EDI document schema, the number of record instances in the EDI document exceeds the specified maximum number of repeats. This is validated against the Max Repeat property for a particular record. |
| 15 | Reserved for future use. |
| 16 | Within a record, this code indicates that the record contains a composite or field error. For a composite, this indicates that the composite contains a subfield error. |
| 17 | A string might not be formatted into the intended format. A format service reported that the data might not be formatted properly. |
| 18 | The conditional validation rule requires a field, but that field is not present in the data. |
| 19 | A conditional validation rule excludes a field, but that field is present in the data. |