BC EDI is rejecting an X12 document with ISO-8859-1 characters.How do I get BC EDI process this document correctly?
Article ID: KB0085913
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Resolution:
Historically, EDI X12 interchanges have been encoded using ASCII characters. However, some customers may have X12 documents that include ISO-8859-1 characters (such as "Ø") included in the transaction fields. These characters can cause SpecBuilder and BC to generate a "5020: An invalid character was encountered in a data element.
Details: Element XXX data type must be 'Alphanumeric'." error when processing a document. This is because the ISO-8859-1 character may not be included in the character set that is used when processing the X12 document.
To get EDI 5.1 or EDI 2.8 to process the document:
1. With SpecBuilder, open the actions-x12.ecs file, in $BC_HOME/protocols/edi/tpcl/config (EDI 5.1) or $BC_HOME/EDI/config directory (EDI 2.8.x), and look for the SelectedNode associated with the X12 version (example Guideline:::V4010 would be for 4010 documents).
2. Open the PropertyChange below the SelectedNode, which will show the "CHARSET" associated with the guideline. Click on the character set to edit it, and add the character that you need to process.
3. Save the file, and restart the BC Server. BC should be able to process your document.
To get EDI 5.2 to process this document:
1. With Notepad or another text editor, pen the $BC_HOME/protocols/edi/tpcl/config/charsets/x12.cs file and look for your transaction type.
2. Add the UTF-16 character into the <charset></charset> field.
3. Save the file, and restart the BC Server.
Historically, EDI X12 interchanges have been encoded using ASCII characters. However, some customers may have X12 documents that include ISO-8859-1 characters (such as "Ø") included in the transaction fields. These characters can cause SpecBuilder and BC to generate a "5020: An invalid character was encountered in a data element.
Details: Element XXX data type must be 'Alphanumeric'." error when processing a document. This is because the ISO-8859-1 character may not be included in the character set that is used when processing the X12 document.
To get EDI 5.1 or EDI 2.8 to process the document:
1. With SpecBuilder, open the actions-x12.ecs file, in $BC_HOME/protocols/edi/tpcl/config (EDI 5.1) or $BC_HOME/EDI/config directory (EDI 2.8.x), and look for the SelectedNode associated with the X12 version (example Guideline:::V4010 would be for 4010 documents).
2. Open the PropertyChange below the SelectedNode, which will show the "CHARSET" associated with the guideline. Click on the character set to edit it, and add the character that you need to process.
3. Save the file, and restart the BC Server. BC should be able to process your document.
To get EDI 5.2 to process this document:
1. With Notepad or another text editor, pen the $BC_HOME/protocols/edi/tpcl/config/charsets/x12.cs file and look for your transaction type.
2. Add the UTF-16 character into the <charset></charset> field.
3. Save the file, and restart the BC Server.
Issue/Introduction
BC EDI is rejecting an X12 document with ISO-8859-1 characters.How do I get BC EDI process this document correctly?
Feedback
Yes
No
Powered by
