none
BizTalk Applications RRS feed

  • Question

  • Hi all,

    Getting back to BizTalk after a long ASP.NET project. I am sure there are many EDI professionals in this forum so once again, I am looking for input as to how to properly structure BizTalk Applications, Send\Receive Ports, etc. for many Trading Partners. I am still finding it confusing the way EDI is handled in BizTalk. I have been doing EDI for sometime now and the EDI translators and data mappers I have used are pretty straight forward.

    Can you EDI Coordinators\Specialists explain how you currently handle the EDI in BizTalk? How do you monitor the acknowledgements? Can you explain from receiving an X12 850 to sending a 856 and or 810?

    I have already gone through the EDI walk through, which only talk about a single Trading Partner. I have also watched many training videos on other BizTalk topics (Orchestrations, Schemas, etc.). I can explain how I am used to working with EDI with other EDI translators\mappers, if needed. I am sure somebody's answer will shine the light.

    I am almost ready to give up on BizTalk. Why EDI is so cumbersome in BizTalk?

    Thanks in advance. 

    Thursday, July 10, 2014 3:38 PM

Answers

All replies

  • Well, BizTalk EDI has some idiosyncrasies but it really only appears cumbersome because they try to support as much of the flexibility X12 and EDIFACT provide.

    Outside of EDI though, and 850 to 856 is not different that any other integration app, SAP to SQL Server for example.

    In BizTalk, EDI is kept at the edge as much as possible and everything else, Maps, Orchestrations, Rules, etc. is available to any other application but are not at all required for EDI.  Other EDI translators seem easier because, frankly, they don't offer as much.

    Since you've done the tutorials, I recommend you just star to develop you application and see where it get you.  Recommendations at this point may only confuse the situation because every scenario is different.

    Thursday, July 10, 2014 5:06 PM
  • boatseller,

    Thank you for you reply.

    How confusing will it be?

    I am going to briefly explain a scenario of one of the EDI Translators I have worked with.

    1. You create an EDI connection entity, VAN, AS2, FTP, etc.

    2. Within this connection entity, you have Trading Partners that utilize this connection.

    3. Within the individual Trading Partner entities, you have EDI documents that are exchanged between you and them. At the same time, these TPs have EDI settings (in Biztalk these are the interchange settings).

    4. Within the Trading Partner's documents you specify the direction, In or Out.

    5. When EDI data is received from a connection (for one or multiple TPs within the same file), the data is sorted to the proper TP and a 997 is generated.

    6. After the data is placed in individual TPs, the mapper kicks in to process the data.

    7. After the data is processed, the 997s are sent.

    Of course there is plenty of details within these steps, but I would like to know how the BizTalk\EDI pros have built the EDI flow from Applications, Send\Receive ports, to Orchestrations(if needed), etc.

    If, you ask me for details as to how I built the EDI flow within the EDI translator I worked with, I would gladly explain it. Perhaps, that's where my confusion is. That I am expecting BizTalk to be as simple and straight forward as an EDI translator, when BizTalk is more than that.

    Thanks. 


    Thursday, July 10, 2014 5:44 PM
  • So, everything you describe, you have to do in BizTalk.  Those are mostly all EDI constructs which any EDI platform has to support.

    The only real difference is the UI and maybe some minor paradigm differences.  Ports, Trading Partners (Agreements), Schemas, all the same.

    It will all come together once you start doing it.

    Yes, BizTalk is much, much more than a stand alone EDI platform, but configuring the EDI relationships cannot be that much different because the structure and requirements of X12 or EDIFACT don't change from platform to platform.  And you don't have to use all the extra BizTalk capabilities if you don't want to.

    So, again, just start.

    • Marked as answer by admdev Monday, July 14, 2014 3:20 PM
    • Unmarked as answer by admdev Monday, July 14, 2014 3:20 PM
    • Proposed as answer by Angie Xu Wednesday, July 16, 2014 1:52 AM
    Thursday, July 10, 2014 7:07 PM
  • Hi,

    Whatever you described is actually mandate for having EDI communication irrespective of tool been used.

    As suggested, start to do it - I would ask you to go through following (if you have not)

    BizTalk EDI Videos and MSDN walkthrough developing EDI solutions


    Maheshkumar S Tiwari|User Page|Blog|BizTalk Server : How Map Works on Port Level

    • Proposed as answer by Angie Xu Wednesday, July 16, 2014 1:52 AM
    • Marked as answer by Angie Xu Monday, July 21, 2014 1:30 AM
    Friday, July 11, 2014 4:28 AM