Destinations
Reaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Consuming remote OData V2/V4 services using SAP Cloud SDK, translating CQN queries against a configured Remote Service into OData V2 or V4 requests over the resolved destination or service binding.
Allows integration with Cloud SDK to connect with remote REST-based services, only including the minimum Cloud SDK dependencies by default so a feature adds the rest as needed.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysA destination used by a covered CAP application sends SAP product data to a non-SAP product rather than only addressing a remote endpoint.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
A destination is configuration, not the deciding boundary. The licence becomes material when the resulting data flow is extraction into a non-SAP product, so the target and purpose need review.
SAP Developer License Agreement 3.2 CAP →Artifacts
Seen working
Neither the package manifest nor the repository tree declares a licence.
Neither the package manifest nor the repository tree declares a licence.
Details
Coverage
For your agent
- Ref
capability:destinations- JSON
- /capabilities/destinations.json
- MCP
- Connecting an agent