BizTalk

Using Dynamic Maps in Microsoft BizTalk

Using maps in a Microsoft BizTalk orchestration is pretty straightforward – create your source and destination schemas, map from one to the other, drop a Transform shape onto your orchestration, and configure the source and destination messages. But what if you need to apply different maps based on some property inside the message, or even who the message is coming from? In our case, we process X12 837 healthcare claim files. In the X12 schemas, the same piece of information can be stored in different ......

Packt Publishing Thousand Titles Campaign–free eBook!

Packt Publishing is celebrating the release of its 1000th title by offering web site members their choice of free eBook. They are also opening their online library for a week for free to members, to allow you to research your choice. 

If you’re not already a member, signing up is free, but you have to do so by September 30th to get the free eBook.

To sign up, just go to www.packtpub.com/login.

BizTalk–Looping through repeating message nodes in orchestrations

Say that you have an incoming BizTalk message with many repeating nodes, and you want to process each one the same. The easiest thing to do would be to use the envelope to split the single message into multiple messages, then have multiple instances of your orchestration handle each one (similar to how the HIPAA “multiple” message schemas work). But what if you need to do some work after every individual message has been processed? I’ll show you how to use the Loop functoid along with xpath queries ......

BizTalk–Mapping a NACHA file using the Flat File Mapping Wizard and preserving header information

In a previous post I demonstrated how to use the Flat File Mapping Wizard to map a NACHA financial file, and at the end I said I’d follow up with a post on setting up the pipeline and preserving the header information. Well, I totally forgot about that until someone asked where the post was, so here it is… Begin by creating the three schemas as shown in the previous post. Add a pipeline to the project, and drag the Flat file disassembler component from the toolbox to the Disassemble stage. Right-click ......

BizTalk Server - Microsoft has released HIPAA 5010 Errata schema

Microsoft has release new BizTalk 5010 HIPAA schemas to support the A1 and A2 errata documents. They are bundled with a BizTalk Server 2009 Cumulative Update (#2, to be specific), but you can easily extract just the schemas for BizTalk 2010. The CU2 download is available at: http://support.microsoft.co... (you'll have to request the download by giving them your email address and having them send you the link). For the HIPAA 5010 Errata schemas, run MicrosoftEdiXSDTemplatesKb2... file ......

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 - Stopping TA1 generation in EDI applications

When receiving EDI messages in BizTalk, you have the option of sending an Interchange Acknowledgment (TA1) when a file is received. This is configured in the X12 Fallback Settings in BT 2010, or in EDI Global Properties in previous versions. However, even if you have this disabled, if your inbound file has the ISA14 field (Acknowledgement Requested) set to 1, then a TA1 will be created. It will then be suspended, since BT doesn't know what to do with the message. To get around this, you have two ......

Directly querying the BizTalk database for suspended messages

I needed to write a quick job that would notify support folks whenever a BizTalk message was suspended. Yes, you could use WMI and/or MOM, but since we're not currently using anything along those lines this was the quickest way to go. Run this against the BizTalkMsgDb database: SELECT nvcName as ApplicationName, DATEADD(hh,-6,dtSuspendTime... as DateSuspended, -- Subtract the appropriate hours for your timezone nvcAdapter as Adapter, nvcURI as URI, nvcErrorDescription as ErrorDescription FROM ......

Full BizTalk Archive