EANCOM® 2002 S4 Edition 2016 Part II
GENRAL General purpose message
4. Segments Description
 
General Message Heading Section
UNH - M 1 - Message header
This segment is used to head, identify and specify a message.
 
BGM - M 1 - Beginning of message
This segment is used to indicate the type and function of a message and to transmit the identifying number.
 
DTM - C 1 - Date/time/period
This segment is used to specify the date of the General message.
 
SG1 - C 10 - RFF-DTM
A group of segments giving references where necessary, their dates relating to the whole message, e.g. despatch advice, contract number.
 
RFF - M 1 - Reference
This segment is used to specify references which relate to the, for example, Purchase Order Numbers.
 
DTM - C 10 - Date/time/period
This segment is used to specify dates relating to the references given in the previous RFF segment.
 
SG2 - C 2 - NAD-SG3-SG4
A group of segments identifying names, addresses and locations, and referred documents relevant for the whole Genral message.
 
NAD - M 1 - Name and address
This segment is used to identify the trading parties involved in the general message. Identification of the sender and receiver of the general message is mandatory.
 
SG3 - C 10 - RFF-DTM
A group of segments giving references only relevant to the specified party rather than to the whole message.
 
RFF - M 1 - Reference
This segment is used to specify reference numbers related to the party identified in the previous NAD segment, e.g., Vat Registration Numbers.
 
DTM - C 10 - Date/time/period
This segment is used to specify dates relating to the references given in the previous RFF segment.
 
SG4 - C 5 - CTA-COM
A group of segments giving contacts details of the specific person or department within the party identified in the NAD segment.
 
CTA - M 1 - Contact information
This segment may be used to identify the department and/or person within the party specified in the NAD.
 
COM - C 9 - Communication contact
This segment is used to identify the communications number and the type of communications used for the person or department identified in the CTA segment.
 
General Message Detail Section
SG5 - C 100 - FTX-SG6
A group of segments enabling the specification of the text and optionally, the identification of other parties or location to whom the information should be directed.
 
FTX - M 1 - Free text
This segment is used to provide free text or coded information. The detail section of the general message is formed by a repeating group of segments always starting with the FTX segment. Each FTX segment corresponds to different textual information.
 
SG6 - C 100 - NAD-SG7-SG8
A group of segments allowing the specification of the name and address of a party, within the receiving party identified in the heading section, to whom the preceding text should be distributed. It also allows to specify the name and address of a party advised as copyreader of this text.
 
NAD - M 1 - Name and address
This segment is used to identify any parties who must be notified on the content of the message contained in the previous FTX segment.
 
SG7 - C 10 - RFF-DTM
A group of segments giving references only relevant to the specified party rather than the whole message.
 
RFF - M 1 - Reference
This segment is used to specify any references relevant to the party identified in the previous NAD segment.
 
DTM - C 10 - Date/time/period
This segment is used to specify any dates related to the references provided in the previous RFF segment.
 
SG8 - C 5 - CTA-COM
A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.
 
CTA - M 1 - Contact information
This segment is used to identify the department and/or person within the party specified in the NAD.
 
COM - C 5 - Communication contact
This segment is used to identify the communications number and the type of communications used for the person or department identified in the CTA segment.
 
General Message Summary Section
UNT - M 1 - Message trailer
This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message.
 
 
© Copyright GS1 Edition 2016