在生成999文件时捕获22 [英] A catch 22 in generating 999 file

问题描述

好吧，我遇到这种情况必须说很有趣:

Well, I have to say it is kind of funny when I meet this situation:

我正在入站HIPPA 837文件，并且一旦接收到837文件，我想创建999个ACK文件.如果我设置了贸易伙伴协议，BizTalk将生成999消息.到目前为止，一切正常.

I am inbounding HIPPA 837 files and I am suppose to create 999 ACK files once received the 837 file. BizTalk will generate the 999 message if I setup the trading partner agreement to do so. And it works fine so far.

今天，我收到了一个837文件，该文件存在一些结构错误:元素中有一些前导空格字符.然后创建了999，但是当我的发送端口订阅此999消息时，尝试将其另存为文件，我收到一个验证错误，抱怨999消息本身无效，因为其元素前导空格字符.....

Today, I received a 837 file with some structure error: there are some leading space character in an element. Then the 999 was created, but when my send port subscribe this 999 message try to save it as a file, I got an validation error complains the 999 message itself is invalid cause its element have leading space characters.....

错误:3(字段级错误)
SegmentID:IK4
在TS中的位置:18
数据元素ID:IK44
区隔中的位置:4
数据值:
6:找到前导或尾随空间

Error: 3 (Field level error)
SegmentID: IK4
Position in TS: 18
Data Element ID: IK44
Position in Segment: 4
Data Value:
6: Leading or trailing space found

对于我来说，它像一个陷阱22:您的999个文件假设是报告入站文件的结构错误，该报告中将包含错误的元素值(在我的情况下，它在IK4段)，但错误的元素值本身也会使999文件无效.

It looks for me like a catch 22: your 999 files are suppose to report structure error of the inbound file,it will include the wrong element value as part of the report (in my case, it's in IK4 segment) , but the wrong element value itself make the 999 file invalid too.

我只想知道是否有人遇到过同样的情况?您对这个问题有什么建议?

I just want to know if anyone have meet the same situation? And what's your suggestion on this issue?

推荐答案

我还没有看到这个，真的，我有点惊讶，如果它真的是22的话，它还没出现过:)

I have not seen this, and really, I'm a bit surprised it hasn't come up before, if it's a real catch-22 :)

尝试此操作，在协议"的您->他们"标签中，将验证"部分中的默认"行设置为前导空格和尾随空格=允许.

Try this, in the You->Them tab of the Agreement, set the Default row in the Validation section to have Leading and trailing spaces = Allowed.

由于999不在交易类型"列表中，您可能必须将所有其他tx明确设置为不允许".

You may have to explicitly set all other tx to Not Allowed since the 999 is not on the Transaction Type list.

这篇关于在生成999文件时捕获22的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！