
## Crawl SAP BW/4HANA

URL: https://docs.atlan.com/apps/connectors/erp/sap-bw4hana/how-tos/crawl-sap-bw4hana

> Extract and catalog metadata from your SAP BW/4HANA system in Atlan.

# Crawl SAP BW/4HANA 

Extract and catalog metadata from your SAP BW/4HANA system in Atlan. Once configured, the crawler connects to your SAP system through Self-Deployed Runtime and automatically discovers your SAP BW/4HANA assets.

## Prerequisites

Before you begin, make sure you have:

- Completed [SAP BW/4HANA setup](https://docs.atlan.com/llms/connectors/sap-bw4hana/set-up-sap-bw4hana/llms.txt) with required permissions
- Learn more about SAP connectivity: [How Atlan connects to SAP BW/4HANA](https://docs.atlan.com/llms/connectors/sap-bw4hana/how-atlan-connects-to-sap-bw4hana/llms.txt)
- Secure Agent deployed with network access configured:
 - **Outbound HTTPS**: Connection to Atlan Cloud
 - **SAP connectivity**: Local network access to your SAP BW/4HANA system
 - **Firewall**: No inbound ports required
 - **Proxy support**: Configured for corporate HTTP/HTTPS proxies (if applicable)
- Complete the Self-Deployed Runtime configuration by following the instructions in the [How to configure Self-Deployed Runtime for workflow execution](https://docs.atlan.com/llms/platform/secure-agent/configure-secure-agent-for-workflow-execution/llms.txt) guide.

## Create crawler workflow

To create and configure the SAP BW/4HANA crawler workflow, complete the following steps.

1. In your Atlan workspace, click **Connectors** in the left sidebar.
 * If you are using the **Old UI (Classic)**, click **New Workflow** in the top navigation.

2. Click **Marketplace**.

3. Search for **SAP BW/4HANA Assets** and select it.

4. Click **Install**.

5. Once installation completes, click **Setup Workflow** on the same tile.

### Configure metadata extraction

Atlan supports using Self-Deployed Runtime for fetching metadata from SAP BW/4HANA.

1. Install Self-Deployed Runtime if you haven't already:
 - [Install via Docker Compose](https://docs.atlan.com/llms/platform/self-deployed-runtime/install-on-docker-compose/llms.txt)
 - [Install on Kubernetes](https://docs.atlan.com/llms/platform/self-deployed-runtime/install-on-kubernetes/llms.txt)
2. Select the **Agent** tab.

3. Add secret keys for your SAP BW/4HANA credentials in the linked secret store.

4. Provide the following SAP BW/4HANA connection parameters:
 - **SAP Host Name**: The hostname or IP address of your SAP BW/4HANA system
 - **SAP User Name**: The dedicated user account for metadata extraction
 - **SAP Password**: The password for the user account
 - **Connection Type**: Choose between Application Server or Message Server. If you choose Message Server, provide:
 - **Port**: Port number (required if using Message Server)
 - **Group**: Group number (required if using Message Server)
 - **SAP System Number**: Two-digit system identifier (00-99)
 - **SAP Client Number**: Three-digit client identifier (001-999)
 - **Use SAP Router**: Choose **Yes** if using a SAP Router, and provide the **SAP Router String**
5. Click **Next** after completing the configuration.

### Configure connection

To complete the SAP BW/4HANA connection configuration:

1. Provide a connection name that represents your source environment, such as `production`, `development`, `gold`, or `analytics`.

2. To change the users able to manage this connection, change the users or groups listed under **Connection Admins**. If you don't specify any user or group, nobody can manage the connection—not even admins.

3. Click **Next** to proceed.

### Run preflight checks

The SAP BW/4HANA crawler runs [preflight checks](https://docs.atlan.com/llms/catalog/connector-capabilities/what-are-preflight-checks/llms.txt) on the configured connection before extraction. Unlike other SAP connectors, this step doesn't include component-level include or exclude filters—Atlan crawls the full set of supported BW/4HANA assets once the preflight checks pass.

The following checks are performed:

- **Connection check**: Validates that Self-Deployed Runtime can reach your SAP BW/4HANA system using the provided host, system number, and client number.
- **Authentication check**: Verifies that the configured service user can log in and call the required RFC modules (`STFC_CONNECTION`, `RFC_SYSTEM_INFO`, `RFC_READ_TABLE`).
- **System info check**: Retrieves system metadata (SYSID, release version, operating system) to confirm the target system is reachable and reporting expected values.

If any check fails, review the error message, fix the underlying configuration in your SAP system or in the connection parameters, and re-run the preflight checks.

### Run crawler

Choose how and when to run the crawler to extract metadata from your SAP BW/4HANA system.

1. You can either:
 - To run the crawler once immediately, click **Run**
 - To schedule the crawler to run hourly, daily, weekly, or monthly, click **Schedule Run**

Once the crawler completes, you can view the discovered SAP BW/4HANA assets in Atlan's asset page.

## See also

* [What does Atlan crawl from SAP BW/4HANA](https://docs.atlan.com/llms/connectors/sap-bw4hana/what-does-atlan-crawl-from-sap-bw4hana/llms.txt): Learn about the SAP BW/4HANA assets and metadata that Atlan discovers

---
