|
GS1 eCom provides global standards for electronic business messaging that allow
rapid, efficient and accurate automatic electronic transmission of agreed business
data between trading partners.
GS1 eCom provides two complementary standards for business messaging:
●
GS1 XML
● GS1 EANCOM
●
Frequently Asked Questions (FAQ)
Quick Links
GS1 XML Technical User Guide to Release 2.0
Updates to EANCOM 2002
Digital Signatures for EANCOM messages
I.
GS1 XML
Overview
XML is an acronym for "eXtensible Markup Language". XML is designed for information
exchange over the internet. Within GS1 set of standards, XML is used for Electronic
Data Interchange - GS1 eCom.
The
GS1 XML standards are not meant to compete or replace GS1
EANCOM - the GS1 standard for "traditional" EDI. GS1 XML standards
initially addressed different user groups than the existing EANCOM standards, but
currently both technologies are being used in parallel.
The GS1 XML standards provide a set of XML schemas which can be used to create XML
instance documents and validate them during the business information exchange. These
documents are business messages equivalent to paper business documents.
The GS1 XML schemas have been developed based on UML models of business processes.
This practice ensures that the business message models are syntax neutral and based
on real business processes. These models can be mapped to any technical syntax that
allows actual business data exchange. This makes them future-proof and can be mapped
to any syntax or data exchange technology to come.
GS1 XML 2.0.2 Reader
●
Download
GS1 XML 2.0.2 Reader
The GS1 XML 2.0.2 Reader is a free of charge tool,
making it easier for the users to understand the structure of the suite of schemas,
relationship between them, etc. It provides a map of the schemas, helping users
to decide which implementers Packets they need to download and what do they contain.
The XML messages are represented in a tree structure view.
The user companies that are evaluating the GS1 set of Business Message Standards
can use the GS1 XML Reader is an easy to use and clearly arranged means of information
on the content and the structure of the standards. The GS1 XML Reader helps to get
a more precise picture of what is necessary to implement for a given business processes.
The tool has been developed in cooperation with GEFEG, a German solution provider
company.
Implementation
Use the links below to help you implement GS1 XML:
●
GS1 XML Technical User Guide to Release 2.0
●
UN/CEFACT Standard Business Document Header Technical
Specification Version 1.3
● Electronic Business in the GS1 Community in 2004
II.
GS1 EANCOM
GS1 EANCOM provides a standardised and predictable structure for electronic business
messages, enabling business partners to communicate business data rapidly, efficiently
and accurately, irrespective of their internal hardware or software types.
This section of the website gives you the change to view the GS1 EANCOM message types
and gives you assistance in their implementation.
Overview
EANCOM is fully based on the UN/EDIFACT (United Nations Electronic Data Interchange
for Administration, Commerce and Transport), which comprises a set of internationally
agreed standards, directories and guidelines for the electronic interchange of data.
EANCOM is a detailed implementation guideline of the UN/EDIFACT standard messages.
UN/EDIFACT messages are often complex and users may easily misunderstand the principles
and original intentions of message's designers. EANCOM guideline is a subset of
UN/EDIFACT messages, providing clear definitions, explanations and examples which
allow trading partners to exchange commercial documents in a simple, accurate and
cost effective manner.
EANCOM also incorporates into the electronic messages, the GS1 standards of physical
identification of trade items, logistics units and the Global Location Numbers identifying
the trading partners. It allows to integrate the physical flow of goods with related
information sent by electronic means.
Technical
The messages available in the EANCOM standard cover the functions required to effect
a complete trade transaction:
-
the messages which enable
the trade transaction to take place, e.g. price catalogue, purchase order, invoice,
etc;
-
the messages used to instruct
transport services to move the goods;
-
the messages used in settlement
of the trade transactions through the banking system.
The flows and trading partners catered for in EANCOM can be simply represented as
follows:
The business messages available in EANCOM can be divided into the following categories:
Master Data Messages
These contain data which rarely changes (product measurements, names and addresses,
etc):
-
The
Party Information message:
is used to identify all the locations
name, address, contact persons, financial accounts, etc) associated to subsequent
commercial transactions and their related operational information.
-
The
Product Information messages:
provide parties with information containing the descriptive, logistical and financial
details of a product or a service.
Business Transactions
Messages
These cover the general trading cycle from quotation request to remittance advice:
-
Quotation messages contain all details relevant
to the supply of the goods or services requested by the potential buyer (terms of
delivery, payment terms, price, allowances and charges, etc).
-
Purchase
Order set of messages
relates to the ordering process from a proposed order, subsequent changes and the
eventual order confirmation (relevant quantities, dates, location of delivery, etc).
-
Transport
and Logistics messages
provide information related to the dispatch transport and receipt of previously
ordered products.
-
Invoice
and Remittance Advice
messages relate to the payment of the goods supplied. The buyer can automatically
reconcile the suppliers invoice using the product receipt information.
Report and Planning
Messages
These messages include general trading reports which allow partners to plan for
the future:
● They enable trading partners
to exchange precious information in order to understand each others requirements.
● They provide valuable and up-to-date reports
and forecasts concerning delivery, sales and stocks and enable the partners involved
to plan their activities and marketing strategies.
Syntax and Service
Report Message
The Syntax and Service Report message may be sent by the receiver of any EDIFACT
message to acknowledge or refuse an interchange, functional group or message.
General Message
The General message may be used to send data for which there is no specific standard
message.
Security Messages
These messages are only available in the EANCOM version 2002, Syntax 4.
● The secure authentication and acknowledgement
message is used in order to transmit the digital signature, related information
to verify the signature by the recipient, and the references to the data secured.
The security key and certificate management
message can be used to transmit the public key of the sender
to the recipient. The recipient is then able to verify digital signatures in further
transmissions. It is also possible to make references to certificates from certification
authorities (trust centres).
Implementation
The following resources are available to help you implement EANCOM.
Updates to EANCOM
2002
In the EANCOM 2002 , many updates have been made to the User Manual. To help you
to navigate through these changes a series of short documents have been provided
as supplementary information to the manual. They are intended to ease any migration
issues that may arise when changing from EANCOM 97 (based on UN/EDIFACT D.96A) to
EANCOM 2002 (based on UN/EDIFACT D.01B).
Summary of
Accepted Change Requests (Update 05)
EANCOM Change Request
Forms
How to submit an
EANCOM Change Request
Step 0
Before doing anything on GSMP CR System, check with your local MO or, in case of
an MO, with the EANCOM TDT TO for a peer review in order to avoid spending time
on CRs which are:
-
submitted incorrectly
-
not required
-
already resolved using another solution
This will save time for the submitter and TDT members.
Step 1
Create a record in the GSMP CR System at http://www1.ean-ucc.org/change_request/index.cfm
Step 2
Attach one of the following documents depending of the type of CR:
Describe your business case, your business needs and the proposed solution in as
much relevant detail as possible.
Make sure you mention:
-
EANCOM message
-
Relevant Directory
-
Segment and Segment Group (if it exists)
-
Data Element or Composite
Step 3
As soon as your CR has been created, EANCOM TDT will assign one of its member to
make the Initial Technical Assessment (ITA) using the document INITIAL TECHNICAL
ASSESSMENT.doc, also located at http://eroom.uc-council.org/eRoom/facility/EANCOM/0_a15c
Step 4
Based on the ITA, EANCOM TDT will approve (or not) the proposed solution. If the
CR is not approved then an EANCOM TDT solution could be offered to the submitter.
Once an agreed solution between the submitter and the TDT has been reached, then
the CR can be forwarded to ITRG for eBallot.
III.
FAQ
●
Frequently Asked Questions
|
