EDIFACT: The universal message standard

Overview

EDIFACT is the abbreviation for "Electronic Data Interchange for Administration, Commerce and Transport". This is a global set of rules defined by the UN for the inter-company electronic data exchange between two or more business partners via EDI.

The goal of EDIFACT is the optimization and standardization of the data flow between business partners. By defining uniform segments and elements that describe the information in the electronic file and which are used for a wide variety of document types (such as invoices, purchase orders, delivery notes, etc.) merely by means of a differentiated arrangement, a worldwide standard was created.

However, since the EDIFACT standard was very comprehensive and created for almost every business transaction and every industry, subgroups (the so-called subsets) soon emerged. The subset EANCOM was created for the retail sector, which contains the mandatory fields of the EDIFACT standard and the industry-specific optional fields. By creating so-called subsets, the messages are better handled and easier to understand. The following table provides an overview of the EDIFACT messages.

Figure 1: EDIFACT Messages
EDIFACT messages
DELFORdelivery forecast
DELJITdelivery Just-in-Time
DESADVdespatch advice message
IFTMINinstructions of transport
IFTMBFtransport booking request
IFTMBCtransport booking confirmation
INVOICinvoice message
ORDERSpurchase order message
PAYORDpayment order message
PRICATprice catalogue message
PRODATproduct data message
INVRPTinventory report
RECADVreceipt advice
MSCONSMetered Services CONsumption report message
UTILMDUTILities Master Data message

 

Structure of an EDIFACT message

Like any language, the EDIFACT rules are based on a character set to be used, the vocabulary (data elements) and grammar (syntax).

Based on the data elements, data element groups / segments of the syntax and the guidelines for the development of message types, globally applicable uniform messages are created. The syntax contains rules according to which the messages exchanged between the communication partners can be structured uniformly, i.e. equally well understandable for all participants, regardless of the hardware and software used. In addition, the syntax allows the user to optimise the transfer files so that only the content actually required is transferred.

The segments and data elements are variable in length. Unlike fixed-length data records, their contents do not have to be filled with blanks or zeros. Only the segments, data element groups and data elements for which content exists in the current message are transferred. This leads to significant savings in data transmission overhead.

Figure 2: UN/EDIFACT Syntax/ISO 9735
UN/EDIFACT syntax/ISO 9735
ElementsSegmentsMessages

United Nations trade data in the business directory

For example:
Date, time, unit of measure, quantity, city, street (on... 35)
variable field length

Functional grouping of data elements
  • Mandatory/can elements
  • Syntax rules
For example:
NAD = name & address
= variable segment length
Grouping of segments to describe business processes
  • Mandatory/can elements
  • Syntax rules
For example:
Invoice, order

 

The EDIFACT syntax

The EDIFACT Syntax defines the following facts:

A) Usable character sets

Two character sets are currently defined to display the message contents:

  • Typ A: printable characters only
  • Typ B: printable characters and all characters of the 7- and 8-bit code permitted in data communication.

 

B) Data elements

This is the basic module that represents information, e.g. the article number. A data element is comparable to a data field. The data elements are always in a defined sequence within a segment. They can be identified in the segment by their position.

 

C) Segments

This is a summary of logically related data elements. It is comparable to a data set. The segments within a message are always in the sequence defined in the message structure diagram.

Figure 3: EDIFACT segments
EDIFACT segments
NADName and address
Description:

To specify the name, address and function of a partner, either as a code only by C082 or (if necessary also additionally) unstructured by C058 or structured by C080 to 3207

3035

Participant, qualifier

Man..3BY = purchaser
DP = delivery address
C082Identification of the participantK  
3039Identification of the participantMan..17 
1131Code list, qualifierKan..3 
3055Responsible for code maintenanceKan..3 
C058Name and addressK  
3124#1Line for name and addressMan..35 
3124#2Line for name and addressKan..35 
C080Name of the participantK  
3036Name (1-5)Man..35 
3042StreetKan..35 
3164CityKan..35 
3251ZIP codeKan..9 
3207CountryKan..3 

 

D) News

The message is a summary of all EDIFACT segments that are required to represent a business transaction, such as an invoice. The message is identified by the specifications in the message header segment (UNH). It is closed with the message end segment (UNT). Only those segments whose data elements contain content are transferred. Segments for which no information is available are omitted completely.

The EDIFACT message name "ORDERS D96 A" indicates:

An order is "ORDERS"

The letter "D" stands for draft

"96" is the year on which a change was made to this message, and

"A" means in the first half of 1996

A message group is a group of messages of the same message type, for example, several delivery notes, for the same recipient.

Since each message is identified by the message reference number, the sequence of messages within the message group is arbitrary. The message group is identified by the specifications in the header segment UNG. The end of a message group is described with the end segment UNE.

 

E) Transmission file

This is a summary of messages or message groups. The transfer file is sent directly to a recipient or forwarded to several recipients via a clearing center. Since each message group is unique due to sender and recipient information and the message reference number, the sequence of the message group within the transfer file can be arbitrary. It is identified by the specifications in the user data header segment (UNB) and ends with the user data end segment (UNZ). The transmission file of an EDIFACT message looks like this:

Figure 4: EDIFACT format using the example of an invoice
The following is an example of an invoice in EDIFACT format:
UNB+UNOA:1+01010000253001+O0013000093SCHA-Z59+991006:1902+PAYO0012101221'
UNH+1+INVOIC:D:97A:UN'
BGM+381+1060113800026+9'
DTM+137:199910060000:102'
NAD+BT+VAUXHALL MOTORS LTD::91'
RFF+VA:382324067'
NAD+SU+2002993::92'
RFF+VA:123844750'
CUX+2:EUR'
PAT+1'
DTM+140:19991031:102'
LIN+++090346642:IN'
QTY+12:54:PCE'
MOA+203:1960.29'
PRI+AAA:3630.1724::NTP:100:C62'
RFF+SI:165480'
DTM+11:199909280000:102'
RFF+ON:X18V00003'
RFF+TN:AB1'
TAX+7+VAT+++:::0'
NAD+ST+023::92'
UNS+S'
MOA+77:1960.29'
TAX+7+VAT'
UNT+24+1'
UNZ+1+PAYO0012101221'

The basic structure of an EDIFACT message is always the same and consists of certain frame segments:

UNA segment (optional): here you can rename separators and special characters
UNB segment: file header; forms the envelope with the UNZ, which contains general information
UNG segment: group start; messages can be combined into message groups
UNH segment: message header; this is where the actual message is located
UNT segment: end of message
UNE segment: group end
UNZ segment: end of file
Structure of an EDIFACT message

 

Figure 5: Structure of an EDIFACT message

 

More about EDIFACT and the SEEBURGER EDI/EDIFACT solutions

Download brochure: 5 Principles For Your EDI Success

Download brochure: Experience the SEEBURGER Difference

What is EDI?

 

Further articles

Industry-Specific B2B/EDI Solutions

SEEBURGER Cloud Services

Use the advantages of EDIFACT also in your company!

Contact us for a product presentation.

Contact Us