Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
EDI debatching

Answered EDI debatching

  • Friday, April 27, 2012 3:08 PM
     
     
    Sign In to Vote
    0

    Hi

    I have EDI 834  file has 137Mb all the details within one ST-SE, when i convert them into xml 1 GB with edi dissembler. but it is failing to Load in the Oracle each member detail stored in 6 tables. it works till 27mb not more than that. so i tried to debatch the one ST-Se into multiple ST-SE (using sequential convoy in the prchestration) in the decode statement using String and String Builder . but it is taking long time to debatch . it stays in the receive location for days. it works for small file. the systems has no memory issue. high end systems .

    any suggestion most welcome. We might get 200MB in single ST-SE in future .

    thanks in advance

    rameshkumar singh

     

All Replies

  • Saturday, April 28, 2012 5:03 AM
     
     Answered
    Sign In to Vote
    0

    Hi,

    Have you tried debatching in the pipeline component as that would help reducing the time it takes to debatch.

    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.

     
  • Wednesday, May 02, 2012 1:57 PM
     
     Answered
    Sign In to Vote
    0

    Hi

    Are you using single or multiple schema?

    EDI Disassembler debatch 834 at INS segment in case of multiple schema. Refer Splitting HIPAA Subdocuments. Also, instead of using sequential convoy which becomes really slow in case large messages as it persist all messages until orchestration instance completes, you can use ordered deleivery on subscribing send ports.

    I used following approach to process 834 messages 70K+

    1. Debatch EDI using multiple schema in receive port and Map it to generic canonical schema.

    2. subscriber send port to above receive port and schema and pass complete message into SQL SP.

    3. work on canonical message in SP.

    It avoids orchestration and provide loose coupling of EDI message with DB.

    Thanks With Regards, Bharat Bhatia Please Mark This As Answer If This Helps You. http://xs2bharat.wordpress.com/

     
  • Thursday, May 03, 2012 4:13 AM
     
     
    Sign In to Vote
    0

    As DPS Bali said implementing rebatching in pipeline would be much faster in Pipeline. And it takes very less memory because it will work on the EDI file rather than the xml file.