Events
Take the Microsoft Learn Challenge
Nov 19, 11 PM - Jan 10, 11 PM
Ignite Edition - Build skills in Microsoft security products and earn a digital badge by January 10!
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Metadata Extraction | Full Scan | Incremental Scan | Scoped Scan | Classification | Labeling | Access Policy | Lineage | Data Sharing | Live view |
---|---|---|---|---|---|---|---|---|---|
Yes | Yes | No | No | No | No | No | No | No | No |
The supported SAP BW versions are 7.3 to 7.5. SAP BW/4HANA isn't supported.
When scanning SAP BW source, Microsoft Purview supports extracting technical metadata including:
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.
When you create a scan for the first time, you need to create a function module in your SAP server. Microsoft Purview provides some code in the asset page in the Microsoft Purview Data Map to create the module. To download this code, you need to have Data Source Administrator permissions on the root collection in your data map.
Set up the right integration runtime for your scenario:
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. For scan execution, the user account requires sufficient permissions to connect to the SAP server and execute the following RFC function modules:
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.
This section describes how to register SAP BW in Microsoft Purview using the Microsoft Purview governance portal.
The only supported authentication for SAP BW source is Basic authentication.
Open the Microsoft Purview governance portal by:
Select Data Map on the left navigation.
Select Register.
In Register sources, select SAP BW > Continue.
On the Register sources (SAP BW) screen, do the following:
Enter a Name that the data source will be listed within the Catalog.
Enter the Application server name to connect to SAP BW source. It can also be an IP address of the SAP application server host.
Enter the SAP System number. It's an integer between 0 and 99.
Select a collection from the list.
Finish to register the data source.
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.
Important
When you create a scan for the first time, you need to create a function module in your SAP server. Microsoft Purview provides some code in the asset page in the Microsoft Purview Data Map to create the module. To download this code, you need to have Data Source Administrator permissions on the root collection in your data map.
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 in prerequisites to create a self-hosted integration runtime.
Navigate to Sources
Select the registered SAP BW source.
Select + New scan
Provide the below details:
Name: The name of the scan
Connect via integration runtime: Select the configured self-hosted integration runtime.
Credential: Select the credential to connect to your data source. Make sure to:
Client ID: Enter the SAP Client ID. It's a three-digit numeric number from 000 to 999.
JCo library path: Specify the directory path where the JCo libraries are located, for example: D:\Drivers\SAPJCo
. Make sure the path is accessible by the self-hosted integration runtime, learn more from prerequisites section.
D:\Drivers\SAPJCo
. It's the path to valid JAR folder location. The value must be a valid absolute file path and doesn't contain space. Make sure the driver is accessible by the self-hosted integration runtime; learn more from prerequisites section../drivers/SAPJCo
. It's the path to valid JAR folder location. The value must be a valid relative file path. Please refer to the documentation to set up a scan with external drivers for uploading drivers in advance.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.
Select Test connection.
Select Continue.
Choose your scan trigger. You can set up a schedule or ran the scan once.
Review your scan and select Save and Run.
To view existing scans:
To edit, cancel, or delete a scan:
Go to the Microsoft Purview portal. On the left pane, select Data Map.
Select the 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.
Select the scan that you want to manage. You can then:
Note
Now that you've registered your source, follow the below guides to learn more about Microsoft Purview and your data.
Events
Take the Microsoft Learn Challenge
Nov 19, 11 PM - Jan 10, 11 PM
Ignite Edition - Build skills in Microsoft security products and earn a digital badge by January 10!
Register now