Connect to and manage an SAP Business Warehouse – Microsoft Purview

Table of Contents0.1 In this article1 Supported capabilities2 Prerequisites3 Register3.1 Authentication for registration3.2 Steps to register4 Scan4.1 Create and run scan4.2 View your scans and scan runs4.3 Manage your scans – edit, delete, or cancel5 Next steps Article 06/30/2022 5 minutes to read […]

This article outlines how to register SAP Business Warehouse (BW), and how to authenticate and interact with SAP BW 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 No No

The supported SAP BW versions are 7.3 to 7.5. SAP BW4/HANA isn’t supported.

When scanning SAP BW source, Microsoft Purview supports extracting technical metadata including:

  • Instance
  • InfoArea
  • InfoSet
  • InfoSet query
  • Classic InfoSet
  • InfoObject including unit of measurement, time characteristic, navigation attribute, data packet characteristic, currency, characteristic, field, and key figure
  • Data store object (DSO)
  • Aggregation level
  • Open hub destination
  • Query including the query condition
  • Query view
  • HybridProvider
  • MultiProvider
  • InfoCube
  • Aggregate
  • Dimension
  • Time dimension

Prerequisites

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

  • An active Microsoft Purview resource.

  • 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. The minimal supported Self-hosted Integration Runtime version is 5.15.8079.1.

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

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

      Note

      The driver should be accessible to all accounts in the machine. Don’t put it in a path under user account.

  • Deploy the metadata extraction ABAP function module on the SAP server by following the steps mentioned in ABAP functions deployment guide. You 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)
    • OCS_GET_INSTALLED_COMPS (check software versions)
    • Z_MITI_BW_DOWNLOAD (main metadata import)

Register

This section describes how to register SAP BW in Microsoft Purview using the Microsoft Purview governance portal.

Authentication for registration

The only supported authentication for SAP BW 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. In Register sources, select SAP BW > Continue.

On the Register sources (SAP BW) 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 BW source. It can also be an IP address of the SAP application server host.

  3. Enter the SAP System number. It’s an integer between 0 and 99.

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

  5. Finish to register the data source.


    Screenshot of registering an SAP BW source.

Scan

Follow the steps below to scan SAP BW 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 BW 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. It’s a 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:DriversSAPJCo. 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 the Self-hosted Integration Runtime machine to be used by scanning processes. This is dependent on the size of SAP BW source to be scanned.


      Screenshot of setting up an SAP BW scan.

  6. Select Test connection.

  7. Select Continue.

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

  9. 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 Microsoft Purview governance portal. 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 Microsoft Purview governance portal. 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.

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 in the schema tab of Microsoft Purview.

Next steps

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

Source Article

Next Post

BCDR for Azure Virtual Desktop - Cloud Adoption Framework

Mon Aug 1 , 2022
Table of Contents0.1 In this article1 Design considerations1.1 Host pool active-active vs. active-passive1.2 Host pool resiliency1.3 Optimal storage for profile and office containers1.3.1 User data storage replication and resiliency1.4 Golden image availability1.5 Backup protection1.6 Infrastructure and application dependencies2 Design recommendations Article 08/09/2021 9 minutes to […]