EDI

BizTalk–Mapping repeating EDI segments using a Table Looping functoid

BizTalk’s HIPAA X12 schemas have several repeating date/time segments in them, where the XML winds up looking something like this: <DTM_StatementDate> <DTM01_DateTimeQualifier... <DTM02_ClaimDate>2012... </DTM_StatementDate> <DTM_StatementDate> <DTM01_DateTimeQualifier... <DTM02_ClaimDate>2012... </DTM_StatementDate> The corresponding ......

BizTalk 2010 EDI batching–using an external release trigger

In an earlier post I showed you how to implement basic EDI batching, releasing the batch every time 3 messages were waiting. In the real world, you’re probably going to have some other criteria for releasing the batch; in our case a back-end system notifies BizTalk when all HIPAA 837 claims in a single file are ready to be sent. The MSDN page for this process is actually very easy to follow, but I’ll summarize it here. First, you’ll set up a new receive port and location to receive the trigger file. ......

BizTalk 2006 & 2009 hotfix for EDI leap year date errors

Microsoft has released a hotfix to fix a date problem in BizTalk Server 2006 R2 & 2009 when processing EDI files where a data element contains a leap date. BizTalk Server 2006 and 2010 are not affected. This issue occurs because the EDI interchange cannot validate a data element that contains a leap date value, such as "20120229". This issue can be resolved by either installing the BizTalk Server 2009 cumulative update package 1 (if you’re running 2009…) or the hotfix at the top of KB article ......

BizTalk 2010 EDI Batching Tutorial

In two previous posts I talked about party configuration and routing of EDI messages: Basic Party Resolution in BizTalk 2010 EDI Party Resolution (& trading partners) in BizTalk 2010 In this post I’ll build off of those examples and set up EDI batching so that we can deliver more than one EDI 810 invoice per file. You’ll need to have worked through the previous two posts to have your BizTalk application ready to follow along with these steps. First, change the File name: of the Contoso Send Port ......