Data elements & code sets directory - GS1

EANCOM ® 2002 Part III Data element & Code sets directory
Introduction
The Data Elements and Code Sets Directory contains a list of all data elements which appear in segments in the
EANCOM ® 2002 messages. For coded data elements the appropriate code set is highlighted.
For each data element the following information is provided: Tag, name and description. In addition for all coded
data elements the code values associated with the data element, their names, and descriptions are indicated.
Where necessary, an EANCOM ® note has been added.
The majority of the code values in the EANCOM ® 2002 code sets are taken directly from the UN/EDIFACT D.09B
directory which was published in summer 2009.
Additionally some code values which are EANCOM ® specific are also included in the code sets. These codes are
not part of the UN/EDIFACT directory and have been allocated as temporary code values in advance of EDIFACT
code values being made available.
The temporary code values are easily recognisable by the '(GS1 Code)' or '(SWIFT Code)' message immediately
following the code. The '(SWIFT Code)' codes were included in the codelist with the approval of SWIFT.
Where applicable temporary code values contained in this release of the code sets will be forwarded to
UN/EDIFACT for official code values in due course.
Code values with a '+' sign before the code name are codes which have been added to the code sets since the last
release of the EANCOM ® 1997 code sets in July 1997. These codes have been added either as a result of
successful change requests or following their publication in one of the new messages published in EANCOM ® 1997.
Please note that it may not be possible to use these codes in all messages as restricted code lists apply to some
data elements in some messages. If in doubt please contact your numbering organisation before using codes in a
restricted code list.
Code values with a '@' sign before the code name are codes which have been added to the code sets because
UN/EDIFACT has allocated formal values for previous temporary codes. To the right hand side of the name and
definition of every code marked with the '@' sign, the code value which has been replaced is detailed. These old
code values are provided simply for information purposes to assist users to map previous temporary codes to new
EDIFACT ones. Additionally, the ”@” sign will be used if the code definition, name or tag, or any combination of
these is changed.
Code values with a "++” sign before the code name are codes which have been added to the code sets since the
first publication of EANCOM ® 2002, "@@” shows modification since the first publication.
Code values with a '+++' sign before the code name are codes which have been added to the code sets since the
Ed. 2008 publication of EANCOM ® , '@@@' shows modification since the Ed. 2008 publication.
Code values with a '4+' sign before the code name are codes which have been added to the code sets since the
Ed. 2010 publication of EANCOM ® , '4@' shows modification since the Ed. 2010 publication.
Code values with a 'X' sign before the code name are codes which are marked for deletion and will not exist any
more in the next release of EANCOM ® .
Code values with a '-' sign before the code name are codes which have been deleted in the current release (not
physically).
A number in squared brackets at the beginning of the code name refers to the Trade Data Element Directory
UNTDED.
In the column headed with an ”S” codes which are only used in syntax 3 messages are marked with a ”3”, whereas
codes used in syntax 4 messages are marked with a ”4”. Where neither ”3” or ”4” is marked in the column, the use
of the code value is independant from a specific syntax version.
Any user requiring additional code values not currently contained in the EANCOM ® code sets should address their
needs to their local GS1 member organisation via the change requests procedure (See Part I, Section 3.1.2).
Accepted change requests for additional code values may be implemented bi-laterally among trading partners
before they appear in the EANCOM ® code sets.
© Copyright GS1 - 2 - Edition 2012