View Categories

Configure Your SAP Environment

3 min read

Table of Contents

This page describes the SAP-side setup you complete alongside Metrica onboarding. Metrica subscribes your BTP subaccount to the connector; you configure the SAP Destination Service so the connector can reach your S/4HANA system, and complete any additional configuration your SAP variant requires.

i
The SAP-side steps differ between deployments. On-premise / Private Cloud customers configure their SAP backend directly (technical user, OData services, PFCG role, business authorizations). S/4HANA Public Cloud customers use SAP Communication Arrangements instead. Both paths are covered under Step 2 below.

Prerequisites #

  • An SAP BTP subaccount where you have Subaccount Administrator permissions.
  • Access to your S/4HANA system’s base URL and credentials for the technical user that will read data.
  • (On-premise S/4HANA only) SAP Cloud Connector configured between your BTP subaccount and your SAP backend.
  • (S/4HANA Public Cloud only) Access to a Public Cloud administrator during onboarding.

Step 1: Create the SAP destination #

The connector reads from SAP through the BTP Destination Service. Create a destination named exactly s4-destination — this name is wired into the connector configuration and cannot be changed.

In Subaccount → Connectivity → Destinations → New Destination, set:

  • Name: s4-destination
  • Type: HTTP
  • URL: your S/4HANA system’s base URL
  • Proxy Type:
    • OnPremise if your S/4HANA runs on-premise (routes via Cloud Connector).
    • Internet if your S/4HANA is reachable directly over the public internet (typically S/4HANA Public Cloud).
  • Authentication: one of the options below.

Add an additional property:

  • Property: sap-client
  • Value: your S/4HANA client number (for example, 200).

Authentication options #

For productive deployments, use one of:

  • OAuth2ClientCredentials
  • OAuth2SAMLBearerAssertion
  • PrincipalPropagation — for on-premise S/4HANA via Cloud Connector.

For sandbox / development against the SAP API Business Hub sandbox or a non-productive dev system, BasicAuthentication is acceptable.

Avoid BasicAuthentication for production: it stores static credentials at rest on the destination and provides no per-user audit trail in SAP.
s4-destination configured in the BTP cockpit

Step 2: Complete SAP-side configuration #

Depending on your S/4HANA deployment, additional configuration is required on the SAP side before the destination will return data. Follow the guide that matches your environment:

  • S/4HANA On-Premise, Private Cloud, or other on-prem SAP variants — see On-Premise SAP Configuration for the SAP-side steps: technical user, OData service activation, PFCG role, business authorizations.
  • S/4HANA Public Cloud — see S/4HANA Public Cloud for CBC scope items, Communication User, Communication System, and Communication Arrangements setup.

Step 3: Open the connector and verify the setup #

In Subaccount → Instances and Subscriptions, click the powerbi-connector subscription and choose Go to Application. You land on the Data Sources page.

Go to Application from the subscription

From there, create an access token and create a small data source to confirm the setup works end to end. For the step-by-step walkthrough, see Quickstart — from Zero to a Power BI Report.

What you’ll need next #