IEEM 5352 EEnterprise Integration Introduction of XMLEDI What

IEEM 5352 E-Enterprise Integration Introduction of XML/EDI

What is XML/EDI? • This is the present attempt to combine the best features of traditional EDI (which has a broad industry support) with the improvements in technology offered by XML. It is EDI with XML, or XML with EDI - depending on the perspective. • In an XML/EDI message, the EDI information is explicitly labeled using tag names. Reference may be made via Internet to a Document Type Definition (DTD) - which contains structure declaration and relevant sets of code values. • Web browsers are expected to support XML; therefore, XML/EDI messages could be transmitted in any way: e-mail, VAN, Internet etc.

Characteristics of XML/EDI • • Support W 3 C XML standard Compatible with EDI (X 12 or EDIFACT) Business data exchanges Support business processes Provide business document and process templates Use public network for business transactions Time and cost efficiency • Ref Fig. 7. 1

(Ref. 梁等, 2000)

XML/EDI Elements • • • EDI Message/Transaction Format XML DTD/Schema Parsing Process Templates Software Agent Global Entity Repositories • Fig. 7. 7

Layered Structure of XML/EDI • • Application & Repository Rules Template & Java/Active X XML Tags/Agents/Databots XML Parser/Generator XML/EDI Data File/Message Storage/Transport

Core Models of XML/EDI • Star model – 以大廠為核心，設定交易遵循標準(Master/Parent, Children) – Follow the traditional EDI model. • Ad hoc model – 教小型貿易夥伴建立應對模式，再相互結合 • Hybrid model – Combination of star and ad hoc models • Web – A document centric model – Examples: electronic catalog, RFQ dialogs

Example: X 12 810 (INVOICE) Wrapped and Compressed ST~810~189’BIG~980208~TF 87654~980112~KJ 98 76 -34~~PR’N 1~BT~RUNNER UNLIMITED~92~MTB 1 ’N 1~ST~RUNNER UNLIMITED~92~MT 01’N 1~SE~AC ME SUPPLIES~92~AC 987’IT 1~01~100~EA~10~EA ~BP~98754 -987~EC~E~VP~5986 -0834’IT 1~02~2 ~EA~200~EA~BP~BK 454532~EC~W~VP~ 646455 -5 6’TDS~1400’CTT~2@SE~10~189’ Invoice TF 87654 date 2/8/98 for PO KJ 9876 -34 dated 1/12/98 Bill to Runner Unlimited location coded MTB 1; MTB 1 Ship to Runner Unlimited location coded MT 01 Selling Party is Acme Supplies location coded AC 987. There are two line items: IT 1= ‘ 01’ which is the PO line item number. Buyer part is 98754 -987 with engineering change E. The vendor part is 5986 -0834 for 100 units IT 1 =‘ 02’ which is the PO line item number. Buyer part is BK 454532 with engineering change W. The vendor part is 646455 -56 for 200 units

HTML vs. XML Documents of X 12 810 (INVOICE) HTML <h 1> ST~810~189’ BIG~980208~TF 87654~980112~KJ 9876 -34~~PR’ N 1~BT~RUNNER UNLIMITED~92~MTB 1’ N 1~ST~RUNNER UNLIMITED~92~MT 01’ N 1~SE~ACME SUPPLIES~92~AC 987’ IT 1~01~100~EA~10~EA~BP~98754987~EC~E~VP~5986 -0834’ IT 1~02~2~EA~200~EA~BP~BK 454532~EC~W~VP~6 46455 -56’ TDS~1400’ CTT~2’ SE~10~189’ </h 1> XML <st> <class>invoice</class> <apply>TF 87654</apply> <date>2/8/98</date> <PO> <number>kj 9876_34</number> <due>1/12/98</due> <bill_to>MTB 1</bill_to> <ship_to>MTO 1</ship_to> <selling_party>ACME</selling_party></PO> <items> <item> <count>01</count> <bp>98754 -987</bp> <ec>E</ec> <vp>5986 -0834</vp> <unit>100</unit></item> <count>02</count> <bp>BK 454532</bp> <ec>w</ec> <vp>59860834</vp> <unit>200</unit></item> </items> </st>