Philosophies and assumptions

Before we start our tutorial on how to translate a Purchase order in xml to edi 850, there are some key assumptions and philosophies to cover.

Assumptions

XML and XSL Knowledge

It is assumed that the user is familiar with the general concepts of XML and has a basic understanding of the XML Stylesheet Language (XSL). This is not a tutorial on these technologies. For that, visit TopXML for some good tutorials.

Windows Programming

In Step 4, where we put everything together in an automated VBScript, it is assumed that the user has some familiarity with how Windows works and more particularly how VBScripting on Windows, and how the Windows' Scheduler works.

You do not need to be an expert, just have some familiarity with these technologies. We will not be spending much time on detailing how these technologies work, rather we will be focusing on getting your Purchase Order in XML to EDI 850.

Philosophies

xmlLinguist

The user must be familiar with xmlLinguist and the logic behind that easy-to-use tool. If not, visit the xmlLinguist product page at http://www.sysonyx.com/products/xmllinguist. Keep in mind that xmlLinguist is a map of the text document, not the XML document. This means that if you are translating from XML to EDI, the XML must look like EDI document, but in XML. If the XML document does not look like that yet, then you must create a Stylesheet