Blogger :
mike hatchs blog
All posts :
All posts by mike hatchs blog
Category :
SAP IDOC
Blogged date : 2005 Dec 23
Today one of our developers responded to a customer inquiry with an excellent summary of some SAP integration solutions and their relative complexities I thought worth sharing. Please note these are subjective figures and do not represent the views of Microsoft Corporation.
Yes, more information will be needed to come up the best and least complex solution for you. This is break down based on the effort of integration I know currently for each solution.
| Architecture | Integration strength | Dependency | Complexities (1 5) | Note |
| BizTalk 2004/SAP adaptor | Full integration suite. No code or minimum code required. | SAP.Net Connector Biztalk 2004 Microsoft.Net and Visual Studio.Net SAP Biztalk Adaptor 2.0 | 3 | New. Need some patient |
| SAP .Net Connector | Low level SDK. Only provide inbound iDoc implementation. You have to develop your own outbound iDoc handler. | Microsoft .Net framework Microsoft visual studio.net | 4 | Flexible and scale. But need dev work on case by case basis |
| Biztalk 2002 and SAP adaptor 1.0 | Full integration suite. | SAP DCOM Component Connector Biztalk 2002 | 3 | Only work with older Biztalk. |
| Flat files with Share folder. | No integration required Full SAP implementation and configuration | None | 2 | |
| SAP Business Connector | SAP implementation. More like Biztalk 2002 with SAP adaptor 1.0 | SAP Business Connector, | 4 | Work well. Competing with Biztalk |
| SAP XI | SAP new product | License required. | ? | New Product and might be the replacement of BCON |
