none
No matching group could be found for transaction set with DocType RRS feed

  • Question

  • I have two GS and ST segment definitions for a Party in Biztalk. The GS and ST definition for the 5010 834 allows us to create 5010 834 files. However, when I try to create a 5010 820 file, I get the message below. Both 834 and 820 schemas are deployed correctly.  We have a custom pipeline with Pre-Assembler which "promotes" the filename and sets ST03 to the correct value.

    Why is the 834 file being generated but the 820 generates the error message at the bottom of this post?

                    System.Xml.XmlNodeList ST01Elementlist;
                    string filetype;
                    ST01Elementlist = TempXML.GetElementsByTagName("ST01_TransactionSetIdentifierCode");
     
                    filetype = ST01Elementlist.Item(0).InnerXml;
                    if (filetype == "834") {
                        System.Xml.XmlNodeList ST03Elementlist;
                        string filename;
                        ST03Elementlist = TempXML.GetElementsByTagName("ST03_ImplementationConventionReference");
                        filename = ST03Elementlist.Item(0).InnerXml;
                        //Promote the filename
                        inmsg.Context.Promote("ReceivedFileName", "http://schemas.microsoft.com/BizTalk/2003/file-properties", System.IO.Path.GetFileName(filename));
                        ST03Elementlist[0].InnerXml = "005010X220A1";
                        TempXML.Save(vs);
                        vs.Position = 0;
                        inmsg.BodyPart.Data = vs;
                    };
                    if (filetype == "820")
                    {
                        System.Xml.XmlNodeList ST03Elementlist;
                        string filename;
                        ST03Elementlist = TempXML.GetElementsByTagName("ST03_ImplementationConventionReference");
                        filename = ST03Elementlist.Item(0).InnerXml;
                        //Promote the filename
                        inmsg.Context.Promote("ReceivedFileName", "http://schemas.microsoft.com/BizTalk/2003/file-properties", System.IO.Path.GetFileName(filename));
                        ST03Elementlist[0].InnerXml = "005010X218";
                        TempXML.Save(vs);
                        vs.Position = 0;
                        inmsg.BodyPart.Data = vs;
                    }
                    if (filetype == "835")
                    {
                        System.Xml.XmlNodeList ST03Elementlist;
                        string filename;
                        ST03Elementlist = TempXML.GetElementsByTagName("ST03_ImplementationConventionReference");
                        filename = ST03Elementlist.Item(0).InnerXml;
                        //Promote the filename
                        inmsg.Context.Promote("ReceivedFileName", "http://schemas.microsoft.com/BizTalk/2003/file-properties", System.IO.Path.GetFileName(filename));
                        ST03Elementlist[0].InnerXml = "005010X221";
                        TempXML.Save(vs);
                        vs.Position = 0;
                        inmsg.BodyPart.Data = vs;

                    }

    A message sent to adapter "FILE" on send port "Write Files Out TCMC 820 CareOregon" with URI "\\prdfiles\files\cco\tcmc\Outbound\CareOregon\%SourceFileName%" is suspended.

     Error details: There was a failure executing the send pipeline: "FileNamePromotion.SendEDI, FileNamePromotion, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bc090513402c5683" Source: "EDI assembler" Send Port: "Write Files Out TCMC 820 CareOregon" URI: "\\prdfiles\files\cco\tcmc\Outbound\CareOregon\%SourceFileName%" Reason: While sending X12 message to party with name , no matching group could be found for transaction set with DocType http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_820b 

     MessageId:  {DDB7ED2E-9B97-484E-A839-DC4CB166C2C7}

    InstanceID: {B3C3FC80-1938-4D92-813E-7C549CBF8DB2}

    Friday, August 31, 2012 4:23 PM

Answers