EDI Experience – Common errors and solutions

ERROR: Invalid value in data element

Data Element ID: FTX01
Position in Segment: 3
Position in Field: 2
Data Value: ZZZ
12: Invalid value in data element

Cause

  • Your Data elements FTX01 contain the invalid code, “ZZZ”. These elements have specific lists of allowable codes.

Solution

  • This code must be added to the list of the FTX01 element in the schema.

ERROR: Data element too long

Data Element ID: C08001
Position in Segment: 5
Position in Field: 1
Data Value: XXXXXXXXX X�X DE X�XXXX XX XXXXX
39: Data element too long

Cause

  • The value “C08001” is too long for the defined length of the element.

Solution

  • Check the max length of the UNB9 element and correct your data. If you and your trading partner agree, both may increase the max length, in which case you would modify your schema.

ERROR: Invalid character(s) found in data element

Data Element ID: UNB11
Position in Segment: 11
Data Value: METCASH-AC3:ZZ
Or
Data Value:
37: Invalid character(s) found in data element

Cause

  • You have bad data in an UNB11 element.
  • You have an invalid character in an UNB11 element.

Solution

  • Often this error occurs when you put a space in a mandatory element to avoid failing for missing mandatory. If this is the situation and you have no valid data for the element, you may have to change the element to optional in the schema.
  • This could be either the ‘-‘ or the ‘:’, or both, depending on the character set you are using and on what separators you using. If this is an outbound transaction, you can use a script to remove or replace the offending character

ERROR: Duplicate Control Number

Error: 1 (Miscellaneous error)
25: Duplicate Control Number
Error: 2 (Field level error)
SegmentID:
Position in TS: 1
Data Element ID:
Position in Segment: 13
Position in Field: 1
Data Value: <n>
25: Duplicate Control Number

Cause

  • This problem occurs because the interchange control numbers in the ISA13 segment of the suspended EDI messages are still recorded in BizTalk Server. This causes a duplicate detection check to be performed.

Solution

References

Tags: BizTalk | EDI | Errors and Warnings, Causes and Solutions

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

BizTalk360
BizTalk Server

Over 500+ customers across
30+ countries depend on BizTalk360

Learn More
Serverless360
Azure

Manage and monitor serverless
components effortlessly

Learn More
Atomicscope
Business Users

Monitor your Business Activity in iPaaS
or Hybrid integration solutions

Learn More

Back to Top