Connect to and manage SAP ECC in Azure Purview

This article outlines how to register SAP ECC, and how to authenticate and interact with SAP ECC in Azure Purview. For more information about Azure Purview, read the introductory article.

Supported capabilities

Metadata Extraction Full Scan Incremental Scan Scoped Scan Classification Access Policy Lineage
Yes Yes No No No No Yes**

** Lineage is supported if dataset is used as a source/sink in Data Factory Copy activity


  • An Azure account with an active subscription. Create an account for free.

  • An active Purview resource.

  • You will need to be a Data Source Administrator and Data Reader to register a source and manage it in the Purview Studio. See our Azure Purview Permissions page for details.

  • Set up the latest self-hosted integration runtime. For more information, see the create and configure a self-hosted integration runtime guide.


    Scanning SAP ECC is a memory intensive operation, you are recommended to install Self-hosted Integration Runtime on a machine with at least 128GB RAM.

  • Ensure JDK 11 is installed on the virtual machine where the self-hosted integration runtime is installed.

  • Ensure Visual C++ Redistributable for Visual Studio 2012 Update 4 is installed on the self-hosted integration runtime machine. If you don't have this update installed, you can download it here.

  • Download the 64-bit SAP Connector for Microsoft .NET 3.0 from SAP's website and install it on the self-hosted integration runtime machine. During installation, make sure you select the Install Assemblies to GAC option in the Optional setup steps window.


  • The connector reads metadata from SAP using the SAP Java Connector (JCo) 3.0 API. Make sure the Java Connector is available on your virtual machine where self-hosted integration runtime is installed. Make sure that you are using the correct JCo distribution for your environment. For example: on a Microsoft Windows machine, make sure the sapjco3.jar and sapjco3.dll files are available.


    The driver should be accessible to all accounts in the VM. Do not install it in a user account.

  • Deploy the metadata extraction ABAP function module on the SAP server by following the steps mentioned in ABAP functions deployment guide. You will need an ABAP developer account to create the RFC function module on the SAP server. The user account requires sufficient permissions to connect to the SAP server and execute the following RFC function modules:

    • STFC_CONNECTION (check connectivity)
    • RFC_SYSTEM_INFO (check system information)


This section describes how to register SAP ECC in Azure Purview using the Purview Studio.

Authentication for registration

The only supported authentication for SAP ECC source is Basic authentication.

Steps to register

  1. Navigate to your Purview account.

  2. Select Data Map on the left navigation.

  3. Select Register

  4. On Register sources, select SAP ECC. Select Continue.

    register SAPECC options

On the Register sources (SAP ECC) screen, do the following:

  1. Enter a Name that the data source will be listed within the Catalog.

  2. Enter the Application server name to connect to SAP ECC source. It can also be an IP address of the SAP application server host.

  3. Enter the SAP System number. This is a two-digit integer between 00 and 99.

  4. Select a collection or create a new one (Optional)

  5. Finish to register the data source.

    register SAPECC


Follow the steps below to scan SAP ECC to automatically identify assets and classify your data. For more information about scanning in general, see our introduction to scans and ingestion.

Create and run scan

  1. In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it is not set up, use the steps mentioned here to create a self-hosted integration runtime.

  2. Navigate to Sources

  3. Select the registered SAP ECC source.

  4. Select + New scan

  5. Provide the below details:

    1. Name: The name of the scan

    2. Connect via integration runtime: Select the configured self-hosted integration runtime.

    3. Credential: Select the credential to connect to your data source. Make sure to:

      • Select Basic Authentication while creating a credential.
      • Provide a user ID to connect to SAP server in the User name input field.
      • Store the user password used to connect to SAP server in the secret key.
    4. Client ID: Enter the SAP Client ID. This is a three-digit numeric number from 000 to 999.

    5. JCo library path: The directory path where the JCo libraries are located.

    6. Maximum memory available: Maximum memory (in GB) available on the Self-hosted Integration Runtime machine to be used by scanning processes. This is dependent on the size of SAP ECC source to be scanned. It's recommended to provide large available memory e.g. 100.

      scan SAPECC

  6. Select Continue.

  7. Choose your scan trigger. You can set up a schedule or ran the scan once.

  8. Review your scan and select Save and Run.

View your scans and scan runs

To view existing scans, do the following:

  1. Go to the Purview Studio. Select the Data Map tab under the left pane.

  2. Select the desired data source. You will see a list of existing scans on that data source under Recent scans, or can view all scans under the Scans tab.

  3. Select the scan that has results you want to view.

  4. This page will show you all of the previous scan runs along with the status and metrics for each scan run. It will also display whether your scan was scheduled or manual, how many assets had classifications applied, how many total assets were discovered, the start and end time of the scan, and the total scan duration.

Manage your scans - edit, delete, or cancel

To manage or delete a scan, do the following:

  1. Go to the Purview Studio. Select the Data Map tab under the left pane.

  2. Select the desired data source. You will see a list of existing scans on that data source under Recent scans, or can view all scans under the Scans tab.

  3. Select the scan you would like to manage. You can edit the scan by selecting Edit scan.

  4. You can cancel an in progress scan by selecting Cancel scan run.

  5. You can delete your scan by selecting Delete scan.


  • Deleting your scan does not delete catalog assets created from previous scans.
  • The asset will no longer be updated with schema changes if your source table has changed and you re-scan the source table after editing the description in the schema tab of Purview.

Next steps

Now that you have registered your source, follow the below guides to learn more about Purview and your data.