Crawl SAP S/4HANA Public Preview
Extract and catalog metadata from your SAP S/4HANA system including tables, fields, CDS views, and modules in Atlan. Once configured, the crawler connects to your SAP system through the secure agent and automatically discovers your SAP assets.
Prerequisites
Before you begin, make sure you have:
- Completed SAP S/4HANA setup with required permissions
- Learn more about secure agent connectivity: How Atlan connects to SAP S/4HANA
- 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 Secure Agent configuration by following the instructions in the How to configure Secure Agent for workflow execution guide.
Create crawler workflow
To create and configure the SAP S/4HANA crawler workflow, complete the following steps.
- In the top right corner of any screen, navigate to New and then click New Workflow.
- From the list of packages, select SAP S/4HANA Assets, and click Setup Workflow.
Configure metadata extraction
Atlan supports using a Secure Agent for fetching metadata from SAP S/4HANA.
- Select the Agent tab.
- Add secret keys for your SAP S/4HANA credentials in the linked secret store.
- 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
- Click Next after completing the configuration.
Configure connection
To complete the SAP S/4HANA connection configuration:
- Provide a connection name that represents your source environment, such as
production,development,gold, oranalytics. - 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.
- To use secure network communication:
- Use Secure Network Connection: Choose Yes
- SNC Name: Your SNC name
- SNC Partner: Partner SNC name
- SNC Security Level: Security level
- SNC Library Path: Path to SNC library
- 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.
- 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)
Run crawler
Choose how and when to run the crawler to extract metadata from your SAP S/4HANA system.
- 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: Learn about the SAP S/4HANA assets and metadata that Atlan discovers