Integrations / SAP S/4HANA

SAP S/4HANA

Read-only access to the published SAP S/4HANA Business Partner OData API. For each target edition (Public Cloud, Private Edition, or on-premise), confirm that the exact release exposes API_BUSINESS_PARTNER and that its communication, HTTPS Basic-auth, and network route are configured. This definition does not claim identical setup or reach across editions, SAP ECC, RFC/BAPI/IDoc, or write support.

Basic auth

Actions

What Telara does

Capability matrix

Indexes No Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

An SAP S/4HANA tenant and exact release that publishes the API_BUSINESS_PARTNER OData service.

An administrator who can configure the appropriate communication arrangement and a communication user for that deployment.

Vendor setup

Get the credential

Confirm the deployment route

Identify whether the target is Public Cloud, Private Edition, or on-premise. Confirm API_BUSINESS_PARTNER exposure, the HTTPS endpoint, communication setup, and network route for that exact release; setup and reach are not interchangeable across editions.

Create a least-privilege communication user

Grant only the published Business Partner read access required for the connection. The declared catalog method is HTTPS Basic Authentication for a customer-enabled communication arrangement.

Configure the connection

In Telara’s SAP S/4HANA integration settings, enter the verified service base URL and communication username and password. Use a sandbox or non-production tenant for validation.

In Telara

Connect in Telara

Basic auth

SAP communication user credentials for a customer-enabled API_BUSINESS_PARTNER communication arrangement over HTTPS.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Base Url
Username
Password

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

This definition covers read-only Business Partner OData access when the exact S/4HANA deployment exposes and permits the service.

SAP ECC, RFC/BAPI/IDoc, unconfigured private-network access, and write operations are not included.