NET Connector

Enterprise Resource Planning Portal

ERPGenie.COM -> Interfaces -> .NET Connector

The SAP .NET Connector offers developers to expose BAPIs and remotely-enabled function modules to any .NET application (inside-out). You now also can access .NET components from with a mySAP.com application (outside-in).

Links

SAP Connectors - SAP Official connectors site (need OSS logon)
SAP Interfaces club - A place to discuss SAP Interfacing technology issues
ASP Training CDs - .NET training CDs
.NET Connector FAQ - Frequently asked questions
BIT528 .NET Connector Programming (five days course). Target audience: Developers who want to use BAPIs, RFC function modules and/or IDocs to build Internet, Intranet or Desktop .NET applications that communicate with SAP components
Read SAP-R/3 Tables with VB or VB.Net - Saplink.ocx/SAPLink.Net and ASPSaplink: a VB oxc/VB.net DLL and a IIS DLL, which can access tables from a R/3 system by ADODB Recordset or .NET Datatables. And how can that be done exactly? The RFC functions in the R/3 contain routines, which make it possible to bring in and let run an ABAP with SAP automation or the SAP .Net connector. The output list of a particularly produced ABAP is written into a temporary data base or data table. This again manufactures the basis of the ADO/DAO/Datatable / .Net recordsets.

SAP .NET Connector 1.0.2 is now released! (January 2004)

"At design-time the new Proxy Wizard for Visual Studio .NET allows the integration of SAP business data and processes into .NET applications in a very comfortable and intuitive way. The Proxy Wizard will interactively generate proxy classes in C# and add them to your .NET project. You then can access all properties, methods and even table structures from your .NET application independently of your preferred .NET language (C#, VB or any other supported language). Generated code for logon and connecting to an SAP system as well as IntelliSense support facilitate the process of building your first application. All this is taking place within the familiar Visual Studio .NET development environment.

At run-time the SAP .NET Connector will perform and manage all necessary communication between the .NET application and the SAP server. Transparent for the application both SOAP or SAP RFC can be used as communication protocols. Transactional RFC or queued RFC are supported. For communication security you can use Kerberos, X.509 certificates or Microsoft Passport.

Availability

Currently, the SAP .NET Connector is a beta product. A date for the general availability for the SAP .NET Connector has not been determined yet. However, we expect only very minor changes between this beta and the final product. As soon as a date is fixed, we will inform you either via the SAP Service Marketplace or persons, who have registered for the download, via email.

The SAP .NET Connector works with all SAP application servers starting with release 4.0B, which means access to .NET applications for all existing SAP R/3 systems as well as for the new Web Application Server."

All product names are trademarks of their respective companies. ERPGenie.COM, Inc. is in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any other SAP trademarks are registered trademarks of SAP AG in Germany and in several other countries.
Every effort is made to ensure content integrity. Use information on this site at your own risk.