• Without SCC → Your BTP apps can’t reach internal (on-premise) systems.
• With SCC → You can expose only selected resources safely to BTP apps, without opening up the entire network.

Think of it like a firewall-friendly, secure bridge.

Step-by-Step Setup

Step 1: Install SAP Cloud Connector

• Download it from the SAP Development Tools website.
• Install on a server (Windows/Linux) inside your corporate network.

Step 2: Access the SCC UI

• Open a browser and go to:
  https://localhost:8443

• Default login:

  • Username: Administrator

  • Password: manage (you’ll be forced to change it).

Step 3: Connect SCC to Your Subaccount

• In the SCC UI, go to Subaccount → Add Subaccount.

• Enter:

  • Region: Select the SAP BTP region (e.g., eu10, us10).

  • Subaccount ID: Get this from your BTP Cockpit.

  • Login Email & Password: Your SAP BTP user.

• Save → SCC now shows “Connected” if successful.

Step 4: Define On-Premise Systems

• In SCC UI, go to Cloud To On-Premise → Access Control.

• Click Add System Mapping.

• Choose:

• Backend Type: e.g., ABAP System, HTTP, RFC.
• Protocol: e.g., HTTP for OData services, RFC for SAP function calls.
• Internal Host & Port: (e.g., sap.internal.corp:44300).
• Virtual Host & Port: The alias name that BTP apps will use.

• Save.

Step 5: Expose Resources

• Still under Access Control, select your system.
• Choose Resources → Add.
• Define which path/services (e.g., /sap/opu/odata) are exposed.
• Save.

Step 6: Use in SAP BTP Destination

• Now, when creating a Destination in BTP Cockpit:

  • Set Proxy Type = OnPremise.

  • Use the Virtual Host & Port defined in SCC.

• Test connection — if green, your BTP app can reach the on-premise system.