Hi all,

It's been a while since last time I attempted to integrate EDI in BizTalk. I have been very busy with other projects, but I really need to understand how BizTalk processes EDI from multiple EDI partners within the same file. With that said, I'm including some data I used to process coming from our VAN.

Could somebody please help me understand how I would be able to process the attached file? below is the data. I used to process this file using an EDI translator, a mapping software, and some VB6 and Fox Pro programs.

Thanks in advanced. 

ISA*00*          *00*          *01*SENDER1111      *12*RECEIVER123     *070710*1325*U*00201*000006742*0*P*}
GS*PO*SENDER1111*RECEIVER123*20070710*1325*6750*X*004010
ST*850*67500001
BEG*00*SA*41090_133**20070710
DTM*037*20070717
N1*BT*0010-Plymouth
N3*6105 Trenton Ln N
N4*Plymouth*MN*55442
PER*BD**TE*763-551-7000
PO1*1*2*EA*57.95********IN*420961
PID*F**ZZ*PD*MATTRESSPAD,LYOCELLDOWN,QUEEN
SDQ*EA*92*1461*2*******************1
PO1*2*2*EA*69.95********IN*420963
PID*F**ZZ*PD*MATTRESSPAD,LYOCELLDOWN,EK
SDQ*EA*92*1461*2*******************2
PO1*3*4*EA*18.95********IN*421160
PID*F**ZZ*PD*PILLOW,RESTANDREAD,KHAKI,COVER
SDQ*EA*92*1514*4*******************3
PO1*4*4*EA*12.25********IN*421198
PID*F**ZZ*PD*PILLOW,DUALLOFT,SIDE,STD
SDQ*EA*92*1508*4*******************4
SDQ*EA*92*1025*4*******************5
SDQ*EA*92*1382*4*******************6
PO1*5*4*EA*12.85********IN*421199
PID*F**ZZ*PD*PILLOW,DUALLOFT,BACK,STD
SDQ*EA*92*1025*4*******************7
CTT*5
SE*26*67500001
GE*1*6750
IEA*1*000006742
ISA*00*          *00*          *01*SENDER1111      *12*RECEIVER123     *070710*1745*U*00201*000006747*0*P*}
GS*FA*SENDER1111*RECEIVER123*20070710*1745*6755*X*004010
ST*997*67550001
AK1*SH*3256
AK2*856*032560001
AK5*A
AK2*856*032560002
AK5*A
AK2*856*032560003
AK5*A
AK2*856*032560004
AK5*A
AK2*856*032560005
AK5*A
AK2*856*032560006
AK5*A
AK2*856*032560007
AK5*A
AK9*A*7*7*7
SE*18*67550001
ST*997*67550002
AK1*IN*3257
AK2*810*032570001
AK5*A
AK2*810*032570002
AK5*A
AK2*810*032570003
AK5*A
AK2*810*032570004
AK5*A
AK2*810*032570005
AK5*A
AK2*810*032570006
AK5*A
AK2*810*032570007
AK5*A
AK9*A*7*7*7
SE*18*67550002
GE*2*6755
IEA*1*000006747
ISA00          00          12SENDER2222   12RECEIVER123     0707101849U004010068776200P>
GSFASENDER2222RECEIVER1232007071018493068776201X004010
ST9970001
AK1SH994
AK2856009940001
AK5A
AK2856009940002
AK5A
AK2856009940003
AK5A
AK2856009940004
AK5A
AK2856009940005
AK5A
AK2856009940006
AK5A
AK2856009940007
AK5A
AK2856009940008
AK5A
AK2856009940009
AK5A
AK2856009940010
AK5A
AK2856009940011
AK5A
AK9A111111
SE260001
GE168776201
IEA1006877620
ISA00          00          12SENDER2222   12RECEIVER123     0707101937U004010000021040P>
GSPOSENDER2222RECEIVER12320070710193737972106X004010
ST8500001
BEG00SA0084700796458720070710
REFX91817304588
REFIA6692600
REFCO020433105
DTM01020070710
TD5UG
N1BTTest9392,539,352
N329560 LILAC RD
N4VALLEY CENTERCA920824011US
PERBDTE7607512212EMtest@test.com
N1STTest9392,539,352
N329560 LILAC RD
N4VALLEY CENTERCA920824011
PERBDTE7607512212EMtest@test.com
PO1011EA69TESK170511VN170511
PIDF08ABBOUD DOWN ALT QN COMF
PO47LB
DTM01020070710
TD5UG
PO1021EA20.45TESK170883VN170883
PIDF08ABBOUD DOWN ALT STD PILLW
PO44LB
DTM01020070710
TD5UG
CTT2
SE270001
GE12106
IEA1000002104
ISA*00*          *00*          *08*SENDER3333     *12*RECEIVER123     *070710*2012*U*00401*000002528*0*P*>
GS*PO*SENDER3333*RECEIVER123*20070710*2012*2528*X*004010VICS
ST*850*2842
BEG*00*RE*1783437**20070710
REF*BT*8768600241
REF*DP*0613HOME TEXTILES
FOB*DF
ITD*05*2*****30
DTM*001*20070720
DTM*010*20070716
DTM*015*20070716
PO1*1*140*EA*74.5*WE*UP*732165407621*CG*41
CTP**RES*250
SDQ*EA*92*0001*8*0002*6*0003*4*0004*2*0005*6*0006*6*0007*6*0009*4*0010*6*0011*6
SDQ*EA*92*0012*6*0013*6*0014*6*0016*6*0017*4*0020*2*0021*4*0022*4*0025*4*0026*4
SDQ*EA*92*0027*4*0028*6*0029*4*0030*6*0031*4*0033*4*0037*2*0055*2*0056*2*0061*4
SDQ*EA*92*0062*2
PO1*2*126*EA*89.5*WE*UP*732165407638*CG*41
CTP**RES*315
SDQ*EA*92*0001*8*0002*6*0003*4*0004*4*0005*4*0006*4*0007*4*0009*4*0010*6*0011*6
SDQ*EA*92*0012*6*0013*6*0014*6*0016*6*0017*2*0020*4*0021*4*0022*2*0025*2*0026*2
SDQ*EA*92*0027*4*0028*6*0029*4*0030*6*0031*2*0033*4*0037*2*0055*2*0056*2*0061*2
SDQ*EA*92*0062*2
CTT*2
SE*23*2842
GE*1*2528
IEA*1*000002528
ISA00          00          12SENDER2222   12RECEIVER123     0707102235U004010000021050P>
GSPOSENDER2222RECEIVER12320070710223539802107X004010
ST8500001
BEG00SA0084700796543420070710
REFX91817604040
REFIA6692600
REFCO020436733
DTM01020070710
TD5UG
N1BTtest9318,257,147
N335 IMPERIAL DR
N4SOUTH BURLINGTONVT054037826US
PERBDTE8028659164EMtest@comcast.net
N1STtest9318,257,147
N335 IMPERIAL DR
N4SOUTH BURLINGTONVT054037826
PERBDTE8028659164EMtest@comcast.net
PO1011EA54TESK170512VN170512
PIDF08ABBOUD DOWN ALT TW COMF
PO46LB
DTM01020070710
TD5UG
CTT1
SE220001
GE12107
IEA1000002105
ISA*00*          *00*          *01*SENDER1111      *12*RECEIVER123     *070710*2125*U*00201*000006751*0*P*}
GS*PO*SENDER1111*RECEIVER123*20070710*2125*6759*X*004010
ST*850*67590001
BEG*00*SA*40361_435**20070710
DTM*037*20070717
N1*BT*0010-Plymouth
N3*6105 Trenton Ln N
N4*Plymouth*MN*55442
PER*BD**TE*763-551-7000
PO1*1*2*EA*68.45********IN*420962
PID*F**ZZ*PD*MATTRESSPAD,LYOCELLDOWN,CK
SDQ*EA*92*1579*2*******************1
CTT*1
SE*12*67590001
ST*850*67590002
BEG*00*SA*41090_143**20070710
DTM*037*20070717
N1*BT*0010-Plymouth
N3*6105 Trenton Ln N
N4*Plymouth*MN*55442
PER*BD**TE*763-551-7000
PO1*1*4*EA*40.95**UP*732165075585*****IN*420737
PID*F**ZZ*PD*PILLOW,BACK SLEEPER,EUROLOFT,STD
SDQ*EA*92*1579*4*******************1
PO1*2*4*EA*26.95********IN*420852
PID*F**ZZ*PD*PILLOW,BACK SLPR,NATURE PREFERENCE,STD
SDQ*EA*92*1448*4*******************2
SDQ*EA*92*1579*4*******************3
PO1*3*4*EA*33.95********IN*420854
PID*F**ZZ*PD*PILLOW,SIDE SLPR,NATURE PREFERENCE,KING
SDQ*EA*92*1579*4*******************4
PO1*4*2*EA*57.95********IN*420961
PID*F**ZZ*PD*MATTRESSPAD,LYOCELLDOWN,QUEEN
SDQ*EA*92*1579*2*******************5
PO1*5*2*EA*69.95********IN*420963
PID*F**ZZ*PD*MATTRESSPAD,LYOCELLDOWN,EK
SDQ*EA*92*1579*2*******************6
PO1*6*4*EA*18.95********IN*421160
PID*F**ZZ*PD*PILLOW,RESTANDREAD,KHAKI,COVER
SDQ*EA*92*1448*4*******************7
SDQ*EA*92*1579*4*******************8
PO1*7*4*EA*12.25********IN*421198
PID*F**ZZ*PD*PILLOW,DUALLOFT,SIDE,STD
SDQ*EA*92*1579*4*******************9
PO1*8*4*EA*12.85********IN*421199
PID*F**ZZ*PD*PILLOW,DUALLOFT,BACK,STD
SDQ*EA*92*1448*4*******************10
SDQ*EA*92*1579*4*******************11
CTT*8
SE*36*67590002
GE*2*6759
IEA*1*000006751
ISA00          00          08SENDER4444     12RECEIVER123     0707110435U004010010001800P?
GSPOSENDER4444RECEIVER1232007071104351000180X004010
ST8500001
BEG00RE25919220070711
REFDP696
REFIA000076489
REFPD07
SACNVIOHPR
DTM01020070717
N1BY921918
N1ST9287449
N1Z7921918
PO116EA39.5IN10541UP732165176862
PO130EA49.5IN10542UP732165176879
CTT2
SE140001
GE11000180
IEA1001000180

• Edited by admdev Thursday, February 26, 2015 3:27 AM

You don't need to do anything.

The EDI Disassembler can handle multiple Interchanges, ISA...IEA, in a stream, file, http whatever, just fine.  It is fully supported by BizTalk and X12.

All other Trading Partner rules apply so still need an Agreement for each set of Identifiers.  Each Interchange is processed under the rules for it's Agreement so you can have different delimiters etc.

• Marked as answer by admdev Thursday, February 26, 2015 8:49 PM

Thanks for your reply boatseller!

How would I process it, though? I know that I have to have the different Parties with their proper Agreements, that I have to have the proper maps and schemas. But how would you process it? Do I create an orchestration to process the file?

How would you process it?

Thanks for your help.

What do you mean 'process' it?

You need some application that does something with at least the 850.  The PO's have to go somewhere.

Do you not already have a process to handle the 850?  And any other transaction types that come in.

Meaning, the fact they they all come in the same transmission is mostly irrelevant. Each transaction would be handled however it would be otherwise.

This will be a new BizTalk integration. There is nothing in place. I'm starting from zero.

When I say how would I process it, I mean the following..

I believe I had already explained on this forum how I used to do EDI with another EDI translator, but if you ask me.... how would you process it the way you used to do EDI, this is how I used to do it.

1. Data is received within the same file and sorted out by the EDI translator to the proper trading partner.

2. Once sorted, within the individual Trading Partner entities, a 997 (good or reject) is generated and placed in the Outgoing documents. 

3. Next, the individual EDI 850 maps read the data and populate it into a temporary DB table.

4. A program (C#, VB.NET, etc.) kicks in, which further analyzes the data(price, quantities, customer on hold, etc.) against customer info in the production DB to flag it as good or invalid. This step is performed so that an E-mail is sent back to the Trading Partner informing of invalid data, if found.

5. Next the good data is imported into the production DB.

6. After the data is processed, the 997s are sent.

I'm oversimplifying the entire process, but those are some of the steps.

My point is... if somebody asks me how I did it from start to end, I can definitely explain every step from receiving 850s to sending 856s, 810s, etc.

I have watched BizTalk Training videos and read some articles and books on this topic, but I have not been able to find one that explains how to deal with more than one trading partner, receiving and sending back.

Hope the experts here can help me with this.

Thanks in advance.

Ok, then you have several things going on.  If the specific question, multiple ISA segments, has been answered, then I recommend you mark this thread such and open a new thread for any specific scenarios you would like advice on.

If you have watched all of the EDI videos, then you should have a good start on how BizTalk processed EDI.

Few points:

• The fact the messages come in as EDI becomes mostly irrelevant since they are translated to Xml.  Then are then handled through Map, Orchestrations, Ports, like any other Message.
• 997/999 Generation is automatic and is a setting on the Agreement.
• There's is nothing special about having multiple Trading Partners or Agreements, you just do.

Don't worry too much about this right now, you have to start somewhere so...just start and you will learn it.

Boatseller,

I really appreciate your input. However being new to the BizTalk world, I would like to get more detail answers.

So say I already have the Parties with their agreements setup. How would you recommend starting the integration? How would other pros here on the forum recommend starting this. Creating one application per Trading Partner or creating an application for incoming messages and another application for outgoing messages. Then creating an Orchestration to process incoming and another for outgoing.

These are the types of answers I'm hoping to get.

Hope you or somebody else here can guide me through the process. I'm sure that once I have two Trading Partners working, the rest will be easier.

Thanks in advance.

For the benefit of future readers, we should try to keep the thread on topic.

If the original question of multiple ISA segments has been answered, please mark the appropriate Answers and open a new thread with any new questions.

For example: How to Organize BizTalk EDI Applications

Will do thanks for your help.

Just wish that somebody would give me more concrete answers as to how to start building my process.

Thanks.

Please, ask the question.  I promise, you will get answers but that is just a different topic.