EDI Configurations
- Karsten Markmann
Partner Details → EDI Configurations
On this page you can configure the Edifact and X12 settings for the partner when sending and receiving messages. Technical knowledge about Edifact and X12 is needed to modify these settings.Â
The page is divided into two sections. Each section as well as its fields will be explained in detail below.
Edifact Section
This section is only relevant if the partner is exchanging EDIFACT documents via Link.
The fields contain details about how EDIFACT headers are constructed for this partner.Â
The first line in an Edifact file has the segment name UNA.
The second line in an Edifact file has the segment-name UNB.
An example could be:Â
UNA:+.? ' UNB+IATB:1+6XPPC:ZZ+LHPPC:ZZ+940101:0950+1'
Identification Type
The value created in the EDIFACT UNB segment, which specifies the Sender or Receiver value. (https://www.stylusstudio.com/edifact/40100/UNB_.htm  - 020/0004 - Interchange sender identification)
Qualifier:
The value created in the EDIFACT UNB segment, which specifies the Sender or Receiver Qualifier value. (https://www.stylusstudio.com/edifact/40100/UNB_.htm - 020/0007 - Identification code qualifier)
Comp. Elem.Sep:
The character separating each element in an EDIFACT segment. (default value: ‘ : ’) Â
Decimal Mark:
The character used for decimal notation. (default value: ‘ . ’) Â
Segment Terminator
The character separating each EDIFACT segment. (default value: " ‘ ") Â
Application Reference
The value created in EDIFACT UNB segment, which specifies the value for Application Reference. (https://www.stylusstudio.com/edifact/40100/UNB_.htm  - 070/0026 - Application reference)
Priority Code
The value created in EDIFACT UNB segment, which specifies the value for Priority. (https://www.stylusstudio.com/edifact/40100/UNB_.htm  - 080/0029 - Processing priority code)
Edifact Segment Suffix
The value separating each EDIFACT segment. (Carriage Return or  Carriage Return + Line Feed or Line Feed or None)
Enable Una
If marked, the UNA segment will be created as the first segment in the completed EDIFACT message.
Element Seperator
The character separating each data element in an EDIFACT segment. (normally “ + ’’) Â
Release Character
The character specifying that the next value in the string will be transferred to the output data. (normally “ ? ’’) Â
Repetition Character
The Repetition Character is defined in the UNA segment. Often it is blank and sometimes it is *.
Here an example where the repetition Character is defined as blank:Â
The Repetition Charracter is used to sparate repeating elements.
Password Qualifier
The value created in EDIFACT UNB segment, which specifies the value for Password Qualifier. (https://www.stylusstudio.com/edifact/40100/UNB_.htm  - 060/0025 - Recipient reference/password qualifier)
Password
The value created in the EDIFACT UNB segment, which specifies the value for Password (https://www.stylusstudio.com/edifact/40100/UNB_.htm  - 060/0022 - Recipient reference/password
Edifact Syntax
The value created in the EDIFACT UNB segment, which specifies the character set (syntax identifier) for the EDIFACT message. (https://www.stylusstudio.com/edifact/40100/UNB_.htm  - 010/0001-0002-0080-0133) - SYNTAX IDENTIFIER
X12 section
This section is only relevant if the partner is exchanging X12 documents via Link.
The fields contain details about how X12 headers are constructed for this partner.Â
Identification Type
The value created in the X12 ISA segment, which specifies the Sender or Receiver value. (https://msdn.microsoft.com/en-us/library/bb259967(v=bts.20)Â - ISA5-6)
Qualifier
The value created in the X12 ISA segment which specifies the Sender or Receiver value. (https://msdn.microsoft.com/en-us/library/bb259967(v=bts.20) – ISA5-6)
Authorization Qualifier
The value created in the X12 ISA segment, which specifies the Sender or Reciever qualifier. (https://msdn.microsoft.com/en-us/library/bb259967(v=bts.20) - ISA1-2)
Author. Quali. Value
The value created in X12 ISA segment, which specifies the Authorization Qualifier value. (https://msdn.microsoft.com/en-us/library/bb259967(v=bts.20) – ISA1-2 )
Security Qualifier
The value created in the X12 ISA segment, which specifies the Sender or Receiver Security qualifier. (https://msdn.microsoft.com/en-us/library/bb259967(v=bts.20) – ISA3-4)
Security Qualifier Value
The value created in the X12 ISA segment, which specifies the Sender or Receiver Security qualifier value. (https://msdn.microsoft.com/en-us/library/bb259967(v=bts.20) – ISA3-4)
Edifact Segment Suffix
(change guidingtxt to X12) -  The values used for separating each X12 segment. (Carriage Return or  Carriage Return + Line Feed or Line Feed or None)
Character Set
The character set used for the X12 message. (normally UTF-8/Unicode)
Comp. Elem.Sep
 X12 Component element separator. It is used to separate composite data elements.
Data Element
The character used for separating each element in a X12 segment. (normally ‘ * ’) Â
Segment Terminator
The character used for separating each EDIFACT segment. (normally “ ~ ’’) - tilde Â
Replacement Character
Replacement character is used for replacing all separator characters in the payload data when generating the outbound X12 message
Interchange Numbers
Link stores a global EDIFACT interchange number sequence in its database. Each time a new EDIFACT interchange is constructed from Link, a new number sequence is generated and used as the interchange number.
An EDIFACT ‘interchange number’ is a number used to identify an EDIFACT interchange – it appears in the header of the interchange. One interchange consists of one or several documents, each having their own document number.
Interchange Number On Resend
If you tick the Interchange Number On Resend checkbox, Link will not generate a new interchange number in case you need to resend an interchange – instead the old interchange number will be reused.
Use Partner Specific Interchange Number
If you tick the Use Partner Specific Interchange Number checkbox, Link will dedicate a sequence to the specific partner instead of using the global number sequence.
Current Specific Interchange Number
You can manually set this partner-specific interchange sequence number by supplying a value in the field Current Specific Interchange Number.
Content on this page:
The information on this page is based on Link 2.12