Sower SAP ABAP Architecture

In a previous tip, I described how to set up the testing/development environment for connecting SAP 4.6c and SharePoint Portal Server 2003 in order to meet the business needs of displaying SAP data on SharePoint sites.

The key starting point of accessing SAP data is to define a SAPProxy, which is “generated from a standard Web Service Description Language (WSDL) file, a WSDL file included in an SAP interface repository (IFR), or from an SAP server. At run time, the SAP .NET Connector uses these classes to perform and manage communication between the .NET application and the SAP server.” In our first web part, we will invoke one of RFC functions the SAP proxy class provides to get the customer data like below figure shows.

In a previous tip, I described how to set up the testing/development environment for connecting SAP 4.6c and SharePoint Portal Server 2003 in order to meet the business needs of displaying SAP data on SharePoint sites.

The key starting point of accessing SAP data is to define a SAPProxy, which is “generated from a standard Web Service Description Language (WSDL) file, a WSDL file included in an SAP interface repository (IFR), or from an SAP server. At run time, the SAP .NET Connector uses these classes to perform and manage communication between the .NET application and the SAP server.” In our first web part, we will invoke one of RFC functions the SAP proxy class provides to get the customer data like below figure shows.