SAP Connector () is a Enterprise connector which provides a set of actions and triggers to connect to your SAP Service. Ref: SAP - Connectors | Microsoft Learn
The SAP connector supports the following message and data integration types from SAP NetWeaver-based systems:
Intermediate Document (IDoc)
Business Application Programming Interface (BAPI)
Remote Function Call (RFC) and Transactional RFC (tRFC)
The SAP connector uses the SAP .NET Connector (NCo) library.
To use the available SAP trigger and SAP actions, you need to first authenticate your connection. You can authenticate your connection with a username and password. The SAP connector also supports SAP Secure Network Communications (SNC) for authentication. You can use SNC for SAP NetWeaver single sign-on (SSO), or for additional security capabilities from external products.
2. Connecting and Creating a Workflow:
- Create a new Logic App Standard. Ref: Create Standard workflows in single-tenant Azure Logic Apps with the Azure portal - Azure Logic Apps...
- Upload all required SAP Private DLLs as Client/SDK Assembly (.NET Framework). See below for known issue with DLLs larger than 4 MB.
All SAP Libraries (like sapnco.dll, sapnco_utils.exe, libicudecnumber.dll, rscp4n.dll, also visible here SNC's sapcrypto.dll, sapgenpse.exe, slcryptokernel.dll which are discussed later below) were uploaded to Assemblies.
- Add an SAP Action to the workflow.
- Create a connection (Refer Section 2.2) and run the workflow.
2.2 Creating SAP Connections:
2.2.1 Using Username and Password:
- You can create a simple Username and Password connection by selecting 'Auth Type' as 'Basic' and providing required fields in 'Add Connection' pane.
- Then click Create.
2.2.2 Using SNC
- You can create a SNC connection by selecting 'Auth Type' as 'Logon Using SNC' and providing required fields in 'Add Connection' pane.
- For SNC to work properly, you need to upload SAP Libraries namely (sapcrypto.dll, sapgenpse.exe, slcryptokernel.dll) using Assemblies pane in Azure portal.
- For SNC Partner Name, enter the backend's SNC name. For example,
p:CN=DV3, OU=LA, O=MS, C=US.
- For SNC Certificate, enter your SNC client's public certificate in base64-encoded format. Don't include the PEM header or footer. Don't enter the private certificate here because the PSE might contain multiple private certificates, but this SNC Certificate parameter identifies the client certificate that must be used for this connection.
- Configure PSE settings. For PSE, enter your SNC PSE as a base64-encoded binary.
- The PSE must contain the private client certificate, which thumbprint matches the public client certificate that you provided in the previous step.
- The PSE may contain additional client certificates. We recommend however that you create separate Workflow applications if you intend to authenticate with different client certificates.
- The PSE must have no PIN. If needed, set the PIN to empty using the SAPGENPSE utility.
- Then click Create.
3. Known Issues
- Assemblies tab doesn't allow uploading libraries above 4MB. As a workaround you can follow steps below:
All SAP libraries can be uploaded to
site/wwwroot/lib/builtinOperationSdks/net472/* using kudu tool.
- Open Kudu tool:
- Navigate to
- Create Directory
lib/builtinOperationSdks/net472/ (if it does not already exist):
- Upload all your SAP/SNC assemblies to
NOTE: SAP Connector is in Preview and doesn't guarantee SLA and latency requirements.