In every EDI integration project, each new business partner and each set of EDI transactions to be added can create a new challenge for IT consultants and developers. This challenge gets even more complex when the project involves EDI integration with JDE. In my previous article How to Solve the Biggest EDI Integration Problems With JDE, I have identified one of the main problems of EDI integration with JDE and how to work around it. In this blog, I would like to discuss the advantages and benefits of using EDI2XML as a component within Magic xpi integration studio, to alleviate the complexity of EDI integration.
What is Magic xpi
Magic xpi is a business integration platform proprietary technology for Magic Software. This business integration suite is very powerful and comes loaded with tons of built-in components to build workflows and orchestrate an entire business flow:
- Database gateways: to connect “natively” to the most common databases used within an enterprise (i.e. SQL server, Oracle, DB2, Pervasive, MySQL, ODBC…).
- Connectors: to directly connect to JDE, SAP, Dynamics, SalesForce.
- Triggers and Data mappers: whether to monitor a folder content or to parse and map from one file format to another
- Connectivity and messaging: through FTP, SOAP, MSMQ, etc.
And the list goes on…
How EDI2XML works within Magic xpi
As you might already know by now, EDI2XML is our own technology to convert an X12 EDI transaction to XML. When doing the conversion from EDI to XML, EDI2XML is able to generate the FA 997 (Functional Acknowledgment) as a response to the incoming EDI transaction. In the meantime, EDI2XML installer comes with all the xml schemas (.xsd) of the EDI2XML format.
Since Magic xpi is missing a component to transform X12 EDI to XML, EDI2XML can fill this gap. By creating a custom component and inserting the command to trigger EDI2XML from within a Magic xpi business flow, EDI2XML will turn an incoming EDI file (i.e. 850) into XML format.
In a subsequent step, using a Data mapper component, the user can map the content of the EDI file in XML and map it to any other format (Flat file, database….).
Mapping EDI from EDI2XML to JDE
As mentioned previously, Magic xpi comes loaded with connectors to major systems such as SAP, JDE, Salesforce, etc. As an example, any table in JDE can be used as a source or destination in data mapping process, using a Data Mapper step within Magic xpi.
Once the incoming EDI X12 file is converted to XML, it is very simple to then map it to JDE:
- Create a step with a Data mapper
- Source: XML based on the EDI2XML .xsd (schema file)
- Destination: the JDE table to feed from the XML format
Once the source and destination are defined, the user can use his mouse to drag and drop to map fields from the source to the destination (JD table).
This is why we love EDI2XML in EDI integration with JDE
EDI2XML has a rich library of EDI documents to translate and it is expandable. In addition, using EDI2XML within a flow in Magic xpi is a MUST in order to map EDI data to XML and from XML directly to JDE. Most importantly, there is no need for EDI knowledge to interpret the fields and segments, as it is all easily understandable by any person. On top of it all, all .xsd files are provided with the EDI2XML engine!
EDI integration into JDE is as simple as mapping from XML to JDE using drag and drop!