none
How to setup Party for Multiple GS 02 and same ISA Configuration RRS feed

  • Question

  • I am using BizTalk 2009 and my project is to send outbound 837I and 837P files.  I have 4 types of files for which the ISA 05-08 is same but the GS02 is 110007 for  for 2 files and GS02 is 550005 for other 2 files.

    1. 837I 110007(GS02 = 110007)

    2. 837P 110007(GS02 = 110007)

    3. 837I 550005(GS02 = 550005)

    4. 837P 550005(GS02 = 550005).

    I tried to create 2 parties 1 can take 837P/I-110007 files and other to take 837P/I-550005 files but the when I try to create the 2nd party its throwing me a error saying that ISA6-ISA8 needs to be unique. I changed the ISA06 for the 2nd party and wrote a custom pipeline to update the ISA06 before it writes it to the out folder. Is this the correct method of doing this or is there any other easier method of doing this ?

    • Moved by Ben Cline1Moderator Friday, October 8, 2010 3:04 AM Related to EDI (From:BizTalk Server General)
    Thursday, October 7, 2010 11:51 PM

Answers

  • I would say this is the right way. Party configuration editor will not allow you to set two parties with same ISA06-08 values. So if you are receiving different GS02, you can configure the party with one GS02 and other GS02 you need to handle in using custom pipeline component. We done this for non existent X12 versions and to convert that to existent version so the BizTalk EDI should accept them.
    Best Regards, Vishnu
    • Marked as answer by rkmamidi Friday, October 15, 2010 9:00 PM
    Friday, October 8, 2010 2:32 AM
  • If you are using Orchestration for creating the files. You can use the EDI override properties to address your scenario.

    Step 1: In the Party Configuration :

    Create a party for your receiver.

    Party As Interchange Receiver -> Configure ISA Segment Definition with your ISA05 to ISA08.

    GS and ST Segment Definition -> Configure 837_I (GS02 - 110007) and 837_P (GS02 - 110007 )

    Step 2: In the Orchestration

    Before sending the XML message to Send Port

    Place Message Assignment Shape and place the following code

    sendMsg(EdiOverride.OverrideEDIHeader) = true;
    sendMsg(EDI.DestinationPartySenderQualifier) = "ISA07";
    sendMsg(EDI.DestinationPartySenderIdentifier) = "ISA08";

    sendMsg(EDI.DestinationPartyReceiverQualifier) = "ISA05";

    send277Msg(EDI.DestinationPartyReceiverIdentifier) = "ISA06";

    sendMsg(EdiOverride.GS02) = "110007";  or  sendMsg(EdiOverride.GS02) = "550005";  //based on your condition
    sendMsg(EdiOverride.GS03) = "YOUR RECEIVER";

     

     


    Sathish
    Friday, October 8, 2010 4:07 AM

All replies

  • I would say this is the right way. Party configuration editor will not allow you to set two parties with same ISA06-08 values. So if you are receiving different GS02, you can configure the party with one GS02 and other GS02 you need to handle in using custom pipeline component. We done this for non existent X12 versions and to convert that to existent version so the BizTalk EDI should accept them.
    Best Regards, Vishnu
    • Marked as answer by rkmamidi Friday, October 15, 2010 9:00 PM
    Friday, October 8, 2010 2:32 AM
  • If you are using Orchestration for creating the files. You can use the EDI override properties to address your scenario.

    Step 1: In the Party Configuration :

    Create a party for your receiver.

    Party As Interchange Receiver -> Configure ISA Segment Definition with your ISA05 to ISA08.

    GS and ST Segment Definition -> Configure 837_I (GS02 - 110007) and 837_P (GS02 - 110007 )

    Step 2: In the Orchestration

    Before sending the XML message to Send Port

    Place Message Assignment Shape and place the following code

    sendMsg(EdiOverride.OverrideEDIHeader) = true;
    sendMsg(EDI.DestinationPartySenderQualifier) = "ISA07";
    sendMsg(EDI.DestinationPartySenderIdentifier) = "ISA08";

    sendMsg(EDI.DestinationPartyReceiverQualifier) = "ISA05";

    send277Msg(EDI.DestinationPartyReceiverIdentifier) = "ISA06";

    sendMsg(EdiOverride.GS02) = "110007";  or  sendMsg(EdiOverride.GS02) = "550005";  //based on your condition
    sendMsg(EdiOverride.GS03) = "YOUR RECEIVER";

     

     


    Sathish
    Friday, October 8, 2010 4:07 AM
  • Thanks Satish worked perfectly.
    Friday, October 15, 2010 8:59 PM
  • Hi Satish,

     

    I tried to implement your solution and I don't have EdiOverride nor EDI namespaces appearing in the  message assignment shape. Do I need something like adding a reference?

     

    Thanks.

    Tuesday, March 22, 2011 5:52 PM
  • Jean-Luc Vincent,

    You need to reference "Microsoft.BizTalk.Edi.BaseArtifacts".

    - Christopher

     



    Tuesday, March 22, 2011 7:40 PM
  • Christopher,

     

    I didn't find such a reference. That's what I was looking for.

     

    It looks like it was probably not registered in GAC by the installation done by the techie originally.

    I found the dll in my installation source directories. I probably have other uninstalled dlls as well. There are tons of them...

     

    Thanks.

    BTW, nice dog.

    -JLuc

    Tuesday, March 22, 2011 8:18 PM
  • Hi

    Can I explain how I got it?

    sendMsg(EdiOverride.OverrideEDIHeader) = true;

    That will only say that we are now want to overwrite the header. Don't know why we have to do it (we also could simple replace the values) but OK.
    That solution seems to be cool but I didn't get why do we need to set up the ISA Qualifier again

    sendMsg(EDI.DestinationPartySenderQualifier) = "ISA07";
    sendMsg(EDI.DestinationPartySenderIdentifier) = "ISA08";
    sendMsg(EDI.DestinationPartyReceiverQualifier) = "ISA05";
    sendMsg(EDI.DestinationPartyReceiverIdentifier) = "ISA06";

    ?

    And what does "277" mean? Only a spelling mistake?

    BR


    -kugelschreiber-

    Tuesday, May 15, 2012 3:38 PM
  • How can I access the EDI object into assignment shape? <o:p></o:p>

    When I was using like this sendMsg(EDI.DestinationPartySenderQualifier), through follwoing error:<o:p></o:p>

    identifier EDI does not exist 'unnamed', are you missing as  assembly reference?<o:p></o:p>


    Friday, September 30, 2016 7:37 PM
  • As this thread is very old and marked as Answered, please open a new thread describing you current situation.
    Friday, September 30, 2016 9:17 PM