在BizTalk 2010中将4010转换为5010文件时,无法使用ISA11作为重复分隔符 [英] Unable to use ISA11 as repetition separator when converting 4010 to 5010 file in BizTalk 2010

查看:62
本文介绍了在BizTalk 2010中将4010转换为5010文件时,无法使用ISA11作为重复分隔符的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在创建一个简单的BizTalk 2010进程,它将4010 835文件转换为5010格式。我有一个接受4010 835的接收端口,以及一个将5010版本丢弃的发送端口。接收端口附有地图,因此不涉及
编排。只有一个派对,典型的THEM - >美国和美国 - > THEM标签。

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.

测试时一切正常;文件已正确映射,以及我在美国的所有设置(ISA和GS值) - > THEM选项卡将添加到出站文件中。当我尝试在美国设置ISA11使用时出现问题 - > THEM选项卡重复
分隔符:^(这是5010的标准)。此时,入站消息失败,其中包含一堆"数据元素中的无效字符"。错误 - 存在"U"的任何地方在文件中。它将入站4010 ISA 11中的U视为代表。分离器。

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!

推荐答案

在接收管道中....设置USEISA11AsRepetitionSeparator为真......
In the receive Pipeline....Set USEISA11AsRepetitionSeparator As true......


这篇关于在BizTalk 2010中将4010转换为5010文件时,无法使用ISA11作为重复分隔符的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆