GS1 EANCOM
The messages available in the EANCOM standard support all aspects of a trade transaction and they include:
- the messages which enable each step in trading, eg price catalogues, purchase orders, invoices
- the messages used to instruct transport services for the moving of goods;
- the messages used in settlement of transactions through the banking system.
Data Messages
The messages available in GS1 EANCOM can be divided into the following categories:
Master data messages
These contain data which rarely changes (product measurements, names and addresses, etc).
A party information message is used to identify
the location, address, contact persons, financial accounts and other
information associated with commercial transactions and their related
operational information.
A product information message provides parties with information on the descriptive, logistical and financial details of a product or a service.
Business transactions messages
These cover the trading cycle from quotation request to remittance advice:
- Quotation messages contain all details relevant to the supply of products or services as requested by a buyer (terms of delivery, payment terms, price, allowances and charges etc).
- Purchase order messages relate to the ordering process from a proposed order until its confirmation (relevant quantities, dates, location of delivery, etc).
- Transport and logistics messages provide information related to the despatch, transport and receipt of , products.
- Invoice and remittance advice messages relate to payment for goods. The buyer can automatically reconcile the supplier’s invoice using the product receipt information.
Report and planning messages
These messages include trading reports which allow partners to plan for the future:
- They enable trading partners to exchange precious information and to understand each others’ requirements.
- They provide valuable and up-to-date reports and forecasts concerning delivery, sales and stocks, and they enable partners to plan their activities and marketing strategies
Syntax and service report messages
These messages may be sent by the receivers of an EDIFACT message to acknowledge or refuse an interchange, functional group or other form of message.
General messages
General messages 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.
- EANCOM 2002 – User Manual
To receive the User Manual, contact Steve Rowland on tel. 64 9 525 8444 or steve.rowland@gs1nz.org - Digital Signatures for EANCOM messages
- How to submit an EANCOM change request
eCom Standards survey reports
- eCom Standards in the GS1 community 2006
- eCom Standards in the GS1 community 2005
- Electronic business in the GS1 community in 2004
Updates to EANCOM 2002
In EANCOM 2002, many updates have been made to the User Manual. To help 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).
EANCOM Change Request Forms
- Code change request (COCHRE)
- General change request (GENERE)
- Message structure change request (MSCHRE)
- New code request (NECORE)
- Segment change request (SECHRE)
How to submit an EANCOM change request
Step 1
Before doing anything on GSMP CR System, check with GS1 New Zealand, 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 2
Create a record in the GSMP CR system at http://www1.ean-ucc.org/change_request/index.cfm
Step 3
Attach one of the following documents depending of the type of CR:
- GSMP_COCHRE.doc for a code change request
- GSMP_NECORE.doc for a new code request
- GSMP_SECHRE.doc for a segment change request
- GSMP_MSCHRE.doc for a message structure change request
- GSMP_GENERE.doc for a general change request
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 these exist)
- Data element or composite
Step 4
As soon as your CR has been created, EANCOM TDT will assign one of its members 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 5
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.
Support
For support, contact Merv Horsford on +64 9 820 3784 or email merv.horsford@gs1nz.org








