Connect to and manage SAP S/4HANA in Microsoft Purview

This article outlines how to register SAP S/4HANA, and how to authenticate and interact with SAP S/4HANA in Microsoft Purview. For more information about Microsoft Purview, read the introductory article.

Supported capabilities

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

* Besides the lineage on assets within the data source, lineage is also supported if dataset is used as a source/sink in Data Factory or Synapse pipeline.

When scanning SAP S/4HANA source, Microsoft Purview supports:

  • Extracting technical metadata including:

    • Instance
    • Application components
    • Packages
    • Tables including the fields, foreign keys, indexes, and index members
    • Views including the fields
    • Transactions
    • Programs
    • Classes
    • Function groups
    • Function modules
    • Domains including the domain values
    • Data elements
  • Fetching static lineage on assets relationships among tables and views.

Prerequisites

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

  • An active Microsoft Purview account.

  • You need Data Source Administrator and Data Reader permissions to register a source and manage it in the Microsoft Purview governance portal. For more information about permissions, see Access control in Microsoft Purview.

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

    Note

    Scanning SAP S/4HANA 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 machine where the self-hosted integration runtime is installed. Restart the machine after you newly install the JDK for it to take effect.

    • 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.

      pre-requisite

    • The connector reads metadata from SAP using the SAP Java Connector (JCo) 3.0 API. Hence make sure the Java Connector is available on your virtual machine where self-hosted integration runtime is installed. Make sure that you're 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. Note down the folder path which you will use to set up the scan.

      Note

      The driver should be accessible by the self-hosted integration runtime. By default, self-hosted integration runtime uses local service account "NT SERVICE\DIAHostService". Make sure it has "Read and execute" and "List folder contents" permission to the driver folder.

    • Self-hosted integration runtime communicates with the SAP server over dispatcher port 32NN and gateway port 33NN, where NN is your SAP instance number from 00 to 99. Make sure the outbound traffic is allowed on your firewall.

  • Deploy the metadata extraction ABAP function module on the SAP server by following the steps mentioned in ABAP functions deployment guide. You'll need an ABAP developer account to create the RFC function module on the SAP server. For scan execution, 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)
    • OCS_GET_INSTALLED_COMPS (check software versions)
    • Z_MITI_DOWNLOAD (main metadata import, the function module you create following the Purview guide)

    The underlying SAP Java Connector (JCo) libraries may call additional RFC function modules e.g. RFC_PING, RFC_METADATA_GET, etc., refer to SAP support note 460089 for details.

Register

This section describes how to register SAP S/4HANA in Microsoft Purview using the Microsoft Purview governance portal.

Authentication for registration

The only supported authentication for SAP S/4HANA source is Basic authentication.

Steps to register

  1. Navigate to your Microsoft Purview account.

  2. Select Data Map on the left navigation.

  3. Select Register

  4. On Register sources, select SAP S/4HANA. Select Continue

    register SAPS/4Hana options

On the Register sources (SAP S/4HANA) 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 S/4HANA 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 SAP S/4HANA

Scan

Follow the steps below to scan SAP S/4HANA to automatically identify assets. 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 isn't set up, use the steps mentioned here to create a self-hosted integration runtime

  2. Navigate to Sources.

  3. Select the registered SAP S/4HANA 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 here the SAP system client ID. The client is identified with three-digit numeric number from 000 to 999.

    5. JCo library path: Specify the directory path where the JCo libraries are located, e.g. D:\Drivers\SAPJCo. Make sure the path is accessible by the self-hosted integration runtime, learn more from prerequisites section.

    6. Maximum memory available: Maximum memory (in GB) available on customer's VM to be used by scanning processes. This is dependent on the size of SAP S/4HANA source to be scanned. It's recommended to provide large available memory, for example, 100.

    scan SAP S/4HANA

  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:

  1. Go to the Microsoft Purview governance portal. Select the Data Map tab on the left pane.

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

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

    The page that appears shows you all of the previous scan runs, along with the status and metrics for each scan run. It also displays:

    • Whether your scan was scheduled or manual.
    • How many assets had classifications applied.
    • How many total assets were discovered.
    • The start and end times of the scan, and the total scan duration.

Manage your scans - edit, delete, or cancel

To manage or delete a scan:

  1. Go to the Microsoft Purview governance portal. Select the Data Map tab on the left pane.

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

  3. Select the scan that you want to manage. You can then:

    • Edit the scan by selecting Edit scan.
    • Cancel an in-progress scan by selecting Cancel scan run.
    • Delete your scan by selecting Delete scan.

Note

  • 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 on the Schema tab of Microsoft Purview.

Lineage

After scanning your SAP S/4HANA source, you can browse data catalog or search data catalog to view the asset details.

Go to the asset -> lineage tab, you can see the asset relationship when applicable. Refer to the supported capabilities section on the supported SAP S/4HANA lineage scenarios. For more information about lineage in general, see data lineage and lineage user guide.

Next steps

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