For EDIFACT encoded interchanges, you can set the character set for a party by setting the UNB1.1 party property in the UNB Segment Definition property page for the party as interchange receiver.
The encoding used in an incoming interchange is determined by the value of the UNB1.1 field in the header of the interchange.
This topic indicates which character sets are supported in the EDIFACT features of BizTalk Server:
| Encoding | Allows |
| UNOA | As defined in ISO 646 (with the exception of letters, lowercase a to z).
|
| UNOB | As defined in ISO 646
|
| UNOC | As defined in ISO 8859-1: Information processing – Part 1: Latin alphabet No. 1. |
| UNOD | As defined in ISO 8859-2: Information processing – Part 2: Latin alphabet No. 2. |
| UNOE | As defined in ISO 8859-5: Information processing – Part 5: Latin/Cyrillic alphabet. |
| UNOF | As defined in ISO 8859-7: Information processing – Part 7: Latin/Greek alphabet. |
| UNOG | As defined in ISO 8859-3: Information processing – Part 3: Latin alphabet. |
| UNOH | As defined in ISO 8859-4: Information processing – Part 4: Latin alphabet. |
| UNOI | As defined in ISO 8859-6: Information processing – Part 6: Latin/Arabic alphabet. |
| UNOJ | As defined in ISO 8859-8: Information processing – Part 8: Latin/Hebrew alphabet. |
| UNOK | As defined in ISO 8859-9: Information processing – Part 9: Latin alphabet. |
| UNOX | Code extension technique as defined by ISO 2022 utilizing the escape techniques in accordance with ISO 2375.
ISO-2022-JP character set
|
| UNOY | ISO 10646-1 octet without code extension technique. |
| KECA | A to Z 0 to 9 . , – ( ) / = ! ” % & * ; < > Windows 949 code page
|
useful
thank you for the throughout description of edi encodings.
what about different versions? How is UNOC:2 different from UNOC:3?
The number in the next element (2, 3) refers to the syntax of the message. UNOC:3 = Encoding ISO 8859-1 and syntax of the message 3.
Thank you for this post!
BTS 2016: Is there any way how to set syntax version 4 in outbound one way agreement? Even documented:
https://docs.microsoft.com/en-us/biztalk/core/configuring-charset-and-separators-edifact
I do not see this option in GUI (Characters set and separators. There is only UNB1.1 to select not UNB1.2
Just additional comment, this part of GUI disappeared after applying CU 5 and FP 3
Hello I am facing an issue in processing EDIFACT file containing European characters. UNB1.1 Contains UNOD,
An output message of the component “Unknown ” in receive pipeline “Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” is suspended due to the following error:
Error encountered during parsing. The Edifact transaction set with id ‘00000269034’ contained in interchange (without group) with id ‘00003’, with sender id ‘O0013000001AB R3A’, receiver id ‘209690’ is being suspended with following errors:
Error: 1 (Field level error)
SegmentID: FTX
Position in TS: 6
Data Element ID: C10801
Position in Segment: 5
Position in Field: 1
Data Value:
21: Invalid character found
ŠKOT This characters do not process
Hello, I need set encoding UNOW, but I cannot find it in BizTalk. Is some choice how can I set it please?
Thank you
Actually, it is a bit more complicated than that, AFAIK. Syntax version 1+2 only support UNOA and UNOB. With Syntax version 3 support for UNOC-UNOF were added, according to the VDA specification, which builds up on Edifact, syntax version 3 should also defines UNOE and UNOG, though I couldn’t find any freely accessible sources on that matter. All the other encodings such as UNOW for UTF-8 encoded representations should only be valid if syntax version 4 is declared.