Name: Configuring Cloud Connector to Integrate SAP Sales/Service Cloud Version 2 with SAP S/4HANA
Uploaded: 2026-3-10
Duration: 251 s
Description: Learn how to set up Cloud Connector to allow connections from cloud systems, such as SAP Sales and Service Cloud Version 2 via the SAP BTP Connectivity Services to the customer network without opening ports or changing inbound firewall rules, and how to define granular access rules to resources of systems within the customer network, such as SAP S/4HANA.

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Personalize your learning.

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

This browser is not supported

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Validate your skills and learning by completing the certification exam and gain a highly recognised accreditation.

Book your certification exam

Complete the assessment to validate your SAP PartnerEdge competency qualifications.

Ready to take your assessment?

Learn about the key features and essentials in the latest release to help you prepare for the Stay Certified assessment.

Prepare for assessment

Learn new skills you need at your own pace with our bite-sized lessons.

Prepare for certification

In your My Learning account you can view your certification and learn how to take your Stay Certified assessment.

Ready to take your Stay Certified assessment?

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Overview

Support Resource

Certification Exam

Theoretical Exam

Schedule

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Quiz

Scenario Based Assessment

Course Assessment

Course

Stay Certified

Subscription

System Based Assessment

Test Out

Unit

Video

Video Playlist

Week

Want to remove this from your Learning List?

Your exclusive access to the SAP Learning Hub, event edition is ready. <link>Start learning now.</link>

Access activated

You can now register for free Live Sessions.

<div><div>Learn how to set up Cloud Connector to allow connections from cloud systems, such as SAP Sales and Service Cloud Version 2 via the SAP BTP Connectivity Services to the customer network without opening ports or changing inbound firewall rules, and how to define granular access rules to resources of systems within the customer network, such as SAP S/4HANA.</div></div>

Configuring Cloud Connector to Integrate SAP Sales/Service Cloud Version 2 with SAP S/4HANA

This video demonstrates how to configure Cloud Connector and connect it to your BTP subaccount. First, we'll connect Cloud Connector to your BTP subaccount. Log in to the BTP cockpit and navigate to Cloud Connectors. At the moment, no Cloud Connector is connected to this subaccount. To establish a connection, we must download an authentication data file. Give the file a name and save it somewhere on your computer. We'll use it in a moment. Now, log in to the Cloud Connector Administration web UI and choose Add Subaccount. The first step asks for an HTTP proxy. Since the demo environment doesn't have one, we can leave the fields blank. In the second step, you must choose whether you want to connect the Cloud Connector to your subaccount using a BTP cockpit user, which was the only way in former times, or if you want to use an authentication data file like we have downloaded previously, we decided to use the authentication data file since it is very convenient and we have already prepared it. In the next step, choose the option Add subaccount authentication data from file and browse for the previously downloaded file on your computer. Please note that the file is only valid for a few minutes after downloading. In the last step, you can provide a location ID and a description. The location ID is only mandatory if you connect multiple cloud connectors to the same subaccount. Now, the connected subaccount is showing up in the dashboard and the menu on the left. In the next step, we can create the system mapping. Navigate to cloud to on-premises in the sub-account menu. Use the plus icon in the table mapping virtual to internal system to add a new entry. In the first step, we have to choose the back-end type. As you can see, there are several options available. In our case, we want to connect to an ABAP system, which is the default. In the next step, we have to choose the protocol. Since we want to send data encrypted to our S/4 target system, we choose HTTPS here. Then we have to enter the internal host and port. These are the details of the machine within your network. Enter the real fully qualified hostname and port. In the next step, we can specify the virtual hostname and port. These details must later be entered when configuring an integration flow. We enter a different name and port here to prevent exposing internal network information to the cloud. Depending on your setup, you may or may not use principal propagation. In the demo, we leave it active, but we don't use it. Leave the principal type on the next page as is. On the page with the host in request header, leave the option Use Virtual Host and go to the next page. page. We skip the page with the optional system ID and the description. On the last page, you see a rough summary of the mapping. Activate the checkbox to check the internal host. This verifies if the machine is reachable with the provided details. Then finish the dialog. Now, we can see the mapping entry in the first table. After a short moment, we can see that the host is reachable. That means we can continue to map resources. Add a new entry to the second table where the resources are managed. In this demo, we make it easy for ourselves and simply map the root path and allow access to all subpaths. In production environments, you should limit access as much as possible and only allow access to paths that are needed. Save the entry. That concludes the basic configuration of the cloud connector.