EANCOM® 2002 S4, Edition 2008 | Part I | Part I OVERVIEW

1. OVERVIEW

1.1 Introduction

The GS1 EANCOM® standard is an implementation guideline on the use of subsets of selected UN/EDIFACT messages. It specifies in detail the use of the relevant components of these UN/EDIFACT messages in order to support their electronic exchange between trading partner application systems flows.

This document is the manual for the EANCOM® syntax version 4, 2002, Edition 2008 release. It is based on UN/EDIFACT directory D.01B,syntax version 4 which was released by UN/CEFACT in 2001.

This EANCOM® syntax version 4 manual should be perceived as an enhancement of the EANCOM® syntax version 3, 2002 release manual. The new syntax version 4 features, covering EANCOM® requirements such as digital signature, are further detailed in paragraph 1.4 and specific paragraphs of chapter 5.

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

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

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

1.2 GS1 System

The GS1 System is an integral part of the way business is conducted world-wide. It is a global multi-industry system of supply chain solutions that provides for the identification and communication of products, services and locations based on internationally accepted and business-led open standards for the benefit of the users involved.

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 and services), logistic units, assets, locations, service relationships , and other special applications.

> * Standard bar code formats to allow the automatic and secure capture of the standard identification.

> * Standard supplementary codes to encode variable data (in a bar code), in addition to identification.

> * Standard format for trade, transport and finance transactions exchanged between computer-to-computer applications.

1.3.1. Bar Coding Standards

GS1 specifies standards for data carriers (bar codes). Four bar code symbologies are part of the GS1 System:

> 1. EAN/UPC family of bar code symbols. They must be used for all items that are scanned at the Point-of-Sale.
> 2. Interleaved 2-of-5 (ITF-14). They carry ID numbers only on trade items that are not expected to pass through the Point-of-Sale.
> 3. GS1-128 (a subset of Code 128 which, throughout the use of GS1 Application Identifiers, is capable of encoding all GS1 identification numbers and supplementary codes).
> 4. GS1 DataBar and Composite Symbologies offer enhanced possibilities to print more information on barcodes of smaller dimensions.

1.3.2 eCom (EDI) Standards

Many GS1 Member Organisations have been approached and entrusted by their member companies to develop a standard communication system, including telecommunication facilities, allowing commercial documents such as purchase orders, delivery instructions, invoices, and product information to be sent via Electronic Data Interchange (EDI) to their trading partners.

The GS1 International eCom standard, EANCOM®, came about as a result of EDI developments among the GS1 Member Organisations. In 1987 at the GS1 General Assembly, the decision was taken that an international EDI standard based on UN/EDIFACT should be developed. GS1's international eCom standard, EANCOM®, has been in existence since 1990. This release, the EANCOM® syntax 3 and 4, 2002, Edition 2008, constitutes the new EANCOM® standard.

Since EANCOM® deals with the trade of goods, safeguards must be provided to protect trading partner relations and most importantly, the data exchanged. GS1 has developed a guide on how to secure EANCOM® messages to highlight some possible safeguards available within the UN/EDIFACT standard. It describes EANCOM® application functionalities to secure - digital signature - electronic transactions based on UN/ EDIFACT messages.

1.4 Syntax version 4 Specific Features

Need

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.

Syntax rules

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 is 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 are 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/ message when it is not otherwise possible to ensure unambiguous identification of each message segment upon receipt.

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

D.01B messages using features specific to syntax version 4

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.

Security rules and messages

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

From a user point of view there may be four reasons why the implementation of the EANCOM® syntax version 4, 2002, Edition 2008 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.

© Copyright GS1 2008 |  | 2008-10-01