Stylus Studio has released a comprehensive toolbox of new EDI tools for simplifying working with Electronic Data Interchange (EDI) files in legacy data integration projects, including support for both X12 and EDIFACT. The new EDI tools are fully integrated with Stylus Studio XML Deployment Adapters, meaning you can both develop and deploy sophisticated EDI-XML data integration applications in just minutes. Here's an EDI Tools overview of the new EDI tool's support in Stylus Studio 2006 XML Enterprise Edition:
Converting EDIFACT to XML: Load an EDIFACT document, hit a few buttons, out comes a fully-commented XML file. The EDI/XML comments can be disabled when you're sure the data transformation is just perfect. In the meantime, your data never looked so well-documented.
Converting XML to EDIFACT: Going from EDIFACT to XML is one thing, but Stylus Studio can do it backwards also (we like to have things both ways). Our EDI adapter is transparent to your use, so you can change the text in the XML editor, save it back to disk - your changes will automatically have been persisted to the original EDIFACT file.
http://www.stylusstudio.com/edi/X12_translate.html" target="_new" rel="nofollow">Converting X12 to XML: The X12 adapter, just like the EDIFACT adapter, can go from XML to X12 EDI. Instead of using the X12 URL itself as the destination, simply prefix it with adapter:EDI? and the output will happen through the X12 adapter. The syntax and transaction set and even release will be detected from the XML stream, and the details will be handled for you.
Converting XML to X12: Instead of worrying about the syntactic idiosyncracies of X12, concentrate on your data. The bidirectional nature of the EDI adapter will handle the details of creating a syntactically correct X12 file from the XML editor, or even from your XQuery or XSLT transforms.
http://www.stylusstudio.com/edi/EDIFACT_validate.html" target="_new" rel="nofollow">Generate XML Schema from EDIFACT: How do you know if the EDIFACT data you are working with is valid? How do you map from a copy of some document to your ERP system's inputs? XML Schemas are a useful mechanism for informing disparate applications of an XML document's structure. Stylus Studio allows you to generate an XML Schema for any message type and any version that the EDIFACT standard supports. This can be used for validation, mapping or integration.
Access EDI from XSLT or XQuery: XSLT and XQuery are excellent tools for dealing with tree-structured data like XML. Up to this point, EDI has missed out, but the transparent URL-based adapter library of Stylus Studio can build your EDI bridge. Use EDI as if it were XML -- for input, for output, or even for both (to translate from EDIFACT to X12 for example).
Create Custom EDI to XML Conversions: For your home-grown or proprietary EDI vocabularies, the Convert to XML tool within Stylus Studio can design your own XML adapter, which can then be used like any other adapter to go from EDI to XML.
Download a free trial of the world's best EDI tools today!
Ew. You guys are ugly with a capital UG. Here, maybe this tiny ad can help: