Transcript Electronic Data Interchange

Jeremy Morton
GS1 Sweden
Agenda
 GS1
 EDI changes the way you do business
 EDI – it’s been around for ages
 EDIFACT Syntax
 Messages, transactions, processes, scenarios
 GS1’s role and deliverables
 Where are we heading?
2009-03-24
EDI/BizTalk
2
GS who?
1970 – UCC – Uniform code council
 North America
1975 – EAN – European article numbering
 Europe
 Many names – CCG, ANA, AECOC, INDICOD, …
1980 – EAN International
 Global
 Even more names – Uniscan, HKAna, SANC,
2000 – EAN + UCC = EAN.UCC
 Two cultures
 Two systems
 Two boards
2005 – GS1
 “One world; One name; One global language of business”
 > 100+ countries; > 1500+ staff; > 1.3 million registered users
The GS1System
GTIN
4 512345 678906 >
EAN13
Article number
1
31234
56789
4
ITF14
GLN
Databar
Location number
SSCC
89
Package number
( 01) 04601234567893
EAN128
GRAI
GPC
RTI number
Product
classification
GIAI
EAN8
GS1
system
Asset identifier
GSRN
< 3456 9870 >
Electronic commerce
Relation number
EANCOM
XML
RFID/EPC
A typical business situation
Order Processing
Order
Stock
Control
Confirmation
Production
Delivery
Invoicing
Payment
Credit
What EDI wants to achieve
Order Processing
Order
Order Response
Stock
Control
Production
Delivery
Payment
Credit
Customer
Supplier
Business relationship
Business transactions
Information
EDI
Components of e-business
 Business relationship
 Based on personal contact
 Expressed as an agreement (prices, delivery terms)
 Business transactions
 Order, Invoice, Price list, etc.
 Information
 By mail, fax, telephone, …
Scenarios
Business transactions rarely come alone







a payment refers to
an invoice which refers to
a delivery advice which refers to
an order confirmation which refers to
an order which refers to
a price list which .....
The same information is involved from ”cradle to grave”
Supplier
Buyer
Pricelist
Calloff
Confirmation
Despatch advice
Invoice
Payment
10
Supplier
Pricelist
Buyer
Order-specific
Custom items
Critical for reconciliation
Pull or push
Linked to product data
11
Supplier
Calloff
Buyer
Starts the supply process
Unambiguous item numbers
Unambiguous locations
Unambiguous quantities
Agreed prices
12
Supplier
Confirmation
Buyer
Yes/No/Maybe
What
When
How many
Substitution
13
Supplier
Despatch advice
Buyer
What
When
Where
How many
Package identification
Transport information
14
Supplier
Invoice
Buyer
Simple
Correct
Timely
15
Supplier
Payment
Buyer
Simple
Correct
Timely
16
Supplier
Business
Application
EDI system
Communication
Messaging
Network
Buyer
17
Goals
 of EDI
 To get essential data into your business partner’s
computer system without manual intervention
 of e-Business
 To improve and simplify a business relationship using
EDI
EDI – as old as computers
Proprietary (US)
ANSI X.12
EDIFACT
UN/EDIFACT
GTDI
Proprietary
(Europe)
1960’s
2009-03-24
1970’s
EDI/BizTalk
1987
19
EDI syntax – what really happened
Proprietary
(US)
ANSI X.12
EDIFACT
GTDI
UN/CEFACT
UN/EDIFACT
XML/EDI
Proprietary
(Europe)
TRADACOMS
(UK)
2009-03-24
EDI/BizTalk
20
Goal of EDI
 To get structured data
 from the sender’s system

2009-03-24
to the receiver’s system
 Timely
 Reliably
 Unambiguously
EDI/BizTalk
21
Structured data - 1
“Line number”, “Item number”, “Quantity”
1, 1234, 99
2, 5678, 50
…
All records the same
2009-03-24
EDI/BizTalk
22
Structured data - 2
HEAD
ONUM
DATE
LINE
ITEM
QUAN
LINE
ITEM
QUAN
DONE
2009-03-24
ABC123
090324
1
1234
99
2
5678
50
This method was used
extensively in early EDI.
It is flexible, but takes a lot of
space (2400 bits/s was fast in
those days!)
EDI/BizTalk
23
Structured data - 3
<purchaseOrder>
<header>
<orderNumber>ABC123</orderNumber>
<orderDate>090324</orderDate>
</header>
<line>
<lineNumber>1</lineNumber>
<itemNumber>1234</itemNumber>
<quantity>99</quantity>
</line>
<line>
<lineNumber>2</lineNumber>
<itemNumber>5678</itemNumber>
<quantity>50</quantity>
</line>
</purchaseOrder>
2009-03-24
EDI/BizTalk
This is where we are heading.
It is flexible, but takes even
more space (1 Mbit/s is slow
today)
24
Structured data - 4
The EDIFACT (and X.12)
compromise
BGM+220+ABC123’
DTM+4:20090324:102’
LIN+1++1234:MF’
QTY+21:99’
LIN+2++5678:MF’
QTY+21:50’
2009-03-24
EDI/BizTalk
•
•
Flexible and compact
But unreadable!
25
EDIFACT syntax (simplified)
BGM+220+ABC123’
DTM+4:20090324:102’
LIN+1++1234:MF’
QTY+21:99’
LIN+2++5678:MF’
QTY+21:50’
A segment
A simple data element
A composite data element
A component data element
Segment tag
Separators
CODES
2009-03-24
EDI/BizTalk
26
EDIFACT messages
UNH+9876+ORDERS:D:97A:UN:EAN007’
BGM+220+ABC123’
DTM+4:20090324:102’
LIN+1++1234:MF’
QTY+21:99’
LIN+2++5678:MF’
QTY+21:50’
Header
segment
Trailer
segment
UNT+8+9876’
2009-03-24
EDI/BizTalk
27
EDIFACT messages
UNH+9876+ORDERS:D:97A:UN:EAN007’
Message Message
number type
Catalogue UNSM
ID
Implementation
subset
First there was INVOIC
Today there are dozens of UNSMs
They are too complicated to use directly
So subsets are used
2009-03-24
EDI/BizTalk
28
EDIFACT interchanges
UNB+UNOC:3+FROMME+TOYOU+090324:1200+REF123’
UNH+9876+ORDERS:D:97A:UN:EAN007’
…
UNT+8+9876’
UNZ+1+REF123’
Interchange
header
Interchange
trailer
2009-03-24
EDI/BizTalk
29
EDIFACT syntax summary
An Interchange consists of one or more
Messages which are made up of
Segments with
a Tag and one or more
Simple data elements or
Composite data elements with
Component data elements
all kept in place with Separators
and full of Codes
2009-03-24
EDI/BizTalk
30
The Tower of Babel
 EDIFACT
 One language ...
 ... Many dialects
 UN/EDIFACT
 One standard ...
 ... Many interpretations
GS1’s role
For e-Business to work we need to agree
 Scenarios
 Transactions
 Information
 Semantics
 Documents
 Communication
…
GS1’s role
GS1 has developed
 Standard identifiers (items, places, shipments, …)
 Standard scenarios (FMCG, Public procurement, …)
 Standard semantics (Global Data Dictionary)
 Standard EDIFACT subset (EANCOM)
 Standard XML messages
…
Plug-and-pray
So what’s the hold-up?
 EDI standards work between actors
 But for e-Business to work, the data and processes have
to be well-organized inside the firewall
 That’s where integration software helps
2009-03-24
EDI/BizTalk
34
Conclusion
 EDI is a comparatively simple IT exercise
 it gets rid of paper and makes the information flow more
efficient
 e-Business is a management technique that still really
has not caught on
 but only e-Business will bring dividends
A few links
Me: [email protected]
GS1 Sweden: http://www.gs1.se
Implementation guides (in Swedish):
http://www.gs1.se/sv/Elektronisk-handel/Affarsprocesser/
GS1 International: http://www.gs1.org
EANCOM: http://www.gs1.org/productssolutions/ecom/eancom/
UN/CEFACT: http://www.unece.org/cefact/
GEFEG: http://www.gefeg.com/en/index.htm
2009-03-24
EDI/BizTalk
36