EDI Conversion Tool 850 to 940

Question

I need to convert x12 850 v4010 to x12 940 v4010. Most of the tools are converted from x12 to xml, then I will need to map xml to 940. I hope there is a tool that can convert from one edi document to another.

EDIT INFORMATION:

Short description

Electronic Data Interchange (EDI) is classified as the exchange of applications for an application of structured business data between organizations. X12 is the ANSI standard that provides this structure. There are many good books related to EDI business benefits, implementation considerations and operational aspects.

Answer 1

Transition to Altova MapForce and Stylus Studio®.

http://www.altova.com/downloadtrialmapforce3.html

http://www.stylusstudio.com/xml_product_index.html

Answer 2

Comparison from one document to another almost always involves the adoption of a number of assumptions that are probably true and probably usually not good enough when you talk about moving money.

Answer 3

The Servingxml library is also worth a look, compared to Altova and Stylus it is FOC.

It is capable of parsing EDI in XML and vice versa by combining steps together. It can be invoked from the command line or embedded (written in Java).

There are many examples of how to convert plain text to XML and vice versa.

Compared to Altova and Stylus, there is probably no development GUI; you must declare a mapping manually in an XML-based configuration file.

Answer 4

Also take a look at Orion's Symphonia software. This is commercial software, but does what you want.

Answer 5

I was a project manager for what is called EdiMatch, when I worked at adra match asa (a Norwegian company, I think it is http://adramatch.com ) which could read the EDI files, and then you would get "specific objects "(only COM, Windows, though) that you could serialize to" whatever you want "...

I know that they licensed it, at least Agresso (Norwegian ERP provider), when I worked for them. I think they will be interested in licensing it to others, but not sure ...

Answer 6

I think the problem may be that 850 will not have all the information needed to properly install 940. I never used 940, but I used 856 (Advanced Ship Notice) a lot that look like 940. 850 will contain information about ordering (SKU, quantity, ship and addresses, etc.), but not information about how it was sent (carrier, tracking identifiers, shipping date, weight, packaging, etc.). This information should usually be provided at the time of shipment and in conjunction with information from 850 to create 940.

There are several documents (for example, 997) that can be created from a document without “external assistance”. But I would be surprised if 940 was one of them.

Answer 7

Is this a one-time conversion or part of a process?

There are several enterprise integration tools that you can use as BizTalk.

Otherwise, if you can get hold of BizTalk 2006 R2 EDI schemas, you can get an XML representation of both documents. Then you can read the nodes for the common segments and copy them. I have not used 940 before, but I am familiar with 810, 309 and related documents and 997; but you may have to fill out some data yourself to fill out document 940.

Answer 8

If you want to use the software package to convert EDI to EDI, I would recommend using Softshare Delta . This is actually a great product that I have been using for several years. He will take care of your translation needs, but it's not free.

Answer 9

Here I see three questions. Firstly, the comparison between the purchase order and the warehouse order. The data does not match exactly, but if you accept a one-to-one relationship between the purchase order and the delivery order, then this can be overcome. I assume that you can hardcode data such as warehouse ID, hazardous material codes, etc.

The second problem is whether you need a one-time or random conversion that you do manually, or a translation of the run time that you set up once, and integrate it into the translation system?

The third is based on which tool to use? Anyway, I would take a good look at Stylus Studio. It has both an IDE for local testing, as well as a manual conversion and a run-time component that you install on the server. My former company used it extensively, and it's cheaper than almost any other real-time translator (Mercator, Gentran, etc.).

To use Stylus, you import the source file (850) and create a reusable schema that can be used to parse the file in XML. Then import the sample output format (940) to create a diagram that can be used to serialize the document back to X12.

From there, you can use the matching tools to close you, and then manually edit XSLT for complex logic that you might need to configure (for example, loops are not processed perfectly). Stylus Studio even allows you to create "pipelines" that can be used to chain multiple XSLT cards in a row or pull data from external sources in the middle of a translation.

Then you can wrap it all up and export it to a real-time environment. Even better, if you do it manually, you can simply run your files on the pipeline as you receive them, and you're done.

Answer 10

I would like to try the ALTOVA mapforce tool to convert EDI 850 X12 to Oracle Apps. It's a good choice. I heard that the most popular is http://www.sterlingcommerce.com/ , but it is very expensive.

Please advise Shashi

Answer 11

in open source bots edi-translator you can map 850 v4010 to x12 940 v4010 (http://bots.sourceforge.net). in principle, and input can be matched to any output.