none
BizTalk Server 2010 - EDI Ehancements RRS feed

Answers

  • Hi Muhammad,

    From BizTalk 2006 R2 to BizTalk 2009 there were several improvements:

    • Control of envelope headers: Flexibility to override envelope headers of the outgoing EDI documents
    • Automatic rollover of control numbers: Having the option to specify a range of EDI control numbers with automatic rollover
    • Configurable content delimiter character
    • Support for multiple batches per party: Allows users to create multiple batches per party with different Batching Criteria
    • Updated reporting to cover all new features

     

    In BizTalk 2010 one of most important enhancement is the new Trading Partner Management

    EDI Pipeline and Context Properties – The new Trading Partner Management feature in BizTalk Server 2010 provides the same capabilities as the EDI Pipeline and Context Properties and replaces these features.

    The way trading partners are managed using BizTalk Server has been completely remodeled in BizTalk Server 2010. While in previous versions of BizTalk Server, a party is created only for the trading partner and not for the partner hosting BizTalk Server, in BizTalk Server 2010 a trading partner must be created for all the trading partners, including the partner hosting BizTalk Server. Similarly, while in previous BizTalk Server versions, while the encoding (X12 and EDIFACT) and transport (AS2) protocol properties were defined at the party level, in BizTalk Server 2010 these properties are defined through agreements.

    See:

     

    Other:

    • Intelligent Mapper: Enhanced user interface for better visualization of maps and to support complex mappings.Reusable parts for improved user productivity. Enhancements to the current functoids.
    • FTPS support - Fully supports RFC4217 (FTPS adapter)
    • FTP and LOB adapters updated

     

    BizTalk 2010 - Deprecated EDI Features

    • EDI Pipeline - Some EDI pipeline properties are fully supported with no feature enhancements in BizTalk Server 2010 but are planned for removal in future versions. The properties are now available as part of the Trading Partner Management user interface in the BizTalk Server Administration console.
    • EDI Context Properties - The following EDI context properties are deprecated in BizTalk Server 2010:
                                               - DestinationPartyID
                                               - DestinationPartyName

     

     


    Sandro Pereira Blog: http://sandroaspbiztalkblog.wordpress.com/ Please mark as answered if this answers your question.
    Wednesday, May 4, 2011 12:40 AM

All replies

  • BizTalk 2006 r2 does not have 5010 EDI schemas shipped out of the box, but BTS 2010 has 5010 schemas shipped with it out of the box. And also the way you set up parties and agreements is different in 2010 as compared to 2006.
    Regards, Pa445
    Tuesday, May 3, 2011 6:25 PM
  • Hi Muhammad,

    From BizTalk 2006 R2 to BizTalk 2009 there were several improvements:

    • Control of envelope headers: Flexibility to override envelope headers of the outgoing EDI documents
    • Automatic rollover of control numbers: Having the option to specify a range of EDI control numbers with automatic rollover
    • Configurable content delimiter character
    • Support for multiple batches per party: Allows users to create multiple batches per party with different Batching Criteria
    • Updated reporting to cover all new features

     

    In BizTalk 2010 one of most important enhancement is the new Trading Partner Management

    EDI Pipeline and Context Properties – The new Trading Partner Management feature in BizTalk Server 2010 provides the same capabilities as the EDI Pipeline and Context Properties and replaces these features.

    The way trading partners are managed using BizTalk Server has been completely remodeled in BizTalk Server 2010. While in previous versions of BizTalk Server, a party is created only for the trading partner and not for the partner hosting BizTalk Server, in BizTalk Server 2010 a trading partner must be created for all the trading partners, including the partner hosting BizTalk Server. Similarly, while in previous BizTalk Server versions, while the encoding (X12 and EDIFACT) and transport (AS2) protocol properties were defined at the party level, in BizTalk Server 2010 these properties are defined through agreements.

    See:

     

    Other:

    • Intelligent Mapper: Enhanced user interface for better visualization of maps and to support complex mappings.Reusable parts for improved user productivity. Enhancements to the current functoids.
    • FTPS support - Fully supports RFC4217 (FTPS adapter)
    • FTP and LOB adapters updated

     

    BizTalk 2010 - Deprecated EDI Features

    • EDI Pipeline - Some EDI pipeline properties are fully supported with no feature enhancements in BizTalk Server 2010 but are planned for removal in future versions. The properties are now available as part of the Trading Partner Management user interface in the BizTalk Server Administration console.
    • EDI Context Properties - The following EDI context properties are deprecated in BizTalk Server 2010:
                                               - DestinationPartyID
                                               - DestinationPartyName

     

     


    Sandro Pereira Blog: http://sandroaspbiztalkblog.wordpress.com/ Please mark as answered if this answers your question.
    Wednesday, May 4, 2011 12:40 AM