none
EDIBatchingOrchestration schema validation issue. RRS feed

  • Question

  • Hi,

    I'm new to EDI and using BizTalk 2010 to batch outgoing EDI messages.

    In my project we are receiving flat file and transforming them in to X12_00401_856 messages inside orchestration and setting necessary properties for Batching like, ToBeBatched =true; BatchId = 12; EDI.EncodingType=0;.

    I am able to instantiate the EDIBatchingOrchestration but its getting suspended with below error.

    Note: In our transformation we are not mapping anything for ST segment as we want this to be set by Party agreement.

    I have used the below link for reference http://biztalkwithshashikant.blogspot.com/2010/09/batching-non-edi-received-documents.html

    Error:

    The batch element is being suspended as it either failed schema validation or context properties are not matching batch definition. The error is : Stopping after the first error !!

    Error: 1 (Miscellaneous error)

                    7: Missing or invalid transaction set control number

    Error: 2 (Miscellaneous error)

                    3: Transaction Set Control Number Mismatch

    Please use the EDI Design Time tools to get a complete list of errors.

    My question:  Can we do custom batching for EDI, by subscribing X12_00401_856 without processing it through EDIRcv pipeline as mentioned in the below link.

    http://biztalkwithshashikant.blogspot.com/2010/09/batching-non-edi-received-documents.html

    Any help appriceated.

    Regards,

    Satendra


    Monday, May 28, 2012 11:52 AM

All replies

  • Hi,

    The article you are referring to is for non EDI documents, I would suggest go through this article. Hope this helps.


    Regards,
    Bali
    MCTS: BizTalk Server 2010,BizTalk Server 2006 and WCF
    My Blog:dpsbali-biztalkweblog
    -----------------------------------------------------
    Mark As Answer or Vote As Helpful if this helps.

    Monday, May 28, 2012 11:59 AM
  •  

    Hi Bali,

    Thanks for instant reply.

    But in project we are receiving Flat file batch(Non EDI document) from Mainframes and by using Flat File dissembler in Receive pipeline i am debatching it and publishing corresponding XML's in MessageBox. I have orchestration with direct bound receive port to subscribing these xml and after receiving XML(Flat file) i am doing transformation to EDI856 schema. 

    Now i am trying to do batching for EDI856 message published by my orchestration on the basis of PartnerId without sending them first out to a file location using send port and receive back using EDIRecieve pipeline and then do batching. I don’t know whether it’s possible or not? But the article by shasikant says it’s possible and I have tried same but getting validation error from EDIBatchingOrchestration.

    I think now you will get more clarity on issue I am facing.

     

    Any help appriceated.

    Regards,

    Satendra

    Tuesday, May 29, 2012 7:00 AM
  • did you read the documentation of out-of-box batching that I shared in my earlier post?


    Regards,
    Bali
    MCTS: BizTalk Server 2010,BizTalk Server 2006 and WCF
    My Blog:dpsbali-biztalkweblog
    -----------------------------------------------------
    Mark As Answer or Vote As Helpful if this helps.

    Tuesday, May 29, 2012 12:40 PM
  • I am having the same issue and the link you provided did not help.

    Can someone assist?

    Monday, July 30, 2012 12:52 PM
  • Can you guys throw some more info like what properties you are setting. Did you tried "batch Override", is that part working?
    Monday, September 24, 2012 7:02 PM
  • Hi Bali,

    This is Senthil Murugan my email id is smurugan@live.com. 8971041053.  I New to EDI 856.  kindly help out how to validated. 

    This is my input file.

    ISA*00*          *00*          *12*2525336321     *ZZ*XXXXXX        *121121*1315*U*00401*000000907*0*P*~
    GS*SH*2525336321*XXXXXX*121121*1315*907*X*04010
    ST*856*0884
    BSN*00*CH000000*20121121*1314
    DTM*011*20121121*1314*GM
    HL*1**S
    MEA*CT*RO*15*RL
    MEA*WT*G*40455*LB
    MEA*WT*N*40455*LB
    MEA*CT*RO*15*PK
    TD3*TL*UMXU*881251
    REF*BM*CH000000
    N1*SF**92*XY
    N1*SO*dfkjkjfkjjkfjdkjfk, INC*91*CROC
    N1*ST*cuddalore*92*tamilnadu
    N1*SU*xyz*1*102235004
    N1*MP*xyz*91*060
    HL*2*1*O
    MEA*CT*RO*15*RL
    MEA*CT*RO*15*PK
    MEA*WT*N*40455*LB
    MEA*WT*G*40455*LB
    REF*LI*0000000
    REF*MI*063276
    PRF*102560
    HL*3*2*D
    LIN*3*GC*0200KSW1*GN*yyyyyyy
    PO4*1*32.375*IN*ROL********72*IN
    MEA*PD*BW*58*LB
    MEA*CT*RO*9*RL
    MEA*CT*RO*9*PK
    MEA*WT*N*24585*LB
    MEA*WT*G*24585*LB
    HL*4*3*I
    LIN*4*RO*11119212402A
    MEA*WT*GW*2745*LB
    MEA*WT*N*2745*LB
    HL*5*3*I
    LIN*5*RO*11119212501A
    MEA*WT*GW*2760*LB
    MEA*WT*N*2760*LB
    HL*6*3*I
    LIN*6*RO*11119212502A
    MEA*WT*GW*2770*LB
    MEA*WT*N*2770*LB
    HL*7*3*I
    LIN*7*RO*11119212601A
    MEA*WT*GW*2720*LB
    MEA*WT*N*2720*LB
    HL*8*3*I
    LIN*8*RO*11119212602A
    MEA*WT*GW*2745*LB
    MEA*WT*N*2745*LB
    HL*9*3*I
    LIN*9*RO*11119212701D
    MEA*WT*GW*2705*LB
    MEA*WT*N*2705*LB
    HL*10*3*I
    LIN*10*RO*11119212701E
    MEA*WT*GW*2720*LB
    MEA*WT*N*2720*LB
    HL*11*3*I
    LIN*11*RO*11119212702D
    MEA*WT*GW*2705*LB
    MEA*WT*N*2705*LB
    HL*12*3*I
    LIN*12*RO*11119212702E
    MEA*WT*GW*2715*LB
    MEA*WT*N*2715*LB
    HL*13*1*O
    MEA*CT*RO*15*RL
    MEA*CT*RO*15*PK
    MEA*WT*N*40455*LB
    MEA*WT*G*40455*LB
    REF*LI*CH170815
    REF*MI*063277
    PRF*102561
    HL*14*13*D
    LIN*14*GC*0200KSW1*GN*FTPAK
    PO4*1*31.5*IN*ROL********72*IN
    MEA*PD*BW*58*LB
    MEA*CT*RO*6*RL
    MEA*CT*RO*6*PK
    MEA*WT*N*15870*LB
    MEA*WT*G*15870*LB
    HL*15*14*I
    LIN*15*RO*11119212701A
    MEA*WT*GW*2650*LB
    MEA*WT*N*2650*LB
    HL*16*14*I
    LIN*16*RO*11119212701B
    MEA*WT*GW*2645*LB
    MEA*WT*N*2645*LB
    HL*17*14*I
    LIN*17*RO*11119212701C
    MEA*WT*GW*2640*LB
    MEA*WT*N*2640*LB
    HL*18*14*I
    LIN*18*RO*11119212702A
    MEA*WT*GW*2650*LB
    MEA*WT*N*2650*LB
    HL*19*14*I
    LIN*19*RO*11119212702B
    MEA*WT*GW*2645*LB
    MEA*WT*N*2645*LB
    HL*20*14*I
    LIN*20*RO*11119212702C
    MEA*WT*GW*2640*LB
    MEA*WT*N*2640*LB
    CTT*20**40455*LB
    SE*109*0884
    GE*1*907
    IEA*1*000000907

    Wednesday, December 26, 2012 11:59 AM
  • Hi Senthil Murugan

    You can delete First Two Line

    i.e

    ISA*00*          *00*          *12*2525336321     *ZZ*XXXXXX        *121121*1315*U*00401*000000907*0*P*~
    GS*SH*2525336321*XXXXXX*121121*1315*907*X*04010

    and last two line

    GE*1*907
    IEA*1*000000907

    then you can validate this using visual studio, using Validate Instance

    Regards

    Mohit Gupta

    Wednesday, December 26, 2012 1:13 PM
  • Hi Mohit,

    i followed those step to validate. unable to validate. can you explain me please?

    Regards


    Murugan

    Monday, January 7, 2013 5:07 AM
  • Using Visual Studion we can validate sample edi with the schema .

    Set the input instance property.

    select edi sample file .

    Right click schema file , Validate instance

    Refer Article

    Regards

    Mohit Gupta

    Monday, January 7, 2013 3:32 PM
  • Using Visual Studion we can validate sample edi with the schema .

    Set the input instance property.

    select edi sample file .

    Right click schema file , Validate instance

    Refer Article

    Regards

    Mohit Gupta

    Friday, March 29, 2013 10:52 AM