blocks|key|132590|text|让Altova+MapForce和Stylus试一试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132591|http://www.altova.com/downloadtrialmapforce3.html|offset|length|132592|index.html|132593|entityMap|0|LINK|mutability|MUTABLE|url|1|http://www.stylusstudio.com/xml_product_index.html^0|0|0|1D|0|0|0|A|1|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]|O|$5|K|L|M|A|$N|P]]]]

Going to give Altova MapForce and Stylus Studio® a try. 

<a href="http://www.altova.com/downloadtrialmapforce3.html" rel="nofollow noreferrer">http://www.altova.com/downloadtrialmapforce3.html</a>

<a href="http://www.stylusstudio.com/xml_product_index.html" rel="nofollow noreferrer">http://www.stylusstudio.com/xml_product_index.html</a>

blocks|key|132569|text|从一个文档映射到另一个文档几乎总是需要做出一些假设，这些假设很可能是正确的，而且当您谈论移动资金时，这些假设通常还不够好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132570|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Mapping from one doc to another nearly always involves making a number of assumptions that are only probably true, and probably isn't usually good enough when you're talking about moving money around.

blocks|key|1131676|text|Servingxml库也值得一看，与Altova和Stylus相比，它是FOC。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1131677|通过将步骤链接在一起，它能够将EDI解析为XML和back。可以从命令行或嵌入式调用(用Java编写)。|1131678|有很多示例如何将纯文本转换为XML。|1131679|与Altova和Stylus相比，可能缺少开发GUI，您必须在基于XML的配置文件中手动声明映射。|1131680|entityMap|0|LINK|mutability|MUTABLE|url|http://servingxml.sourceforge.net/|1|http://servingxml.sourceforge.net/examples^0|0|A|0|0|0|3|2|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

<a href="http://servingxml.sourceforge.net" rel="nofollow noreferrer">Servingxml</a> library is also worth looking at, compared to Altova and Stylus it is FOC.

It is able to parse EDI to XML and back, by chaining the steps together. Can be called from command line or embedded (written in Java).

There is a lot of <a href="http://servingxml.sourceforge.net/examples" rel="nofollow noreferrer">examples</a> how to convert plain text to XML and back.

The con compared to Altova and Stylus is probably lack of development GUI, you must declare the mapping by hand in XML-based configuration file.

blocks|key|832929|text|还请看Orion的Symphonia软件。这是商业软件，但做你想做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|832930|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Also look at Symphonia software by Orion. It is commercial software but does what you want.

blocks|key|132817|text|当我在adra+(挪威公司，我认为它在http://adramatch.com)工作时，我是一个叫做EdiMatch的项目经理，它可以读取EDI文件，然后你会得到“具体的对象”(COM，只是Windows+)，你可以把它序列化成“任何你想要的”.|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|132818|我知道，我为他们工作时，他们至少授权给了Agresso+(挪威ERP供应商)。我想他们还是想把它发给别人，但不确定.|132819|entityMap|0|LINK|mutability|MUTABLE|url|http://adramatch.com/^0|J|K|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I was project manager for something called EdiMatch when I worked for adra match asa (Norwegian company, I think it's at <a href="http://adramatch.com" rel="nofollow noreferrer">http://adramatch.com</a>) which could read EDI files and then you would get "concrete objects" (COM, Windows only though) back which you could serialize into "whatever" you wish later...

I know they licensed it out to at least Agresso (Norwegian ERP vendor) back when I worked for them. I think they would be interested in licensing it out still to others, but not sure...

blocks|key|132831|text|我认为问题可能是850将不具备正确完成940所需的所有信息。我从来没有使用940，但确实使用了856(先进船舶通知)，这看起来类似于940。850将包含有关订单的信息(SKU、数量、船舶到地址等)，但不包含关于如何装运的信息(承运人、跟踪ids、船期、重量、包装等)。这些信息通常需要在装运时提供，并与850号的信息相结合才能创建一个940。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|132832|有些文档(如997)可以在没有“外部帮助”的情况下从文档中创建。但如果940是其中之一，我会感到惊讶的。|132833|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I think the problem may be that the 850 won't have all the information necessary to correctly complete a 940. I never used a 940, but did use 856's (Advanced Ship Notice) a lot, which look to be similar to the 940. The 850 will contain information about the order (SKUs, quantities, ship to addresses, etc), but not information about how it was shipped (carrier, tracking ids, ship date, weights, packaging, etc). This information usually needs to be provided at the time of shipment, and combined with the information from the 850 to create a 940.

There are some documents (like the 997) which can be created from a document with no 'outside assistance'. But I would be surprised if the 940 is one of them.

blocks|key|1131908|text|这是一次转换还是一个过程的一部分？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131909|有一些企业集成工具可以像BizTalk那样使用。|1131910|否则，如果您能够获得BizTalk+2006+R2+EDI模式，那么您就可以获得这两个文档的R2表示。然后，您可以读取常见段的节点并复制这些节点。我以前没有使用过940，但我熟悉810,309及其相关文件和997；但您可能需要自己填写一些数据才能完成940文档。|1131911|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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

there are a few enterprise integration tools you can use like BizTalk. 

Otherwise, If you can get a hold of the BizTalk 2006 R2 EDI schemas then you could have the XML representation of both documents. Then you could read the nodes for the segments that are common and copy those. I have not used a 940 before, but i am familiar with 810, 309 and its related documents, and 997; but you might have to fill in some of the data yourself to complete the 940 document.

blocks|key|1131955|text|如果您愿意使用软件包进行EDI到EDI的转换，我建议您使用软分享三角洲。这实际上是一个伟大的产品，我已经使用了几年。它将满足您的翻译需求，但它不是免费的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1131956|entityMap|0|LINK|mutability|MUTABLE|url|http://www.softshare.com/solutions/datatranslation/^0|T|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you are willing to use a software package to do your EDI to EDI conversion, I would recommend using <a href="http://www.softshare.com/solutions/datatranslation/" rel="nofollow noreferrer">Softshare Delta</a>. It is actually a great product that I've used for several years. It will take care of your translation needs, but it isn't free.

blocks|key|1131964|text|我在这里看到三个问题。首先，在采购订单和仓库发货订单之间进行映射。数据并不完全匹配，但是如果你假设一个采购订单和一个发货订单之间存在一对一的关系，那么这是可以克服的。我想你可以对数据进行硬编码，如仓库标识，危险材料代码等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1131965|第二个问题是，您需要手动完成的一次性转换还是偶尔进行的转换，还是只需要设置一次并集成到翻译系统中的运行时转换？|1131966|第三是基于这一点，使用什么工具？不管怎样，我都会好好看看Stylus工作室。它既有用于本地测试或手动转换的IDE，也有安装在服务器上的运行时组件。我以前的公司广泛使用它，而且它比几乎任何其他实时翻译(Mercator，Gentran，等等)都便宜。|1131967|要使用Stylus，您将导入源文件(+850)并创建一个可重用的模式，该模式可用于将文件解析为XML。然后，导入输出格式(+940)的示例，以创建一个模式，该模式可用于将文档序列化回X12。|1131968|在那里，您可以使用映射工具来接近您，然后手动编辑可能需要调整的复杂逻辑的XSLT+(例如，循环没有得到完美的处理)。Studio甚至允许您创建“管道”，这些管道可以用于将多个XSLT映射链接到一行，或者将数据从外部源拉到翻译的中间。|1131969|然后，您可以将所有这些打包并导出到您的实时环境中。更好的是，如果您手动执行此操作，您可以在获取文件时通过管道运行文件，您就可以完成这些操作。|1131970|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I see three issues here. First, mapping between the purchase order and a warehouse shipping order. The data doesn't match up exactly, but if you assume a one-to-one relationship between a purchase order and a shipping order, then that can be overcome. I assume you can hard-code data like the warehouse id, hazardous materials codes, etc.

The second problem is do you need one-time, or occasional transformation which you will do manually, or runtime translation that you set up once and integrate into a translation system?

Third is based on that, what tool to use? Either way, I would take a good look at Stylus Studio. It has both an IDE for local testing or manual conversion, and a runtime component that you install on a 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'll import the source file (the 850) and create a reusable schema which can be used to parse the file into XML. Then, import an example of the output format (the 940) to create a schema which can be used to serialize the document back into X12.

From there, you can use the mapping tools to get you close, then hand-edit the XSLT for complicated logic which may need to be tweaked (loops aren't perfectly handled, for instance). Stylus Studio even allows you to create "pipelines" which can be used to chain multiple XSLT maps in a row, or pull in data from outside sources into the middle of a translation.

Then, you can wrap all that up and export it to your realtime environment. Better yet, if you're doing this manually, you can just run your files through the pipeline as you get them, and you'll be done.

blocks|key|1131985|text|我想试用ALTOVA的mapforce工具，将EDI+850+X12转换为Oracle。这是个好选择吗。我听说最受欢迎的是http://www.sterlingcommerce.com/，但它非常昂贵。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1131986|请通知沙希|1131987|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sterlingcommerce.com/^0|1P|W|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I would like to try out ALTOVA's mapforce tool to convert EDI 850 X12 to Oracle Apps. Is this a good choice.
I hear that the most popular is <a href="http://www.sterlingcommerce.com/" rel="nofollow noreferrer">http://www.sterlingcommerce.com/</a>, but it is very costly..

Please advice
Shashi

blocks|key|1132005|text|在bots开放源码edi转换器中，您可以将850+v4010映射到x12+940+v4010+(http://bots.sourceforge.net)。基本上和输入可以映射到任何输出。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1132006|entityMap|0|LINK|mutability|MUTABLE|url|http://bots.sourceforge.net/^0|1C|R|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

in bots open source edi translator you can map 850 v4010 to a x12 940 v4010 (http://bots.sourceforge.net).
basically and input can be mapped to any output.

I need to convert an x12 850 v4010 to a x12 940 v4010. Most of the tools convert from x12 to xml then I would need to map the xml to a 940. I am hoping there is a tool that could convert from one edi document to another.

EDIT FOR INFORMATION:

<blockquote>
 <a href="http://www.rawlinsecconsulting.com/x12tutorial/index.html" rel="nofollow noreferrer">Quick Background</a>
 
 Electronic Data Interchange (EDI) is
 classically defined as the
 application-to-application exchange of
 structured business data between
 organizations. X12 is an ANSI standard
 that supplies that structure. There
 are many good books concerned with the
 business benefits of EDI,
 implementation considerations, and
 operational aspects
</blockquote>

EDI Converter Tool 850 to 940

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我需要将x12 850 v4010转换为x12 940 v4010。大多数工具从x12转换为xml，然后我需要将xml映射到940。我希望有一个工具，可以转换从一个电子数据交换文件到另一个。编辑以获取信息：电子数据交换(EDI)被经典地定义为组织间结构化业务数据的应用到应用程序的交换。X12是提供该结构的ANSI标准。有许多关于电子数据交换的业务好处、实现注意事项和操作方面的好书。

问EDI转换器工具850至940
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问EDI转换器工具850至940EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问EDI转换器工具850至940
EN