Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A destination describes how to reach a service. For on-premise access, a Cloud Connector provides the route; a Location ID can distinguish connectors in the same subaccount.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Business Technology Platform, or BTP, provides cloud services for applications, data and integration. A connection needs a route, an identity and permission to perform the intended task.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for BTP on-premise destination fails? Check the Cloud Connector location ID
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP BTP destinations and Cloud Foundry application-router connectivity to Cloud Connector. Authentication details are scenario specific; the cited product setup is not a universal credential template.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Connect a plant app through the intended connector

Select the intended connector

Destination: On-premise backend. Connector location: PLANT_A. Working comparison: PLANT_B. Review: Consumer and location scope
What to notice: A route working through one connector does not establish that another selected location can reach the same resource.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Destination
On-premise backend
Connector location
PLANT_A
Working comparison
PLANT_B
Review
Consumer and location scope
Words you’ll meet in this guide
Backend
The service or system doing the work behind an interface.
Destination
Named connection settings for another service.
Credential
Access information used to prove an identity.
Subaccount
A BTP scope for applications, services and access settings.
OData
A standard for reading and updating data through a web API.
BTP
SAP Business Technology Platform: cloud services for applications, data and integration.
HTTP
The request-and-response protocol used by web applications and APIs.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Destination → Connector location → On-premise service. Conceptual diagram for BTP on-premise destination fails? Check the Cloud Connector location ID.
Apply the idea: A manufacturer has connectors for different plants using similar virtual system names, and its extension needs the correct route.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Connect a plant app through the intended connector

    A manufacturer has connectors for different plants using similar virtual system names, and its extension needs the correct route.

  2. Select the right connector before testing the backend

    For a supported SAP BTP on-premise destination, the Cloud Connector location ID selects the intended connector connection for the subaccount.

  3. Keep four identities separate

    The subaccount identifies the cloud context connected to Cloud Connector.

  4. Worked case: PLANT_A and PLANT_B share a virtual name

    Imagine one subaccount connected to two authorized connector installations.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.