Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Fact or not: Is EDI here to stay?

1,348 views

Published on

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 will try to give you an answer on this question and guide you through the world of EDI explaining the basic principles.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Fact or not: Is EDI here to stay?

  1. 1. Sponsored & Brought to you by Fact or not: Is EDI here to stay? Glenn Colpaert http://twitter.com/GlennColpaert https://www.linkedin.com/in/glenncolpaert
  2. 2. Fact or not: is EDI here to stay?
  3. 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. 4
  5. 5. EDI Electronic Data Interchange 6
  6. 6. 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
  7. 7. History 101 8
  8. 8. 9 1960’s ➔ First electronic data ➔ TDCC formed
  9. 9. 1975 ➔ First EDI Standard Published ➔ Edward Guildert aka Father of EDI ➔ FirstVAN established 10
  10. 10. ➔ WW ➔ WW 11 UN/EDIFACT 1981 1985 ➔ WWTRADACOM 1982
  11. 11. 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
  12. 12. Today 13
  13. 13. 14
  14. 14. How about the standards? 15
  15. 15. Tradacoms ➔ Introduced in 1982 ➔ Subset of EDIFACT ➔ Obsolete in favor of EDIFACT since 1995 ➔ But still used in UK 16
  16. 16. X12 ➔ ANSI ➔ Mainly used in the US ➔ Transactions are identified by Numbers ➔ 810 - Invoice ➔ 850 – Purchase Order ➔ 858 – Shipment Information 17
  17. 17. EDIFACT ➔ UN rules for EDI ➔ Internationally agreed standard ➔ Europe & Asia ➔ Transactions are identified by messages ➔ ORDERS ➔ INVOIC ➔ DESADV 18
  18. 18. 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
  19. 19. 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
  20. 20. How to read EDI 21
  21. 21. 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
  22. 22. DEMO Invoicing via Codit Integration Cloud 23
  23. 23. Codit Integration Cloud Integration as a Service Windows Azure based Business Dashboard Remove Complexity Internet of things Integration Patterns Hybrid Connectivity Business Monitoring
  24. 24. 25 Invoice Approval Demo
  25. 25. DEMO Invoicing via Codit Integration Cloud 26
  26. 26. Why EDI will continue to matter...
  27. 27. 28 MATURITY
  28. 28. 29 MULTIPLE INDUSTRIES
  29. 29. 30 AFFORDABILITY
  30. 30. 31 MULTIPLE NETWORKS
  31. 31. 32
  32. 32. #QUESTIONS #DICUSSION
  33. 33. 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

×