EDI X12 Trading partner configuration in BizTalk

 Introduction

In this blog post, we will explore the process of setting up trading partner configuration in BizTalk. This involves creating parties, configuring agreements, and testing the solution. Let's dive into the details.

Steps

Creating parties in BizTalk

To begin, we need to create two parties - one for our company and another for our trading partner. Let's start by creating the party for our company named "Vipin." Follow these steps:

  • Connect to the BizTalk Admin console.
  • Right-click on "Party" and select "New" -> "Party."


  • Name the party as "Vipin" and click on OK


  • Creating the party will also create the profile for you.



Next, let's create the party for our trading partner, "ABCCompany" by following the same steps.


Understanding the X12 File

Now, in order to configure the agreement, we need to have a sample X12 EDI message that "ABCCompany" will be sending to our company, "Vipin." Let's utilize the following sample X12 file for the purpose of this demonstration.

ISA*00*0000000000*00*0000000000*08*4532345856     *12*8038025150     *020624*1158*U*00401*000000009*0*P*>~
GS*PO*4532345856*8038025150*20020624*1158*02*X*004010~
ST*850*103465910~
BEG*00*SA*0065-9182075-0579*123*20020624~
REF*DP*065~
FOB*DF*OR*FT ML SC~
CSH*Y~
ITD*01*2*****60~
DTM*037*20020627~
DTM*038*20020628~
TD5*B*2*SOCS*C~
N1*BY*WALGETS DC 0579*92*0579~
N3*131 NORTH ROAD~
N4*WILTON*NY*12831*US~
N1*ST*WALGETS DC 0579*92*0579~
N3*132 NORTH ROAD~
N4*WILTON*NY*12831*US~
PO1*20*96*EA*4.562*WE*CB*065052404*VA*G70122852*UP*490650524047~
CTP*RS*RES*9.99********1~
PID*F*73***NONE~
PID*F*08***GLASS VASE~
PO4*6~
SE*21*103465910~
GE*1*02~
IEA*1*000000008~


Before proceeding, it's essential to understand the X12 file structure. The first two lines of the file, known as the envelope, are crucial for configuring the agreement. The first line is the ISA segment, and the second line is the GS segment. Each segment consists of multiple elements separated by delimiters (in this case, an asterisk), and each segment ends with a segment terminator (a tilde).

ISA*00*0000000000*00*0000000000*08*4532345856     *12*8038025150     *020624*1158*U*00401*000000009*0*P*>~
GS*PO*4532345856*8038025150*20020624*1158*02*X*004010~

 Creating the agreement

The agreement is where you set up the envelope information and separators. Follow these steps:
  • Right-click on "ABCCompany_Profile" and select "New" -> "Agreement."


  • Name the Agreement as "ABCCompany Agreement"


  • Select the protocol as X12

  • By creating the agreement, you'll notice two additional tabs: "ABCCompany -> Vipin" representing inbound flow and "Vipin -> ABCCompany" representing outbound flow.

Configuring the Agreement
  • Check the check boxes as highlighted in the figure given below.


  • Configure ISA05, ISA06, ISA07, ISA08 based on the input EDI file. Please refer the figure given below.

  • Configure the Acknowledgements section as highlighted below.

  • Configure Envelopes. Configure ISA11, ISA12 and ISA15 based on the input EDI file


  • Configure Character set and separator section as shown below.


  • Let us maintain default settings under the Local Host settings


  • Let us maintain default settings under validation


  • Let us maintain default settings under Batch Configuration

  • Let us maintain default settings under Send Ports


  • Configure the Transaction Set List as shown below.



  • Configure Validation as shown below.


  • Configure Local Host Settings as shown below.

  • Choose the target namespace as shown below.

  • Configure Envelopes as shown below.







From Vipin -->ABCCompany
Now let's configure the outbound flow from Vipin --> ABCCompany by referring the sample EDI file given below. Follow these steps:


  • Go to the tab Vipin --> ABCCompany and  configure the Identifiers tab as shown below.


  • Configure the Acknowledgements as shown below
  • Configure Envelopes as shown below

  • Configure Characters set and separators as shown below.


  • Maintain default settings under local host settings, validation, Batch Configuration and Send Ports
  • Configure Transaction Set List as shown below


  • Configure Validation as shown below
  • Configure Local Host Settings as shown below


  • Configure Envelopes as shown below


  • Click on Apply and Ok


  • You will now see that the agreement has been successfully created.


Testing the solution
To test the solution, follow these steps:
  • Create a BizTalk application and name it as POCTradingPartnerConfiguration. Reference BizTalk EDI Application in this application 
  • Create a one way Receive port named as POCTradingPartnerConfiguration.RP
  • Create a receive location POCTradingPartnerConfiguration.RL with URL "D:\Developer\Vipin\POCTradingPartnerConfiguration\IN". 
  • Reference the EDI receive pipeline in the receive location
  • Create a send port name as POCTradingPartnerConfiguration.SP with the URL "D:\Developer\Vipin\POCTradingPartnerConfiguration\OUT". Configure the filter condition as BTS.ReceivePortName == POCTradingPartnerConfiguration.RP
  • Restart host instances
  • Test the solution by dropping a file in the receive location. You will see that the XML version of EDI file will be created in the send port.



Comments

Post a Comment

Popular posts from this blog

How to create an EDI 850 profile in Boomi?

Image
Here is a sample EDI profile that I downloaded from the internet. ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*> GS*PO*4405197800*999999999*20101127*1719*1421*X*004010VICS ST*850*000000010 BEG*00*SA*08292233294**20101127*610385385 REF*DP*038 REF*PS*R ITD*14*3*2**45**46 DTM*002*20101214 PKG*F*68***PALLETIZE SHIPMENT PKG*F*66***REGULAR TD5*A*92*P3**SEE XYZ RETAIL ROUTING GUIDE N1*ST*XYZ RETAIL*9*0003947268292 N3*31875 SOLON RD N4*SOLON*OH*44139 PO1*1*120*EA*9.25*TE*CB*065322-117*PR*RO*VN*AB3542 PID*F****SMALL WIDGET PO4*4*4*EA*PLT94**3*LR*15*CT PO1*2*220*EA*13.79*TE*CB*066850-116*PR*RO*VN*RD5322 PID*F****MEDIUM WIDGET PO4*2*2*EA PO1*3*126*EA*10.99*TE*CB*060733-110*PR*RO*VN*XY5266 PID*F****LARGE WIDGET PO4*6*1*EA*PLT94**3*LR*12*CT PO1*4*76*EA*4.35*TE*CB*065308-116*PR*RO*VN*VX2332 PID*F****NANO WIDGET PO4*4*4*EA*PLT94**6*LR*19*CT PO1*5*72*EA*7.5*TE*CB*065374-118*PR*RO*VN*RV0524 PID*F****BLUE WIDGET PO4*4*4*EA PO1*6*696*EA*9.55*T...
Read more

Basics of Correlation in BizTalk

Image
 Introduction In this blog, we will try to understand the basics of Correlation. In some cases, we would want the message to be correlated to another message in the message box and we can use correlation set and correlation Type to achieve this. Sometimes, it's not just about connecting messages. We may also need to attach additional properties to a message, such as a unique GUID or an application identifier, and promote these properties on to the context. We can also achieve this using Correlation Type and correlation set. Think of Correlation Type as a class, and Correlation Set as an instance of that Class.  Process Flow Schema Creation Create an Order schema with a field called Order. Distinguish this field Create an Ack Schema with a field called Status Create a Property Schema with 4 fields and set the property base of the fields to "MessageContextPropertyBase": Application Order Application1 Order1 Maps Create a map and name it "Order_TO_Ack". Source Sche...
Read more