Hello EDI World!
Today I respond to THE most often asked question: feature comparison of Edi support across the various releases of BizTalk Server.
The comparison was put together by me along with Microsoft and Partner field representatives with the objective of presenting an unbiased perspective on how the feature set has evolved over various releases.
I truly believe that the R2 Edi offering is very robust and ‘enterprise’ ready; the claim is substantiated by a very impressive set of Beta customers including Microsoft IT.
As always comments and questions are welcome.
Feature Support across versions
BTS 2006 R2
ISA Segment modification at transaction set
*Supported via creating TransactionSet specific Bts Party
ISA11: US or other standard type
ISA12: Interchange Control Version
ISA13: Interchange Control Number (incrementing number)
ISA15: Test or Production
GS Segment modification at document/transaction level
GS sender/receiver IDs allowed to be different than ISA
Inbound Document IDs different than ISA & GS Outbound IDs
GS01: Ability to change type of document
GS04: Date (Ability to change format)
*UI to select format as: CCYYMMDD and YYMMDD
GS05: Time (Ability to change format)
*UI to select format as: HHMM, HHMMSS and HHMMSSdd
GS06: Change the control number
GS07: Agency Code
GS08: Able to put in standards version
Custom EDI Schemas
*Including creating Party based off templates
EDI document routing via document definition
Automatic 997’s to trading partners
*Via party specific configuration.
Outbound EDI reliable messaging via 997’s
*D93 to D05 per ISO 9735 v4.1
*2040 to 5030
Ability to remove enumerators/codelists
Can migrate BTS02 custom XDR EDI schemas to EDI repository
* Migration support BTS04 onwards
Outbound Batching (accumulating multiple transaction types in a single transaction)
*Supports multiple release paradigms: Schedule, Count and External Triggered.
Inbound Batching – Interchange XML (preserving an incoming ‘batched’ interchange) or Transaction Set XML based off configuration options
*This is in addition to supporting inbound-debatching; i.e., splitting interchange into individual Transaction Set Xml.
Interchange and Transaction Set Generation and Validation in Design Time via BTS Editor in VS
TA1 (Technical ACK) Generation and Reconciliation
Optional EDI and XSD Validation flags
Document format/definition at GS level