在 BizTalk 2010 中将 4010 转换为 5010 文件时无法使用 ISA11 作为重复分隔符
我正在创建一个简单的 BizTalk 2010 进程，它将 4010 835 文件转换为 5010 格式。我有一个接受 4010 835 的接收端口，以及一个用于将 5010 版本放入其中的发送端口。接收端口附有一个映射，因此不涉及编排。只有一个聚会，有典型的他们 -> 。美国和美国->他们的标签。
测试时一切正常；该文件已正确映射，并且我在美国的所有设置（ISA 和 GS 值）-> THEM 选项卡将添加到出站文件中。当我尝试在美国设置 ISA11 使用时出现问题 -> THEM 选项卡到重复分隔符：^（这几乎是 5010 的标准）。此时，入站消息会失败，并出现一堆“数据元素中的无效字符”错误 - 文件中任何有“U”的地方。它将入站 4010 ISA 11 中的 U 视为代表。分隔符。
对于为什么会发生这种情况有什么想法吗？谢谢！
I'm creating a simple BizTalk 2010 process that will convert a 4010 835 file to 5010 format. I have a receive port that accepts the 4010 835, and a send port to drop the 5010 version to. There's a map attached to the receive port, so there's no orchestration involved. There's only a single party, with the typical THEM -> US and US -> THEM tabs.
Everything works fine when tested; the file is properly mapped, and all my settings (ISA & GS values) on the US -> THEM tab are added to the outbound file. The problem occurs when I try to set the ISA11 usage on the US -> THEM tab to Repetition separator: ^ (which is pretty much standard for 5010). At that point the inbound message fails with a bunch of "Invalid character in data element" errors - anywhere that there is a "U" in the file. It's treating the U in the inbound 4010 ISA 11 as a rep. separator.
Any thoughts on why this is happening? Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
啊，这是我愚蠢的错误...我习惯于处理在入站和出站文件之间切换 ISA06 和 ISA08 的情况，但在这种情况下，我们只是传递它，保持 ISA 相同。所以我的出站方配置实际上是拾取入站文件，将 U 视为重复分隔符。
当然，这带来了另一个问题，如果您想要入站和出站 ISA06 和 ISA06，您实际上如何进行各方配置？ 08 也是一样，但我下次再问。
Argh, it was my stupid mistake... I'm used to dealing with situations where we switch the ISA06 and ISA08 between the inbound and outbound file, but in this case we're just passing it through, keeping the ISAs the same. So my outbound party configuration was actually picking up the inbound file, treating the U as a repetition separator.
Of course that brings up another question, how would you actually do party configuration if you want the inbound and outbound ISA06 & 08 to be the same, but I'll ask that another time.