1.1 Introduction

The GS1 EANCOM® standard is a subset of selected UN/EDIFACT messages, based on UN/EDIFACT directory D.01B, syntax version 3 which was released by UN/CEFACT in 2001. It includes only components that are mandatory and those relevant for the GS1 user community.

This document is the manual for the GS1 EANCOM® 2002 syntax version 3. It is an implementation guideline containing detailed descriptions of the use of the messages and their components to support their electronic exchange between trading partner applications, as well as usage examples and sample data.

This manual is developed by GS1 and represents an integral part of the suite of GS1 supply chain solutions. In this context, the GS1 EANCOM® manual should be read in conjunction with the "GS1 General Specifications" manual which describes the GS1 Identification and Bar Code standards.

It is important to note that the GS1 EANCOM® 2002 syntax versions 3 and 4, replaces the GS1 EANCOM® 1997 syntax version 3, release which was based on UN/EDIFACT directory D.96A. Therefore, at the time of publication of this manual, the GS1 EANCOM® 2002 syntax versions 3 and 4, becomes the GS1 EANCOM® standard.

In terms of future maintenance and processing of new user requirements, work requests will be processed only against GS1 EANCOM® 2002 syntax versions 3 and 4.

1.2 GS1 System

The GS1 System is an integrated system of global standards that provides for accurate identification and communication of information regarding products, assets, services and locations. It is the most implemented supply chain standards system in the world. It is the foundation of a wide range of efficiency-building supply chain applications and solutions.

The GS1 system is developed and managed by GS1, using the GS1 Global Standards Management Process (GSMP).

1.3 GS1 Standards

The international GS1 Standards include:

- Standard identification of trade items (products or services), logistic units, assets, locations, service relationships, and other special applications, as well as supplementary codes to encode variable data.

- Standard data carriers to allow the automatic and secure capture of the standard identification.

- Global standards for Electronic Data Interchange that allow rapid, efficient and accurate automatic electronic transmission of agreed business data between trading partners.

- Global Data Synchronisation Network™ (GDSN™) is an automated, standards-based, global environment that enables secure and continuous data synchronisation, allowing all partners to have consistent item data in their systems at the same time.

- GS1 EPC Global® is a set of standards that combines RFID (radio frequency identification) technology, existing communications network infrastructure and the Electronic Product Code (a number for uniquely identifying an item) to enable immediate and automatic identification and tracking of an item through the whole supply chain globally, resulting in improved efficiency and visibility of the supply chain.

1.3.1 GS1 EDI Standards

The Electronic Data Interchange (EDI): the interchange of structured data according to agreed message standards, by electronic means.

GS1 currently has three sets of GS1 EDI standards:

- GS1 EANCOM®

- GS1 XML

- GS1 UN/CEFACT XML

All three sets of GS1 EDI standards are implemented in parallel by different users. Although XML is a newer technology than the GS1 EANCOM®, the latter has a large and constantly growing number of users. UN/CEFACT XML is a GS1 profile (subset) of the UN XML standard  it is meant mainly for users exchanging data with government organisations.

GS1 is going to continue supporting all three sets for as long as it is necessary. Any new developments, however (e.g. messages for sectors new to GS1) by default will be done only in GS1 XML. New GS1 EANCOM® developments in new domains will be done only if there is a justified business reason.

The existing GS1 EANCOM® messages will be supported and developed based on the user needs.

1.3.2 GS1 Identification Keys

GS1 has defined 11 Identification Keys and 7 of them are currently relevant in the context of GS1 EDI standards, thus they have been included in GS1 XML and GS1 EANCOM®.

The Keys support the identification of trade items, services, locations, logistic units, assets, shipments, consignments, etc. The GS1 Company Prefix (https://www.gs1.org/company-prefix) assigned to a user company allows that user company to create any of the GS1 identification keys.

- Global Location Number (GLN)

GLN can be used by companies to identify their physical (physical address) or digital (electronic address) locations, legal entities or functions, giving them complete flexibility to identify any type or level of location required.

- Global Trade Item Number (GTIN)

GTIN can be used by a company to uniquely identify all of its trade items. GS1 defines trade items as products or services that are priced, ordered or invoiced at any point in the supply chain.

- Serial Shipping Container Code (SSCC)

SSCC can be used by companies to identify a logistic unit, which can be any combination of trade items packaged together for storage and/ or transport purposes  for example a case, pallet or parcel.

- Global Identification Number for Consignment (GINC)

GINC can be used by companies to identify a consignment comprised of one or more logistic units that are intended to be transported.

-Global Individual Asset Identifier (GIAI)

GIAI is one of the two GS1 Keys for asset identification. Companies can apply a GIAI on any asset to uniquely identify and manage that asset. This could be a computer, desk, vehicle, piece of transport equipment, or spare part, as just a few examples.

-Global Returnable Asset Identifier (GRAI)

GRAI is one of two GS1 Keys for asset identification. This GS1 Key is especially suitable for the management of reusable transport items, transport equipment, or tools and can identify these returnable assets by type and if needed also individually for tracking and sorting purposes.

-Global Shipment Identification Number (GSIN)

GSIN is a number assigned by a seller and shipper of goods to identify a shipment comprised of one or more logistic units that are intended to be delivered together.

More information about the Use of GS1 Identification Keys can be found in the document Use of GS1 keys in GS1 EDI messages Guideline.
www.gs1.org/sites/default/files/docs/EDI/GS1_ID_Keys_in_EDI_messages_Guideline.pdf

1.3.3 Data Carriers

GS1 has an entire portfolio of Data Carriers - media that can encode GS1 ID Keys and attribute data in a machine readable format:

- EAN/UPC

EAN/UPC family of bar codes that are the most widely used GS1 data carriers. They are used to scan trade items at the Point-of-Sale and in logistic applications.

- ITF-14

ITF-14 (Interleaved 2-of-5) bar codes carry ID numbers only on trade items that are not expected to pass through the Point-of-Sale.

- GS1-128

The GS1-128 bar code is a subset of the Code 128 Bar Code Symbology. Its use is exclusively licensed to GS1. This extremely flexible symbology can carry all GS1 Keys and attributes but cannot be used to identify items crossing Point-of-Sale.

- GS1 DataBar

GS1 DataBar family of bar codes that can be scanned at retail point-of-sale (POS), are smaller than EAN/UPC and can carry additional information such as serial numbers, lot numbers of expiry dates. Composite Bar Code integrates both a GS1 System linear symbol and a 2D Composite Component as a single symbology and is approved for special healthcare applications.

- GS1 DataMatrix

GS1 DataMatrix is a "2D Matrix" symbol used for example in healthcare sector. Because GS1 DataMatrix requires camera based scanners it is currently specified for healthcare items not crossing POS and direct part marking. GS1 QR Code is a "2D Matrix" symbol and is approved for Extended Packaging applications using mobile devices for scanning.

- EPC/RFID tags

EPC/RFID tags use Radio-Frequency Identification technology to encode GS1 ID Keys in the GS1 Electronic Product Code (EPC). RFID works via a microchip, which stores the relevant data (including the EPC) and reflects the data to a reader antenna by means of electromagnetic waves. Since these waves can pass through solid materials, the chips may be shielded by adhesive film or integrated directly inside the packaging or product.

More information about the GS1 Data Carriers and GS1 Identification Keys can be found in the GS1 General Specifications - the core document describing how these standards should be used to comply with GS1 System.

1.3.4 GS1 Global Data Synchronisation Network (GDSN)

The Global Data Synchronisation allows exchanging Master Data in an automated manner.

Master Data are fixed attributes of products and parties that never (or hardly ever) change. They need to be aligned between trading partners before any transactional messages, like, Order, Despatch Advice or Invoice are exchanged. In these transactional messages they are referenced by the GS1 Identifications Keys. The Master Data related to them are retrieved from the company's data base via these ID keys.

The Master Data can be exchanged directly between trading partners, but far more efficient way is to use the Global Data Synchronisation Network comprised of:

- Certified Data Pools

Certified Data Pools - interoperable electronic catalogues standardised master data, ensuring the confidentiality and integrity of user information.

- GS1 Global Registry

GS1 Global Registry - acting as the "information directory" identifying where information is held across the network and enabling the uniqueness of the registered items and parties.

User companies (e.g. manufacturers) can publish their Master Data in one of the Data Pools and their trading partners (e.g. retailers) can subscribe to receive notification whenever any of the attributes change or new product descriptions are published. The Data Pools contact the Global Registry to check where the information is stored and synchronise it directly with the Data Pool storing requested information. The relevant subset is then sent to the requesting user.

This infrastructure supporting standards ensure that all participating trading partners have access to most up to date Master Data relevant to them.

1.4.1 Need (Syntax 4 only)

EANCOM® 2002 is published in an additional syntax version 4 as a result of enhancements that have been incorporated in UN/EDIFACT being mainly application level syntax rules. The new features that are used in the present release are summarised below.

1.4.2 Syntax Rules (Syntax 4 only)

The following additions have been made to Syntax 4 that are not available in Syntax 3:

- The coverage of character sets has been extended with the following character set levels: G to K, X and Y.

- Multiple occurrences of stand-alone composite data elements are permitted. To support this capability a new service character ‘*’ has been introduced as "repetition separator". This new feature is only used in the KEYMAN message, in segment USA for the repetition of composite data element S503.

- In the UNA segment, position UNA5 is used for the repetition separator ‘*’.

- A single set of default service characters is defined, independent of the character set level.

- In the UNB segment, the format of data element 0017 has been extended to ‘n8’ in order to conform to year 2000 requirements.

- In the UNG segment, the format of data element 0017 has been extended to ‘n8’ in order to conform to year 2000 requirements. In addition, the status of all simple data elements except 0048 and composite data elements is conditional.

- In the UNH segment, the new data element 0110 permits to specify the version number of the code list directory used.

- The UGH/UGT anti-collision segment group has been added which may be used in a UN/EDIFACT message when it is not otherwise possible to ensure unambiguous identification of each message segment upon receipt.
rules.

-The CONTRL service message, previously developed and published as a separate document, is now part of the syntax rules.

1.4.3 D.01B messages using features specific to syntax version 4 (Syntax 4 only)

In the PAYDUC message, the UGH/UGT segment group anti-collision technique has been used. As such, PAYDUC must use version 4 of the syntax rules.

1.4.4 Security rules and messages (Syntax 4 only)

Two new service messages have been added: AUTACK which applies security services (digital signature) to other UN/EDIFACT structures and KEYMAN which provides a capability of managing security keys and certificates.

1.5 User Perspective (Syntax 4 only)

From a user point of view there may be four reasons why the implementation of the EANCOM® syntax version 4, 2002, release might be taken into consideration:

- Extensive coverage of all written languages of the world,

- Payroll deduction advice message (PAYDUC),

- Explicit identification of the EANCOM® code list version used,

- Digital signature.