## Crawl SAP S/4HANA

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

> Extract and catalog metadata from your SAP S/4HANA system including tables, fields, CDS views, Fiori apps, and modules in Atlan.

# Crawl SAP S/4HANA

Extract and catalog metadata from your SAP S/4HANA system including tables, fields, CDS views, Fiori apps, and modules in Atlan. Once configured, the crawler connects to your SAP system through Self-Deployed Runtime and automatically discovers your SAP assets.

## Prerequisites

Before you begin, make sure you have:

- Completed [SAP S/4HANA setup](https://docs.atlan.com/llms/connectors/sap-s4hana/set-up-sap-s4hana/llms.txt) with required permissions
- Learn more about SAP connectivity: [How Atlan connects to SAP S/4HANA](https://docs.atlan.com/llms/connectors/sap-s4hana/how-atlan-connects-to-sap-s4hana/llms.txt)
- Secure Agent deployed with network access configured:
 - **Outbound HTTPS**: Connection to Atlan Cloud
 - **SAP connectivity**: Local network access to your SAP S/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 S/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 S/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 S/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 S/4HANA credentials in the linked secret store.

4. Provide the following SAP S/4HANA connection parameters:

4. Provide the following SAP S/4HANA connection parameters:
 - **SAP Host Name**: The hostname or IP address of your SAP S/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 S/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.

### Configure crawler

Configure which SAP components to include or exclude and set advanced crawler options. The component selection supports hierarchical browsing, allowing you to expand and collapse component categories to select specific subcomponents.

To configure component filters:

- **Include Components**: Click to select specific SAP components and their subcomponents to crawl. You can search for components using the search bar or use the advanced search option.
- **Exclude Components**: Click to select specific SAP components and their subcomponents to exclude from the crawl.
- **Asset types**: Select the asset types to crawl. Leave this empty to crawl all supported asset types. Available options are Table, View, ABAP Program, Transaction Codes, Function Modules, CDS View, Fiori App, and Classes & Characteristics.
- To configure advanced crawler settings:
 - **SAP Language**: Language code (default: EN)
 - **SAP Codepage**: Character encoding (default: 0)
 - **SAP Unicode System**: Choose **Yes** to use unicode
 - **Unicode Support**: Choose **Yes** to enable Unicode support
 - **SAP Trace**: Choose **Yes** to enable trace logging for debugging
 - **Connection Pool Size**: Maximum number of connections (default: 5)

Component filters apply to tables, views, CDS views, and columns. SAP stores classification classes as customizing data rather than repository objects, so component filters have no effect on classes and characteristics. Selecting a narrow set of components still returns every class. To exclude them, deselect **Classes & Characteristics** in **Asset types**.

### Run crawler

Choose how and when to run the crawler to extract metadata from your SAP S/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 S/4HANA assets in Atlan's asset page.

## See also

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

---