预处理EDI文件 [英] Preprocessing of EDI file

查看:63
本文介绍了预处理EDI文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个几乎构建的过程:

I have a process almost built that:

路径835基于npi

routs 835's based on npi

有些声称分裂

地图上有趣的东西

规则查找一些重命名&文件路由....

Rules lookups for some renameing & routing of files....

使用地图,编排,规则和派对等许多有趣的东西。

Lots of fun stuff using maps, orchestrations, rules and party stuff.

 

但是我有一个问题我不知道如何处理:

But I have one problem I'm not sure how to handle:

需要:我需要获取原始文件(整个事情都是st-se's)和第一个复制到文件共享。这是计费部门想要的。

needs: I need to get the original file (whole thing all st - se's) and first make a copy to a file share. This is what the billing department wants.

我需要使用文件中显示的第一个DTM的前缀和日期来命名此文件。  (这是我要做的代码处理)

I need to name this file with a prefix and date from the first DTM that shows up in the file.  (this I have code process  to do)

为文件添加一个唯一的编号。 (这个我有代码可以做)

Add a unique number to the file. (this I have code prcess to do)

查找一些相同的规则。 (我的代码也在管弦乐队中这样做了)通过  ISA接收者ID和ISA发送者ID

Lookup some of the same rules. (I have code in an orchestratin that does this too) by ISA receiver id and ISA sender id

不确定如何让文件进入biztalk进程来执行此操作?

Stiill not sure how to get the file into the biztalk process to do this?

 

此后的后处理使用了transaction和edi dissasembler设置的派对。所以,我无法改变这个过程。

The post processing after this uses party setup by transaction and edi dissasembler. So, I can't change that process.

 

我在脑海中看到它,并且很难解决这个问题。我需要某种预处理方式,然后将835重新编入biztalk以进行剩余的处理......任何人都可以看到我的意思吗?

I see it in my head, and am having difficulty exressing this. I need some sort of way of preprocessing and then redropping the 835 back into biztalk for the rest of the processing...can anyone see what I mean?

 

将orginial未接触文件获取到文件共享,根据某些规则重命名和路由它,获取一个唯一的id来重命名,并获得第一个DTM日期添加到名称中将文件分开。

Getting the orginial untouched file to a file share, renaming and routing it based on some rules, getting a unique id to rename it with, and getting the first DTM date to add to the name without really splitting the file apart.

 

hmmmmmm

 

感谢您的任何建议,

Chris

 

 

 

推荐答案

我的推荐如下。构建一个表,该表将保存所有进入的事务,包括每个文件的文件名。此表将包含文件信息,成员名称,DOB,以及可用于跟踪每条消息的其他任何内容。
您还可以添加其他列来跟踪835报告或任何其他信息。从该表中插入文件名的所有记录,包括该文件的事务编号。当您需要撤回数据时,您将获得文件名
以及您需要的任何其他内容。您也可以使用同一个表来跟踪发出的消息。例如,您可以使用一个列来标记是否有一个835发送给该成员或类似的东西。我个人喜欢使用外部表跟踪
所有收到的消息并且更少依赖BizTalk,因为我可以根据我的需要对该表进行更改。我确信还有其他一些方法,但对我来说,这非常有效。
My recomendation is the following. Build a table that will hold all transactions that come in including the file names for each file. This table will hold file infomrmation, member names, DOB, pretty much anything else you can use to track each message. You can also add other columns to track the 835 reports or any other information. From that table you insert all the records that file name including the transaction number for that file. When you need to pull the data back out, you will have the file name and anything else you need. You can also use the same table to track the messages going out. For example you can have a column that flags if there was an 835 sent out for that one member or something like that. I personally like using an outside table to track all the messages that come in and rely less on BizTalk becuase I can make changes to that table based on my needs. I am sure there are a bunch of other ways, but to me, this has worked very well.


这篇关于预处理EDI文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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