EDI Tools
Electronic Data Interchange (EDI) is a set of computer interchange standards for business documents such as invoices, bills, and purchase orders. Learn how EDI tools for working with EDIFACT and X12 will radically simplify your next data integration project.
XML Pipeline Server™ is the highly scalable server platform that automates data conversion, validation, transformations, report and document generation from/to a variety of data sources. Deploy XML Pipeline Server™ on any server or workstation in your enterprise. You can also have a zero footprint deployment using our cloud-based offering.
EDI to XML
The <%= ConfigurationManager.AppSettings["SS"] %> EDI to XML Conversion module makes it easy to convert standard EDI documents to XML, and you can create custom conversion definitions to convert proprietary EDI to XML, too! Convert hundreds of EDI standard dialects and message types like EDIFACT, HL7, and X12 to XML, and modify XML output to your specifications.
EDI Mapping
<%= ConfigurationManager.AppSettings["SS"] %> EDI Mapping Tools include utilities for converting EDIFACT to XML, X12 to XML, and bi-directional converters for deploying them.
These converters can be used as part of XSLT and XQuery processing, part of XML pipelines, or used directly within your own programs.
Converting Custom EDI Message Types
<%= ConfigurationManager.AppSettings["DDXC"] %>, which are bundled with <%= ConfigurationManager.AppSettings["SS"] %>, help you convert numerous EDI dialects like EDIFACT, X12, IATA, and EANCOM to XML. But did you know you can use <%= ConfigurationManager.AppSettings["SS"] %> to convert custom EDI message types?
Converting EDIFACT to XML
Point to an EDIFACT document, hit a few buttons, and voilà! a fully-commented XML file. The comments can be turned off when you're sure the data transformation is just perfect. In the meantime, your data never looked so good.
Converting XML to EDIFACT
Going from EDIFACT to XML is one thing, but we can do it backwards also. The converter is so transparent to your use, you can change the text in the XML editor, save it back to disk, and see the change persisted in the EDIFACT file!
Converting X12 to XML
The X12 converter, just like the EDIFACT converter, can go from XML to X12 EDI. Instead of using the X12 URL itself as the destination, simply prefix it with converter:EDI? and the output will happen through the X12 converter. 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 converter will handle the details of creating a syntactically correct X12 file from the XML editor, or even from your XQuery or XSLT transforms.
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. <%= ConfigurationManager.AppSettings["SS"] %> 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.
Generate XML Schema from X12
The DISA X12 standards are constantly being updated. How can you insure that your data stream is valid against what's coming down the pike? Being able to create XML Schemas for any transaction set or release, and then being able to build maps or do validation against said schemas can ease your burden.
Transform EDI to EDI
Since <%= ConfigurationManager.AppSettings["SS"] %> can do XML to EDI and EDI to XML and XML to XML, there is no reason why it shouldn't be able to do EDI to EDI. And the same XSLT and XQuery tools historically used for XML mapping and transforming can now be used for working with EDIFACT, X12, flat files, relational databases, or any combination.
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 converter library of <%= ConfigurationManager.AppSettings["SS"] %> 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).
EDI Standards Support
Stylus Studio supports the following EDI standards: EDIFACT, HL7, IATA, X12, EANCOM, Edig@s, HIPAA, NCPDP and TRADACOMS. Click on the respective section headings below for detailed descriptions of how each standard is supported.
Create Custom EDI to XML Conversions
For the truly strange or proprietary EDI vocabularies, the Convert to XML tool within <%= ConfigurationManager.AppSettings["SS"] %> can help you build your own converter, which can then be used like any other converter to go from EDI to XML.
EDIFACT Standards
Struggling with EDI standards? Simplify your next legacy data integration project with the EDIFACT Zone, a free online reference covering all EDIFACT and UN/CEFACT versions in detail
EDI Discussion Forum
Got an EDI question? Looking for EDI Jobs? Post your EDI-related inquiries to the EDI Discussion Forum, an open and un-moderated forum about Electronic Data Interchange.