1 / 26

Optimizing EDI Translations with XML Solutions: Challenges and Innovations

This presentation, held by EDI Manager Mickael BOMARD from AGENA 3000, explores the complex world of Electronic Data Interchange (EDI) in the Balkans. It discusses the significance of EDI, its translation challenges, and presents software solutions like GENEDI, which utilizes XML for efficient data management and interoperability. The session covers fundamental concepts, partnership insights with LITIS, the role of normalized languages, and technical capabilities needed for successful EDI integration. Join us for an insightful demo and Q&A session aimed at improving EDI processes.

baba
Télécharger la présentation

Optimizing EDI Translations with XML Solutions: Challenges and Innovations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Translating EDI-structured files by using XML Facts, problems and software solution DevReach – Sofia (BG) Tuesday, October 10, 2006

  2. CONTEXT Who is this guy ? Mickael BOMARD EDI Manager for a french software Editor AGENA 3000 – www.agena3000.fr

  3. AGENDA Partnership LITIS – AGENA 3000 towards Balkanic background and perspectives What is EDI How to achieve an EDI-translator Demo Q&A

  4. LITIS & AGENA 3000 PARTERSHIP Process Optimization Expert Knowledge of the balkans Company setteled in Bulgaria French Software Editor Specialist of the reliationship between Retail & its suppliers - ERP - MDM - PIM - EDI

  5. Balkan peninsula topology Romania Serbia Bulgaria Greece Turkey Macedonia

  6. AGENDA Partnership LITIS – AGENA 3000 towards Balkanic background and perspectives What is EDI How to achieve an EDI-translator Demo Q&A

  7. What is EDI ? Without normalization 2 companies – 2 formats for the same message

  8. What is EDI ? Without normalization 4 companies – 12 formats for the same message

  9. Normalized langage Community Value Added Network What is EDI ? EDI stands for Electronic Data Interchange EDI is a three part tuple EDI

  10. ODETTE EDISPORT INOVERT EDITEXT EFOVAD What is EDI – Normalized language EDIFACT normalization is part of the UNO missions EDIFACT Orders EANCOM Despatch Advice Invoice Transport Retail Automobile

  11. Company Suppliers What is EDI - Community Customers Wharehouse bank State

  12. What is EDI – Value Added Network (VAN) X400 exhange protocol insured by a provider Based on adresses (C=BG;A=GENTRAN…) Ruled by request/response process Usually asynchronous GXS ; IBM/GN ; GENTRAN ; ATLAS 400 AS1 : secured smtp (encrypting and e-sign) AS2 : secured http (certificate) Synchronous No provider to pay

  13. What is EDI – Resume Company B Company A ERP ERP EDI EDI B’sbox A’sbox VAN Provider

  14. AGENDA Partnership LITIS – AGENA 3000 towards Balkanic background and perspectives What is EDI How to achieve an EDI-translator Demo Q&A

  15. How to achieve an EDI Translator The requested functionalities Management of Electronic Data Interchange • Basic datas management • Partner’s management • Management of dictionaries(Eancom, Gencod, private, …) • Management of methods (conversions,dates, …) • Management of standard and private flows (orders, shipping notice, invoice, delivery notice, …) • Interchange arrangements management (PiP’s : Partner Interchange Process) • For every interchange with third person – defines the relations between incoming and outgoing flowby means of a« mapper ».

  16. How to achieve an EDI Translator The requested functionalities Interchange flows exploitation • Customize the operatingconditions • Communication layers management • Ensure correctdaily functioning • Planning and automatization of jobs • Ensure activity control • Resolve disfunctions

  17. How to achieve an EDI Translator Problems / Limits / constrains About use • Exclusively for the external flows • 1 message = 1 translation • Difficulty accessing the operating functions • Software solutions based on an outdated technologies • Need of flow centralization (EDI and no EDI) • Need of «network» solutions

  18. How to achieve an EDI Translator Problems / Limits / constrains About norms • Multiplication of incoming and outgoing formats (EDI, plain files, CSV, XLS, …) • The advent of XML and associated norms About networks • Appearance of the Internet network / IP Protocol • EDIINT AS2 Protocol • Web message service integration (SMTP)

  19. How to achieve an EDI Translator The response we’ve achieved : GENEDI About norms • New format : XML • When entering or going out, choose between following formats : • Plain (TXT, CSV, XLS, …) • EDI (Edifact and its subsets, Tradacom, Aecoc, …) • XML • GENEDI is originally XML • The translation is realized via XSLT (XSLT is a recommendation of W3C) • Script integrated

  20. How to achieve an EDI Translator The response we’ve achieved : GENEDI • About networks • Conformity with TCP/IP technologies • Browser (HTTP), • FTP, • EDIINT AS1, AS2 • Integration of mails service using the MS-API’s • Warnings • EDI Interchanges

  21. How to achieve an EDI Translator The response we’ve achieved : GENEDI • Technical prerequisites • Operate in Windows Pro, XP, 2003 • User Interface via browser • Data base MySQL (first version) SQL Server 2005 using XML form improve up to 30% treatment time

  22. How to achieve an EDI Translator The response we’ve achieved : GENEDI

  23. How to achieve an EDI Translator The response we’ve achieved : GENEDI • Outqueues • Via : VAN, SMS, Mail, Fax, ftp, • Follow-up • Tashboard, Warnings (operating, functional and event warnings), Statistics • Multirouting • A received message can be translated in different ways in order to be furnished to a different applications • Flow characterized by sender, recipient, target (= receiving application) • Speed • Possibility of n simultaneous translations • Power • Possibility of load balancing (translation, communication) between several workstations • Simplified backup

  24. GENEDI is pre-parametered with

  25. DEMO www.a3wedi.com Visit the guest environnement login = aspuk Password = kupsa

  26. Q&A panel Don’t hesitate to contact us Liubomir BOUEV dg@litis.com Mickael BOMARD mickael.bomard@agena3000.fr

More Related