none
837 Inbound Processing Error with GS08 Segment RRS feed

  • Question

  • When attempting to process an inbound 837I document, it is being sent with BOTH an A1 and an A2 identifier in the GS08 property. However, the schema definition only defines one of them as possible (A1 for I and A2 for P). The problem is that some I customers use A2 and vice-versa). 

    I have updated both the schema as well as the parties configuration to allow for both A2 and A1 in the GS08 segment, but they continue to throw errors when attempting to process the inbound messages.

    Thoughts? 

    Monday, May 23, 2011 5:50 PM

Answers

  • That error has to do with a missing schema. Look in all artifacts and see if you can find the 5010 schema. If you do, look at the application that has it and make a refernece to it. If you dont, you need to deploy the schema. Also the GS08 for 5010 I is 005010X223A2. Good luck.
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Actually. Microsoft released a cumulative BizTalk 2010 pack 1 update just yesterday... and you know what. It fixed our A2/A1 issue (at least our inital pass was successful). I'll know more as we do our testing but for now, it would appear that the update fixed it.
    • Marked as answer by Kevin.Orbaker Tuesday, May 24, 2011 4:25 PM
    Tuesday, May 24, 2011 4:24 PM

All replies

  • What are the errors? Typically in that situation, I would recomend telling your trade partners to use A1. I am not aware of an A2 or P for GS08. Not sure where you are getting A2 or P for GS08. Are you using the HIPAA guides?
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Monday, May 23, 2011 6:49 PM
  • Carlos, Thanks for the reply. Here is the error message... A message received by adapter "FILE" on receive location "Receive Location1" with URI "C:\BizTalkTest\Sample\Input\*.*" is suspended. Error details: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error: Error encountered during parsing. The X12 transaction set with id '' contained in functional group with id '678988', in interchange with id '000678988', with sender id '75276000 ', receiver id '205498481 ' is being suspended with following errors: Error: 1 (Miscellaneous error) 6: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00501_837" failed. Verify the schema deployed properly. . The sequence number of the suspended message is 1. MessageId: {65B68CB4-0081-4BA1-8A71-77D8FB0A11E1} InstanceID: {17068512-1233-4386-B1E1-3AF2BBDF36D6}
    Monday, May 23, 2011 8:59 PM
  • That error has to do with a missing schema. Look in all artifacts and see if you can find the 5010 schema. If you do, look at the application that has it and make a refernece to it. If you dont, you need to deploy the schema. Also the GS08 for 5010 I is 005010X223A2. Good luck.
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Tuesday, May 24, 2011 12:04 PM
  • That error has to do with a missing schema. Look in all artifacts and see if you can find the 5010 schema. If you do, look at the application that has it and make a refernece to it. If you dont, you need to deploy the schema. Also the GS08 for 5010 I is 005010X223A2. Good luck.
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Actually. Microsoft released a cumulative BizTalk 2010 pack 1 update just yesterday... and you know what. It fixed our A2/A1 issue (at least our inital pass was successful). I'll know more as we do our testing but for now, it would appear that the update fixed it.
    • Marked as answer by Kevin.Orbaker Tuesday, May 24, 2011 4:25 PM
    Tuesday, May 24, 2011 4:24 PM