4. LAYERED ARCHITECTURE OF EDI EDI SEMANTIC LAYER APPLICATION LEVEL SERVICES EDI STANDARD LAYER EDIFACT BUSINESS FORM STANDARDS ANSI X12 BUSINESS FORM STANDARDS EDI TRANSPORT LAYER EMAIL X.435 MIME POINT TO POINT FTP TELNET WWW HTTP PHYSICAL LAYER DIAL UP LINES, INTERNET, IWAY
5.
6.
7. EDI in action BUYER’S COMPUTER SELLER’S COMPUTER PO PO CONFIRMATION TRANSPORT COMPANY BOOKING REQUEST BOOKING CONFIRMATION ADVANCE SHIP NOTICE STATUS RECEIPT ADVICE INVOICE PAYMENT
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22. Functions of a third party VAN Company Financial Institution Transport Company Manufacturing Company Translate Incoming Documents Performs Compliance Checking Format translation of (X.12=> EDIFACT) Route to mailbox ID Third-Party Value Added Network (VAN)
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44. Comparison of EDIFACT and X.12 Standards Easy to update – so trading partners often use different versions of the standard (problem) Fewer data elements and segments and only one beginning segment (header) , but it has more composites Each element should have a specific name such as order date, invoice date… Segments allow element generic or multiuse elements such as date. A qualifier, such as order or invoice, accompanies the generic element identifying what the date relates to X.12 EDIFACT
45. Comparison of EDIFACT and X.12 Standards <iq type='set' id='ANY' to='ANSI_X12Gate@way.com'> <query xmlns='http://jabber.org/protocol/ansi_x.12'> ST*850*000000101~ BEG*00*NE*123456789*991125**AC~ N1*BT***0111213~ N1*ST***5566789~ PO1*1*250*KGM*15.3*SR*EAN*MY1001~ CTT*1*2~ SE*7*000000101~ </query></iq> Example. UNB +UNOA:1+US::US+50138::THEM+960531:0305+001934++ORDERS' UNH +1+ORDERS:91:2:UN' BGM +220+A761902+4:19960530:102+9' RFF +CT:EUA01349' RFF +AAV::C' TXT +THIS IS WHAT AN EDI MESSAGE WOULD LOOK LIKE... ' NAD +BY++OUR NAME PLC::::+++++EW4 34J' CTA +PD' COM +01752 253939:TE+01752 253939:FX+0:TL' CTA +OC+:A.SURNAME' COM +2407:EX' CTA +TI+:B.BROWN' COM +0:EX' CTA +SU' COM +0161 429 7476:TE+01752 670633:FX' UNT +15+1' UNZ +1+001934' Example Message - Segment tags are shown in bold e.g. UNB Note: Data elements that could identify the participants have been changed, although the text is based on a live transmission. X.12 EDIFACT
A Value Added Network (VAN) will be an application service provider (ASP) or the established network between an enterprise and its partner. The ASP will act as an intermediary facilitating business processes among enterprises. VANs transmit data formatted as Electronic Data Interchange (EDI).
Less intervention OmniCapture has helped them scan documents with lesser human intervention and fewer errors. OmniDocs has been useful for archiving purposes, helping them in preserving important documents such as policies and claims granted. OmniFlow has acted as the spine of all information that comes into the organisation through policyholders.
![Electronic Data Interchange (EDI) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)