fact or not: is edi here to stay? (glenn colpaert @ integration monday)
TRANSCRIPT
Fact or not: is EDI here to stay?
1
Fact or not: is EDI here to stay?
Nice to meet you
Glenn COLPAERTIntegration MVP
Integration Consultant @ Codit
Azure Advisor / Insider
BTUG.be Boardmember
@GlennColpaert
be.linkedin.com/in/glenncolpaert/
blog.codit.eu
4
EDIElectronic Data Interchange
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
History 101
8
9
1960’s➔ First electronic data
➔ TDCC formed
1975
➔ First EDI Standard Published
➔ Edward Guildert aka Father of EDI
➔ First VAN established
10
➔WW
➔WW
11
UN/EDIFACT
1981
1985➔WWTRADACOM
1982
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
Today
13
14
How about the standards?
15
Tradacoms
➔ Introduced in 1982
➔ Subset of EDIFACT
➔ Obsolete in favor of EDIFACT since 1995➔ But still used in UK
16
X12
➔ ANSI
➔ Mainly used in the US
➔ Transactions are identified by Numbers➔ 810 - Invoice
➔ 850 – Purchase Order
➔ 858 – Shipment Information
17
EDIFACT
➔ UN rules for EDI
➔ Internationally agreed standard
➔ Europe & Asia
➔ Transactions are identified by messages➔ ORDERS
➔ INVOIC
➔ DESADV
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
How to read EDI
20
• The first segment ‘UNA’ defines the separators and indicatorsUNA:+.? ‘
Default value Element
: Component Data Element Seperator
+ Data Element Seperator
. Decimal Notification
? Release Indicator
<space> Reserved for future use
' Segment Terminator
How to read EDI
21
Structure
22
• The ‘UNB’ segment elements identify sender, recipient, datetimeUNB+UNOA:3+STYLUSSTUDIO:1+DATADIRECT:1+20051107:1159+6002‘
• The ‘UNH’ segment provides information about the message typeUNH+SSDD1+ORDERS:D:03B:UN:EAN008‘
• Body segments depending on the message typee.g. BGM, DTM, NAD, …
• Footer segmentse.g. UNT and UNZ
DEMO Invoicing via Codit Integration Cloud
23
Codit Integration Cloud
Integration as a Service
Windows Azure based
Business Dashboard
RemoveComplexity
Internet of things
Integration Patterns
Hybrid Connectivity
Business Monitoring
25
Invoice Approval Demo
DEMO Invoicing via Codit Integration Cloud
26
Why EDI will continue to matter...
28
MATURITY
29
MULTIPLEINDUSTRIES
30
AFFORDABILITY
31
MULTIPLE NETWORKS
32
#QUESTIONS#DICUSSION
Thank you!
Keep in touch. Call or mail. Ask questions. Happy to help.
@GlennColpaert
be.linkedin.com/in/glenncolpaert/
blog.codit.eu