Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

SAP Cloud Connector exposes selected on-premise resources to supported cloud consumers. System mapping identifies the backend route, while resource rules define the allowed paths.

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 SAP Cloud Connector: Separate system reachability from resource access
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.

Cloud Connector system-mapping/resource concepts illustrated by SAP Cloud Integration and Digital Manufacturing setup documentation. Their exact authentication settings are not universal defaults.

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

Expose the intended plant resource deliberately

System access versus path access

Cloud destination: Backend connection. System mapping: Configured. Requested API path: Check allowed resource rule. Outcome: Path-specific access
What to notice: Mapping a system does not by itself expose every path on that system.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Cloud destination
Backend connection
System mapping
Configured
Requested API path
Check allowed resource rule
Outcome
Path-specific access
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.
BTP
SAP Business Technology Platform: cloud services for applications, data and integration.
API
A defined interface through which programs exchange data or request actions.
RFC
Remote Function Call: a way for one system to call functions in another.
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.

Cloud request → Mapped system → Allowed backend resource. Conceptual diagram for SAP Cloud Connector: Separate system reachability from resource access.
Apply the idea: A manufacturer's cloud extension can reach a mapped system but not the operational API path it needs.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. Expose the intended plant resource deliberately

    A manufacturer's cloud extension can reach a mapped system but not the operational API path it needs.

  2. A reachable system and an allowed resource are separate conditions

    Cloud Connector system mapping identifies an on-premise backend through a virtual host and port.

  3. Understand virtual mapping, internal reachability and path authorization

    The virtual endpoint is the address the supported cloud consumer uses.

  4. Worked case: the system is reachable but the orders path is denied

    Imagine destination ERP_API referring to virtual host erp.virtual on port 443.

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.