SAP

SAP is the enterprise resource planning (ERP) system that runs finance, logistics, procurement, and manufacturing for many of the world’s largest organizations. With BonData, you can connect to your SAP account to read, enrich, and sync your ERP data within Agent workflows.

SAP Connection Setup

BonData connects to SAP over HTTPS. You can route through SAP Integration Suite (Cloud Integration, commonly called CPI), or connect directly to your SAP system - either its OData services or its underlying SAP HANA database.

Step 1: Choose a Connection Method

Method	Best for	Works with
SAP Integration Suite (CPI)	Landscapes that already standardize integration on CPI, or where SAP is not directly reachable from outside the corporate network	S/4HANA Cloud, S/4HANA on-premise, ECC
Direct - OData	The simplest path when BonData can reach SAP over HTTPS; respects SAP application-level authorizations	S/4HANA Cloud, S/4HANA on-premise, ECC with SAP Gateway activated
Direct - SAP HANA	High-volume bulk extracts and historical backfills, where reading tables and CDS views directly is fastest	S/4HANA on-premise or private edition, Suite on HANA, BW/4HANA, SAP HANA Cloud

If you are unsure which applies, ask your SAP Basis or integration team whether BonData should go through your Integration Suite tenant or connect to the system directly. Many organizations already have a policy for this.

Step 2: Set Up the Connection

SAP Integration Suite (CPI)
Direct - OData
Direct - SAP HANA

In SAP Integration Suite, open the Cloud Integration capability and go to Design → Integrations
Identify or create the integration flow (iFlow) that exposes the data you want to sync, using an HTTPS sender adapter
Deploy the iFlow and copy its Endpoint URL from the Monitor → Manage Integration Content view
In the SAP BTP cockpit, go to Instances and Subscriptions and create a service instance of Process Integration Runtime with the api service plan
Create a service key for that instance and grant it the ESBMessaging.send role
Copy the Client ID, Client Secret, and Token URL from the service key

The Token URL is your BTP subaccount’s authentication endpoint, in the form https://<subdomain>.authentication.<region>.hana.ondemand.com/oauth/token.

Confirm the OData services you need are available:
- On-premise: use transaction /IWFND/MAINT_SERVICE to activate the required services in SAP Gateway
- S/4HANA Cloud: go to Communication Management → Communication Arrangements and create an arrangement for the relevant communication scenario
Create a dedicated integration user:
- On-premise: use transaction SU01 to create a service user with read authorization for the relevant OData services
- S/4HANA Cloud: create an inbound Communication User and attach it to a Communication System
Note your Service Root URL, in the form https://<host>:<port>/sap/opu/odata/sap/<SERVICE_NAME>
For on-premise systems, note the Client number (sap-client, e.g. 100)
Confirm your firewall or reverse proxy allows HTTPS connections from BonData’s IP addresses

Your SAP team can identify the right SAP_COM_* communication scenario or OData service for each object you want to sync.

Gather the connection endpoint from your Basis team:
- On-premise HANA: SQL port 3<instance>15 (e.g. 30015), or the tenant database port
- SAP HANA Cloud: port 443
Identify the SAP schema to read from (commonly SAPHANADB on S/4HANA, or SAPABAP1 on Suite on HANA)

Create a read-only database user for BonData:

-- Create a user for BonData
CREATE USER BONDATA_USER PASSWORD "your_secure_password" NO FORCE_FIRST_PASSWORD_CHANGE;

-- Grant read access to the SAP schema
GRANT SELECT ON SCHEMA SAPHANADB TO BONDATA_USER;

Confirm your firewall allows connections from BonData’s IP addresses

A direct HANA connection reads database tables and CDS views, bypassing the ABAP application layer. SAP application-level authorization checks do not apply, and you work with technical table names rather than business objects. Scope the database user’s grants narrowly. This method is not available for S/4HANA Cloud public edition, which does not expose its database.

Step 3: Enter Credentials in BonData

In BonData, navigate to Integrations and select SAP
Choose your Connection Method
Enter the credentials for that method (see below)
Click Connect

Required Fields

SAP Integration Suite (CPI)
Direct - OData
Direct - SAP HANA

Field	Description
Endpoint URL	The deployed iFlow endpoint URL
Token URL	OAuth token endpoint for your BTP subaccount
Client ID	Client ID from the Process Integration Runtime service key
Client Secret	Client secret from the service key

Field	Description
Service Root URL	e.g. `https://sap.example.com:44300/sap/opu/odata/sap/<SERVICE_NAME>`
Client	SAP client number, e.g. `100` (`sap-client`) - on-premise only
Username	Integration or communication user name
Password	Password for the integration user

Field	Description
Host	HANA hostname or IP
Port	SQL port, e.g. `30015` (on-premise) or `443` (HANA Cloud)
Database	Tenant database name
Schema	SAP schema to read, e.g. `SAPHANADB`
User	Read-only database user
Password	Password for the database user

Connecting to an on-premise SAP system over RFC using standard BAPI function modules is also supported for older ECC landscapes. Contact your BonData representative if your system cannot be reached through Integration Suite, OData, or HANA.

Overview

AI & LLM Providers

Databases

Business Applications

Customer Success

Marketing & Sales

HR & People

Developer Tools

Cloud Storage

Notifications

Analytics & BI

Enterprise & Operations

Other

SAP Connection Setup

Step 1: Choose a Connection Method

Step 2: Set Up the Connection

Step 3: Enter Credentials in BonData

Required Fields

​SAP Connection Setup

​Step 1: Choose a Connection Method

​Step 2: Set Up the Connection

​Step 3: Enter Credentials in BonData

​Required Fields

SAP Connection Setup

Step 1: Choose a Connection Method

Step 2: Set Up the Connection

Step 3: Enter Credentials in BonData

Required Fields