

SAP has now announced that a new version 3.0 is planned to be released in December 2010 timeframe. NET Connector runtime using RFCs or HTTP/SOAP/XML. Your applications will then communicate with SAP through the. NET proxy classes using the integrated Proxy Wizard. NET Connector interacts with SAP via BAPIs, RFCs, IDocs or asynchronous web service calls and is fully integrated with Visual Studio. NET is the preferred development platform. Many companies use this approach for "Point-to-Point" integration with SAP whereĪ custom interface is required and. NET technologies which provides the technical interoperability required to build. NET Connector is an SAP product based on Microsoft. If you were creating a custom "Point-to-Point" solution without Biztalk, you would need to build each of these blocks of functionality. Provides reliable, performant and secure data transmissions. I described my experiences with it inĪpply WCF BizTalk Adapter Pack to service-enable SAP BAPI/RFC's blog entry.īizTalk provides transformation(mapping) capabilities, durable messaging (retries, persistence), monitoring(MOM,SCOM)/Tracking(HAT,BAM) and management of of Business Process between multiple systems.
SAP CONNECTOR 3.0 DOWNLOAD ISO
Given that, dependent on situational it may still be better to go for a custom approach iso BizTalk: As earlier replied, if doing a custom p2p you will have to implement this interoperability plumping yourselves. The process you describe comes OOTB with BizTalk, via the available SAP adapter, data transformation capabilities, and SQL adapter.
