问题描述
我正在尝试实施一张地图，将X12 834 4010A1文档翻译成X12 834 5010文档。 对于单个交易集，我没有任何问题。 但是，我还需要为一组批量交易进行此翻译。 我怀疑最有效的方法是将传入的文件保留为批处理，将批处理接受到我的Orchestration，执行地图，然后输出批处理文件。 但我无法弄清楚如何做到这一点。 配置Party以保留批处理为我提供了一个封装的XML文件，我不知道如何在Orchestration中处理。 MS文档说明了批处理XML模式：
"接收管道生成的XML实例上的文档类型将是一个常量（< Encoding> _BatchSchema.xml）并将引用此规范架构。您可以在业务流程中的映射中使用此实例;但是，在这样做之前，您必须更改文档类型和名称空间以映射到所需的实际模式。"
我不能理解该段落。 有人可以帮我解构一下吗？ 我相信这会解决我的问题。
I'm attempting to implement a map which will translate an X12 834 4010A1 document into an X12 834 5010 document. I don't have any problem doing this for a single Transaction Set. However, I also need to do this translation for a batched set of Transactions. I suspect that the most efficient way to do this is to Preserve the incoming file as a batch, accept the batch into my Orchestration, conduct the map, and then output a batched file. But I cannot figure out how to do this. Configuring the Party to preserve the batch gives me an enveloped XML file that I don't know how to handle in the Orchestration. The MS documentation says this about the batch XML schema:
"The document type on the XML instance generated by the receive pipeline will be a constant (<Encoding>_BatchSchema.xml) and will reference this canonical schema. You can use this instance in a map in an orchestration; however, before doing so you have to change the document type and namespace to map to the actual schema required."
I cannot make any sense of that paragraph. Could someone please deconstruct it for me? I'm sure that would go a long way to solving my problem.
推荐答案
这篇关于在业务流程中处理EDI批处理的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！