1. EDI to XML Using XML to take the headaches out of EDI processing Blair Schneider McKay Clareos, Inc. Clareos, Inc. http://www.clareos.comhttp://www.clareos.com BlairSchneiderMcKay@comcast.net

2. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 2 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation 8. Q & A

3. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 3 Project Motivation AT&T Custom User Solutions (ACUS) niche telecomm biller for colleges, military bases, state governments, other AT&T units, etc. niche telecomm biller for colleges, military bases, state governments, other AT&T units, etc. small development group. XP and agile development. small development group. XP and agile development. at issue was one of our VAS offerings: reconcile client facility bills and help them address discrepancies. at issue was one of our VAS offerings: reconcile client facility bills and help them address discrepancies. The Issue: Reconciliation was done by manual comparison of electronic usage records to paper invoices. This was costly and slow, and it created an extra quality-control burden.

4. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 4 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation 8. Q & A

5. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 5 Electronic Data Interchange early alternative to facsimile and postal mail early alternative to facsimile and postal mail standards-based standards-based - ANSI / ASC X12 / DISA - UN/EDIFACT - http://www.disa.org hardware, data, software, and network specs hardware, data, software, and network specs “VANs”, mailboxes, wire-transfer protocols, etc. “VANs”, mailboxes, wire-transfer protocols, etc. widespread widespread DISA estimates over 300,000 companies use it. becoming more integrated with XML becoming more integrated with XML Example: “Electronic Business XML” (ebXML)

6. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 6 Sample EDI Document ISA~00~ ~00~ ~01~00001123 ~ZZ~MICHIGANSTA ~040103~1950~U~00401~000001029~0~T~> GS~CI~006968523CRI~123456XYZ~20040407~1527~128~X~004010 ST~811~000000001 BIG~20040407~734555121299920040407~~~~~DI REF~EH~773 REF~12~7345551212999 REF~AP~7345551212999 ITD~18~3~~~~20040421...snip... SE~17921~10290002 GE~2~128 IEA~1~000001029 Modeled on samples in: http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf

7. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 7 EDI Technical Summary data element types numeric, decimal, identifier, string, date, time delimitersdata-element-separator first character after “ISA”, often “~” sub-element-separator first character of 16 th ISA data element segment-terminator character after the sub-element-separator hierarchies segments nest in “loops” ISA GS ST Details SE GE IEA

8. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 8 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation 8. Q & A

9. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 9 Why XML? The 811 document is already hierarchical.The 811 document is already hierarchical. It’s easier. Many companies find EDI too expensive, too complex, and too inflexible.It’s easier. Many companies find EDI too expensive, too complex, and too inflexible. Once something is in XML format, you can “go anywhere” with it.Once something is in XML format, you can “go anywhere” with it. By converting EDI to XML you trade complex, “single-use” tools for generic XML tools like DTD, W3C Schema, XSLT, SOAP, DOM, SAX, etc.

10. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 10 More Motivation… USD Segment If USD08 is populated, then the amount in USD08 is the segment amount. If USD08 is not populated, then the following determination is made to determine the segment amount: If USD05 = “M4”, then the amount in USD06 is the segment amount. If USD05  “M4”, then the product of USD03 and USD06 is the segment amount. If USD01 = “O”, then the segment amount is for information purposes only. The USD segment can be used to provide taper table information for WATS billing. In this use, USD01 would equal “O”. Note 1: When both USD03 and USD08 are populated, the amount in USD08 takes precedence and becomes the segment amount. Note 2: In order to verify amount in USD08, it is necessary to multiply USD03 * USD06 * USD07 * Percent of Interstate Usage. The Percent of Interstate Usage can be found in an SI pair (DE 1000 = ‘PU’) within the SLN loop, when it is present. From: http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf, p6.2.8

11. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 11 Sample EDI Document - Revisited ISA~00~ ~00~ ~01~00001123 ~ZZ~MICHIGANSTA ~040103~1950~U~00401~000001029~0~T~> GS~CI~006968523CRI~123456XYZ~20040407~1527~128~X~004010 ST~811~000000001 BIG~20040407~734555121299920040407~~~~~DI REF~EH~773 REF~12~7345551212999 REF~AP~7345551212999 ITD~18~3~~~~20040421...snip... SE~17921~10290002 GE~2~128 IEA~1~000001029 Modeled on samples in: http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf http://www.sbc.com/Common/PDF/811v4010_CRIS-SW_CABS-SW+W_SBCT_IG.pdf

12. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 12 Raw XML 4 3 8 1 5.0 I M4 11.85 I SV 0705 HL~4~3~8~1 SLN~5.0~~I~1~M4~11.85~~I~SV~0705 Edi2Xml.exe

13. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 13 The Edi2Xml Utility Sample init file: Nesting ISA 1 Nesting IEA 1 Nesting GS 2 Nesting GE 2 Nesting ST 3 Nesting SE 3 Nesting_FieldComp HL 4 3 Single * class Segment { public: public: enum Relationship { child, sibling, uncle }; enum Relationship { child, sibling, uncle }; virtual Relationship comp( const Segment& other) const; virtual Relationship comp( const Segment& other) const; //... //...};

14. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 14 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation 8. Q & A

15. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 15 XSLT Examples Local IntraState/InterLata IntraState/IntraLata...snip...

16. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 16 4 3 8 1 5.0 I M4 11.85 I SV 0705 Translated XML – v.1 HL~4~3~8~1 SLN~5.0~~I~1~M4~11.85~~I~SV~0705 Edi2Xml.exe XSLT <SLN id1='5.0' relcode='I' qty='1' type='money' included='yes' service-rendered='yes' svc_type='0705'> 11.85...snip...

17. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 17 Translated XML – v.2 4 3 8 1 5.0 I M4 11.85 I SV 0705 HL~4~3~8~1 SLN~5.0~~I~1~M4~11.85~~I~SV~0705 Edi2Xml.exe XSLT $11.85...snip...

18. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 18 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation 8. Q & A

19. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 19 Validating the Input Data EDI transaction sets contain checksums. Control codes in matched segments (ISA/IEA, ST/SE, GS/GE) must line up.Control codes in matched segments (ISA/IEA, ST/SE, GS/GE) must line up. Some segment-types (like HL) have global sequence numbers, parent-references, nesting indicators:Some segment-types (like HL) have global sequence numbers, parent-references, nesting indicators: HL~45~37~5~0 HL~(my id)~(my parent’s id)~(my level)~(I have children) Optional transaction totals:Optional transaction totals: CTT~3 CTT~(# of preceding IT1, or line-item, segments)

20. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 20 Validating the Input Data – With XML! 1. Hook into existing EDI validation rules using time- tested XML methods: DTD DTD W3C XML Schema Language W3C XML Schema Language Schematron Schematron 2. Create sys-admin dashboards. E.g.., express this in XSLT: display in bold-red type: any loops whose instance-id is not (previous-id+1) display in bold-red type: any loops whose instance-id is not (previous-id+1)

21. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 21 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation 8. Q & A

22. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 22 Storing and Using the Results EDI to XML makes great sense. But EDI to XML to RDBMS can be tricky. If the goal is to produce a document (like a detailed invoice) just use XSLT to produce HTML, PDF, etc. In many cases, you should just insert into the RDBMS only the values and labels you care about, along with a unique id pointing to the (saved) XML.

23. Oct 21, 2004Blair Schneider McKayEdi To Xml – Slide 23 Agenda 1. Project Motivation 2. EDI Basics 3. Syntactic Conversion: EDI to XML 4. Semantic Conversion: XML to XML 5. Validating the Input Data 6. Storing and Using the Results 7. System Instrumentation (Demo) 8. Q & A

24. Q & A Blair Schneider McKay Clareos, Inc. Clareos, Inc. http://www.clareos.comhttp://www.clareos.com BlairSchneiderMcKay@comcast.net Source Code for the Edi2Xml tool, and both XSLT and document samples are available at: http://home.comcast.net/~blairschneidermckay/ http://home.comcast.net/~blairschneidermckay/