Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article shows you how to configure SAP source systems with Azure Data Factory. The following prerequisites describe the steps to set up your Azure environment. This article also shows you how to set up the connection in your Business Process Solutions item.
Prerequisites
Required SAP Notes
Before you implement Business Process Solutions, review the following SAP Notes to help prevent common issues during data extraction:
- 2930269: ABAP CDS CDC: Common issues, troubleshooting, and components. (All notes are listed in point 9 of this SAP Note.)
- 3077184: Use new CDS-Views for SAP S/4HANA SD and billing document data.
- 3031375: Customer-specific setting for bucket size in CDC extraction.
Collect information about your source SAP system
To create a source system and establish connectivity, you need the following information:
- Host name or the IP address of the SAP system
- System number
- System ID
- Credentials
Register services in Azure subscription
For Business Process Solutions, register the following providers:
- Azure Storage account (
Microsoft.Storage) - Azure Key Vault (
Microsoft.KeyVault) - Data Factory (
Microsoft.DataFactory)
To finish the registration, follow these steps:
Sign in to the Azure portal.
On the Azure portal menu, search for Subscriptions and select it.
Select the subscription that you want to view.
On the left menu, under Settings, select Resource providers.
Select the Microsoft.KeyVault resource provider.
Select the resource provider and select Register.
Repeat the preceding steps for Microsoft.Storage and Microsoft.DataFactory.
Required permissions in Azure subscriptions
To deploy the required Azure resources for Business Process Solutions, your user account must have specific permissions. You can assign these permissions at either the subscription level or the resource group level. If you assign permissions at the resource group level, you must first create the resource group manually. Then provide the name in the source system configuration within Business Process Solutions.
The following permissions are required:
- Key Vault Secrets Officer Access: Assign Key Vault Secrets Officer access to the subscription for the user who operates Enterprise Insights. Make sure that the access is Permanent and not Time bound.
- Owner Role Assignment: Assign the Owner role in the subscription for the user who operates Enterprise Insights. Make sure that the access is either Permanent or Time bound. If it's Time bound, activate it before you run the configured source system operation.
Create a service principal
In this section, you set up the service principal, which enables Data Factory to access object metadata within Business Process Solutions. Follow the next steps to finish the setup.
To create the following resources, you:
- Create a new service principal.
- Create a new secret for the service principal.
Follow these steps:
Open the Azure portal.
On the left menu, select Microsoft Entra ID.
Go to App registrations and select New registration. Enter the name of the service principal.
Select Register to confirm.
To create a client secret, in App registrations, select your application.
In the Service Principal pane, go to the Certificates & secrets section. Select + New for the client secret. Enter a description of the client secret, and select the validity time. Select Add to confirm.
Copy the value of the secret. The value is stored in the key vault. After you leave this screen, you can't retrieve the secret value again.
Go to the Microsoft Fabric workspace and select Manage Access to add the created service principal as a Contributor in the workspace.
Configure an SAP source system in Business Process Solutions
The first step of configuration is to set up the source system. This step deploys the common artifacts that are required to get started. Follow these steps to configure your source system:
On the home screen, select Configure source system.
Select New source system.
Enter the inputs for the fields:
- Select Azure Data Factory for the connection type.
- Select the subscription and location from the dropdown list.
- Enter unique names for the resource group, Azure Data Factory, Azure Key Vault and Azure Storage account.
In the System Connection section, enter the connection details for your SAP system. Enter the service principal secret that you created in Create a service principal.
Select Create. You can monitor the deployment status by using the refresh button to refresh the page.
After the deployment is finished, you can see the resources that are deployed to your workspace and also the resources that are deployed in your Azure resource group.
Deploy self-hosted integration runtime on an Azure virtual machine
In this section, you deploy the self-hosted integration runtime on an Azure virtual machine (VM). To deploy and configure the self-hosted integration runtime, see Set up a self-hosted integration runtime for the SAP CDC connector. This article covers detailed steps on how to prepare your VM and how to perform connectivity tests. You can also use these steps to configure your VM:
Deploy an Azure VM in the same network or subnet as your SAP system. Direct connectivity between the self-hosted integration runtime and the SAP system is required to extract data.
Install the SAP .NET connector.
Install the Java runtime. For more information, see Download the Java runtime.
Ensure that the
JAVA_HOMEsystem environment variable is set to the JDK folder, not just the JRE folder. You might also need to add the bin folder to your system'sPATHenvironment variable.Install the self-hosted integration runtime. Stop at the registration step.
Open Data Factory and go to Manage > Integration Runtimes.
Select the integration runtime, SAP-IR.
Use the authentication key to continue with the self-hosted integration runtime installation process. Copy the key and finish the setup for the integration runtime on your VM.
After registration is finished, the status of the self-hosted integration runtime changes to Running in Data Factory.