Mohammed Atef’s Technical blog

EDI BizTalk 2009

Introduction
Electronic Data Interchange (EDI) is the single most commonly used means by which business trading partners exchange data electronically. EDI is largely messaging-oriented. Documents are implemented as flat files that can include batched transaction sets. Batched interchanges can contain multiple groups, each of which can contain multiple transaction sets or messages.

How EDI Is Implemented in BizTalk Server 2009

BizTalk Server 2009 includes native functionality providing support for EDI. It is not an add-in to the product, such as an adapter or an accelerator. It is built into the product.

Interchange Processing

The EDI feature performs the following receive-side and send-side processing in pipelines that enforce the rules dictated by the EDI standards.

  • Processes incoming EDI messages, including validating the interchanges and generating acknowledgments
  • Generates and sends outgoing EDI messages, including validating the interchanges and depending upon the configuration, processing received ACKs.

Batch Processing

Batch processing is handled by the receive pipeline and orchestrations:

  • If a received batched interchange is to be split, splits it into its constituent transaction sets, generating an XML file for each transaction set and promoting properties required for send-side batch generation.
  • If a received batched interchange is to be preserved, processes the batch such that it retains the transaction sets and groups that it contained when it was received.
  • If configured, batches received EDI transaction sets and groups into an outgoing interchange.
  • If multiple parties subscribe to a batched interchange, sends a copy of the batch to each party.

Trading Partner Agreements

Trading partners mutually set the properties for their agreement in the BizTalk Administration Console. These party properties, plus send and receive port/location properties, determine receive- and send-side EDI processing.

Interchange Status

BizTalk Server provides EDI-specific status reporting. These status reports provide comprehensive status of an EDI document exchange transaction, including acknowledgments correlated

EDI Components in BizTalk Server 2009

Microsoft BizTalk Server 2009 components used for EDI processing include the following

1-    The BizTalk EDI Application contains artifacts (including pipelines, orchestrations, and schemas) that are needed to process EDI documents.

2-    The BizTalk EDI Receive Pipeline (EdiReceive pipeline) parses EDI-encoded documents, splits EDI batches, converts the EDI-encoded documents into XML encoding, performs EDI and XSD validation, and performs HIPAA X12 sub-document splitting.

3-    The BizTalk EDI Send Pipeline (EdiSend pipeline) converts XML documents into X12 or EDIFACT encoding, serializes EDI-encoded documents, and performs EDI and XSD validation

4-    The Partner Agreement Management (PAM) user interface enables you to set processing properties for parties engaging in EDI document exchange and AS2 document transport, and global properties to be used in the absence of a party

5-    The batching orchestration batches EDI interchanges and sets context properties for sending of the batched interchange. The routing orchestration handles the instances in which multiple parties subscribe to a message to be batched, creating as many copies of the message as required

6-    The status reporting user interface provides comprehensive status of EDI interchanges and correlated acknowledgments

7-    Design time tools in Visual Studio enable you to generate an instance, validate an instance, validate a schema, test a map, and validating a map.

8-    A schema repository includes X12, EDIFACT, HIPAA X12N 4010A XSD, EANCOM, and control schemas

9-    A migration wizard enables you to migrate schema, schema modifications, and party properties from BizTalk Server 2006 to BizTalk Server 2009

Next post will describe EDI processing.

I hope this help

Advertisements

May 18, 2009 - Posted by | Biztalk |

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: