EANCOM PART III: DATA ELEMENT & CODE SETS DIRECTORY

 

1. Introduction

2. Index by data element name

3. Index by data element tag


 

1. Introduction

The Data Elements and Code Sets Directory contains a list of all data elements which appear in segments in the EANCOM 1997 messages and in the new messages published in July 1998 and July 1999. 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.

The majority of the code values in the EANCOM 1997 code sets are taken directly from the EDIFACT D.96A directory which was published in March 1996.

Additionally some code values which are EANCOM specific are also included in the code sets. These codes are not part of the EDIFACT directory and have been allocated temporary code values in advance of EDIFACT code values being made available (see also 2 below).

The temporary code values are easily recognisable by the '(EAN Code)', '(EAN/UCC Code)', or ‘(SWIFT Code)’ message immediately following the code. Additionally several EAN codes are further identified as being book industry code values in the following way, '(EAN Code - book)'.

All temporary code values contained in this release of the code sets will be forwarded to 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 publication of the last codelist in July 1998. These codes have been added either as a result of successful change requests or following their publication in one of the new messages included 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.

The EANCOM codes set will be issued on an yearly basis and will contain all codes agreed for addition as a result of accepted change requests. Any user requiring additional code values not currently contained in the EANCOM code sets should address their needs to their local numbering organisation via the change requests procedure (See Part I, Section 3.4).

Accepted change requests for additional code values may be implemented bi-laterally among trading partners before they appear in the EANCOM code sets.

  

(c) Copyright EAN 1999