none
837I drop and generate xml simple scenario RRS feed

  • Question

  • I have a valid 837I file. i configured two ports to receive edi file using edireceive pipeline and send port with xmltransmit pipeline. when i drop the file, i got error for party so i configured the party properly. Now i am getting error that schema not found, make sure schema is deployed correctly. My question is, In BizTalk 2009, do we need to deploy a schema copy in BizTalk application? I used to run the same simple scenario in BizTalk 2006 before R2 using HIPAA accelerator. Now even i deployed the schema copy x12_4010_837.xsd, i get the same error. here is the error detail. as per error, it is looking for 837_i schema but in BizTalk 2009, i can only see _837.xsd schema.

    Error: 1 (Miscellaneous error)

                    6: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_837_I" failed. Verify the schema deployed properly.

     


    Moonis Tahir MCSD.net, MCTS Sharepoint 07 (Dev & Config), MCTS BizTalk 06, MCTS SQL 2005.
    Friday, May 1, 2009 5:07 PM

Answers

  • Hi Moonis,

    You have to deploy the HIPAA 837 schema at C:\Program Files\Microsoft BizTalk Server 2009\XSD_Schema\EDI\HIPAA\00401A1\Claim-Institutional_837I. Deploy the multiple schema if you want to have subdocument splits otherwise deploy the schema in the single folder. If you deploy the schema at the above mentioned location the root name of the schema deployed will be X12_4010_837_I.

    Regards,
    Kowshik Palivela
    Sunday, May 3, 2009 11:44 AM
  • Thanks for the reply. I verified that schema was already in your mentioned location. I did copy the schema from above location again to my solution. Atleast this schema not deployed issue went away.

    But i started getting other issues of EDI that segment not in proper sequence etc. Since i have couple of Inbound 837 files. so i tried all of them. It did not work. I was using BizTalk 2009 Beta version. I created another VM of 2006 R2. All of my 837 files worked perfectly there.
    Since it worked on 2006R2. i just completed my assignment for 837 files and have handed over to my team to add BAM stuff on top of it.


    Moonis Tahir MCSD.net, MCTS Sharepoint 07 (Dev & Config), MCTS BizTalk 06, MCTS SQL 2005.
    • Marked as answer by Moonis Tahir Tuesday, May 12, 2009 3:02 PM
    Tuesday, May 12, 2009 3:02 PM

All replies

  • link says that i have deployed two versions of the schema. while i mentioned above that whether i deploy the schema or i dont deploy the schema, it gives me the same message. it is asking for 837_I schema while in BizTalk 2009 there is only one schema XSD for 837.
    Moonis Tahir MCSD.net, MCTS Sharepoint 07 (Dev & Config), MCTS BizTalk 06, MCTS SQL 2005.
    Friday, May 1, 2009 7:58 PM
  • Hi Moonis,

    You have to deploy the HIPAA 837 schema at C:\Program Files\Microsoft BizTalk Server 2009\XSD_Schema\EDI\HIPAA\00401A1\Claim-Institutional_837I. Deploy the multiple schema if you want to have subdocument splits otherwise deploy the schema in the single folder. If you deploy the schema at the above mentioned location the root name of the schema deployed will be X12_4010_837_I.

    Regards,
    Kowshik Palivela
    Sunday, May 3, 2009 11:44 AM
  • Thanks for the reply. I verified that schema was already in your mentioned location. I did copy the schema from above location again to my solution. Atleast this schema not deployed issue went away.

    But i started getting other issues of EDI that segment not in proper sequence etc. Since i have couple of Inbound 837 files. so i tried all of them. It did not work. I was using BizTalk 2009 Beta version. I created another VM of 2006 R2. All of my 837 files worked perfectly there.
    Since it worked on 2006R2. i just completed my assignment for 837 files and have handed over to my team to add BAM stuff on top of it.


    Moonis Tahir MCSD.net, MCTS Sharepoint 07 (Dev & Config), MCTS BizTalk 06, MCTS SQL 2005.
    • Marked as answer by Moonis Tahir Tuesday, May 12, 2009 3:02 PM
    Tuesday, May 12, 2009 3:02 PM