EDI is a standard that is typically used in supply chain and logistic for exchanging business data. Although it’s wide usage is it still relevant in this new world of API’s, BIG Data and IOT solutions? In this session Glenn (Codit) will try to give you an answer on this question and guide you through the world of EDI explaining the basic principles.

1. Fact or not: is EDI here to stay?
1

2. Fact or not: is EDI here to stay?

3. Nice to meet you
Glenn COLPAERT
Integration MVP
Integration Consultant @ Codit
AzureAdvisor / Insider
BTUG.be Boardmember
glenn.colpaert@codit.eu
@GlennColpaert
be.linkedin.com/in/glenncolpaert/
blog.codit.eu

4. 4

6. EDI
Electronic Data Interchange
6

7. What?
7
Exchange of
Business Data
e.g. purchase orders, invoices,
shipping notices, ...
Standard data
formats
Standard definition of the
structure is provided
Between Business
Partners
Typically between two
different companies

8. History 101
8

9. 9
1960’s
➔ First electronic data
➔ TDCC formed

10. 1975
➔ First EDI Standard Published
➔ Edward Guildert aka Father of EDI
➔ FirstVAN established
10

11. ➔ WW
➔ WW
11
UN/EDIFACT
1981
1985
➔ WWTRADACOM
1982

12. 1990’s
➔ Early 1990’s about 12,000 businesses are using EDI
➔ EDI is starting to get transmitted over the Internet
12
2001
➔ AS/2 communication standards are published

13. Today
13

14. 14

15. How about the standards?
15

16. Tradacoms
➔ Introduced in 1982
➔ Subset of EDIFACT
➔ Obsolete in favor of EDIFACT since 1995
➔ But still used in UK
16

17. X12
➔ ANSI
➔ Mainly used in the US
➔ Transactions are identified by Numbers
➔ 810 - Invoice
➔ 850 – Purchase Order
➔ 858 – Shipment Information
17

18. EDIFACT
➔ UN rules for EDI
➔ Internationally agreed standard
➔ Europe & Asia
➔ Transactions are identified by messages
➔ ORDERS
➔ INVOIC
➔ DESADV
18

19. Structure
19
• Different EDI-messages (e.g.
INVOIC, ORDERS, …)
• Has multiple segments (e.g.
BGM, DTM, NAD, …)
• Segments can be grouped
and recurrent
• Every message and segment
can be found at
StylusStudio.com/edifact

20. How to read EDI
20
• The first segment ‘UNA’ defines the separators and indicators
UNA:+.? ‘
Default value Element
: Component Data Element Seperator
+ Data Element Seperator
. Decimal Notification
? Release Indicator
<space> Reserved for future use
' Segment Terminator

21. How to read EDI
21

22. Structure
22
• The ‘UNB’ segment elements identify sender, recipient, datetime
UNB+UNOA:3+STYLUSSTUDIO:1+DATADIRECT:1+20051107:1159+6002‘
• The ‘UNH’ segment provides information about the message type
UNH+SSDD1+ORDERS:D:03B:UN:EAN008‘
• Body segments depending on the message type
e.g. BGM, DTM, NAD, …
• Footer segments
e.g. UNT and UNZ

23. DEMO
Invoicing via Codit Integration Cloud
23

24. Codit Integration Cloud
Integration
as a Service
Windows
Azure based
Business
Dashboard
Remove
Complexity
Internet of
things
Integration
Patterns
Hybrid
Connectivity
Business
Monitoring

25. 25
Invoice Approval Demo

26. DEMO
Invoicing via Codit Integration Cloud
26

27. Why EDI will continue to
matter...

28. 28
MATURITY

29. 29
MULTIPLE
INDUSTRIES

30. 30
AFFORDABILITY

31. 31
MULTIPLE
NETWORKS

32. 32

33. #QUESTIONS
#DICUSSION

34. Thank you!
Keep in touch.
Call or mail. Ask questions. Happy to help.
glenn.colpaert@codit.eu
@GlennColpaert
be.linkedin.com/in/glenncolpaert/
blog.codit.eu