Skip to Content

More SAP .NET Connector 2.0 News

SAP .NET Connector 2.0 (final) is available for download

You need Visual Studio Professional (or higher) to install.

If you have a older version of SAP .NET Connector, deinstall it first. Also delete the “SAP Proxy” toolbox tab with all items.
Deinstallation of SAP .NET Connector 1.x can cause problems with Visual Studio. To fix them, execute the following command:
regsvr32 "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\vcpackages\csproj.dll"

As the things work fairly different from Version 1.0, here some tips to get started:

– Download the ZIP and extract the MSI.
– Installl it. You need Visual Studio 2003 beeing installed.
– Start Visual Studio.
– You see the documentation in “Content”.
– Create or open a VB or C# project.
– Add new item “SAP Connector Proxy” (go down the list).
– Open Server Explorer.
– Select the “Data Connections” node and click on “Refresh” button. Do not right click and select “Refresh”, but click the small button on top of the Server Explorer Window. You should see the SAP root node. If you still don’t see it, perhaps you have a “Standard” Edition of Visual Studio that is not supported.
– Add your SAP Server nodes and drag Functions or BOR objects to the designer.

You must be Logged on to comment or reply to a post.
  • I created my connection and call manually in code.  When I call the SAPProxy object I get an error:  “An unhandled exception of type ‘SAP.Connector.RfcException’ occurred in sap.connector.rfc.dll.

    Here’s my code:
            ‘ Create Variables
         Dim CustomerBO As New ZDISPLAY
            Dim CustTable As New ZBAPICUSDISTable
            Dim CustReturn As New SAP.Connector.BAPIRET1
            Dim SAPDest As New SAP.Connector.Destination
            Dim rsItems As New System.Data.DataTable

            ‘ Setup Connection Information for our call into SAP BAPI Object
            SAPDest.AppServerHost = strSession
            SAPDest.Username = strUser
            SAPDest.Password = strPass
            SAPDest.Language = strLang
            SAPDest.Client = strClient
            SAPDest.SystemNumber = “0”
            CustomerBO.Connection = New SAP.Connector.SAPConnection(SAPDest)

            ‘Call the SAP BAPI
            CustomerBO.ZCustomerDisplay1(strSoldTo, strShipTo, strSalesOrg, strDistch, strDivision, strOrdType, CustReturn, CustTable)

    • As you may be aware, SAP .NET Connector version 2.0 doesn’t work from within

      VS.NET 2005. It’s impossible to use the proxy generator wizard in the new VS


      For those of you interested, we’ve developed a NEW SAP .NET Connector to be

      used with VS.NET 2005. It’s fully build with C# & .NET Framework 2.0 and

      doesn’t require Java runtime at all (as SAP’s Connector does.) providing

      seamless SAP interface programming .


      – Execute BAPIs and RFCs with few lines of code.
      – Send and receive IDocs.
      – Call .NET functions from ABAP programs using the RFC Server classes.
      – Supports RFC & SOAP for full integration in SAP NetWeaver scenarios.
      – Read SAP tables directly
      – Generate and execute ABAP code on the fly.
      – Use Batch Input to execute tracsactions in SAP.

      It provides a far more natural way of interface programming trought exposing

      each function with objects such as Imports/Exports/Tables/Structures, common

      elements to ABAP programmers.

      Wizard generated code is more legible and maintanable than classic SAP .NET

      Connector Wizard’s one.

      We have a license that provides full source code, many examples &

      documentation at a very competitive price.

      Please feel free to send questions and comments to


      Ing. Dante R. Otero

  • Hello,

    I have to suggestions for improvements for the proxy code generation feature of .Net Connector 2.0:

    – If an RFC function does not expect any parameter (it just clears some tables, for example), the (VB) code is generated as
    “Public Overridable Sub Z_Mm_SomeName ( _)”
    The “_” should be removed automatically.

    – If an RFC function expects parameters that have the same name as keywords in the programming language used (VB in my case), the properties should be put into parenthes:
    “Public Property Ctype As String” should become “Public Property [Ctype] As String”

    All other things work great, the .Net Connector 2.0 is a major improvement over the 1.0 release.

    • Thanks for the suggestions.
      – The “_” problem is a bug that is fixed in the “refresh” version at OSS note “506603”.
      – I didn’t know about the trick with ‘[‘ decoration. However I know about the problem with VB keyword conflicts. The easy workarround is to use the designer (not the generated code) and customize the name. All names (functions, fields, parameters) can be customized. To make it even easier, there is a list of keywords that will be “auto customized” by appending a “0”, e.g. a parameter called “Return” would be automatically renamed to “Return0”. I will extend the list to include CType.

      BTW: For further discussion, please better use the Forum.