Destinations
Covers SAP BTP Destinations as the abstraction layer for outbound connectivity from BTP applications and services (Integration Suite, extension apps, SAP Build) to on-premise and cloud target systems. Explains destination configuration properties, authentication types, Cloud vs On-Premise proxy types, Destination service scoping at subaccount and application levels, runtime resolution, Cloud Connector interplay, troubleshooting connectivity failures, and security/performance considerations relevant across Cloud Foundry and Kyma environments.
Overview
Covers SAP BTP Destinations as the abstraction layer for outbound connectivity from BTP applications and services (Integration Suite, extension apps, SAP Build) to on-premise and cloud target systems. Explains destination configuration properties, authentication types, Cloud vs On-Premise proxy types, Destination service scoping at subaccount and application levels, runtime resolution, Cloud Connector interplay, troubleshooting connectivity failures, and security/performance considerations relevant across Cloud Foundry and Kyma environments.
Lessons in this topic
- BTP Destinations Part 1: What the Destination Service DoesThe destination service stores how to reach remote systems — URL, authentication and proxy details — so apps, integration flows and SAP Build tools can connect without hard-coded settings. Learn destination levels (subaccount vs service instance), types (HTTP, RFC, MAIL, LDAP), and how consumers read them.
- BTP Destinations Part 2: Proxy Types, Authentication Methods and Cloud ConnectorConfigure destinations for real systems: proxy type Internet vs OnPremise, location ID for multiple Cloud Connectors, virtual host mapping, authentication types (NoAuthentication, BasicAuthentication, OAuth2ClientCredentials, OAuth2SAMLBearerAssertion, PrincipalPropagation, client certificates), and testing.
- BTP Destinations Part 3: Choosing the Right Authentication and Proxy TypeDecide authentication by scenario: technical integration, user-specific access to on-premise (principal propagation), user-specific access to cloud (OAuth2 SAML bearer / token exchange / JWT bearer), certificate-based auth — and troubleshoot 401/403/500 errors with destination, Cloud Connector and back-end traces.
Interview questions covered
- What are the core concepts of Destinations, and how would you explain them clearly in an SAP interview?
- How would you apply Destinations in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Destinations. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in Destinations?
- Suppose you inherit an existing Destinations solution. How would you review it before making a change?
- Configure destinations for an S/4HANA on-premise system and a cloud partner API.
- A principal propagation destination returns 401. Walk through your troubleshooting.
- Test calls from a BTP app hit a production S/4HANA system. Explain how destinations are resolved and how you'd fix this.