{"ref":"capability:destinations","page":"/capabilities/destinations","json":"/capabilities/destinations.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"destinations","name":"Destinations","domain":"integration-and-messaging","ecosystems":["cap","btp","ui5"],"universal":true,"description":"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.","short":"Reaching remote systems without addresses or credentials in the code","core_coverage":{"state":"core-and-community","assessed_at":"2026-09-27","where_it_stops":"At the SAP Cloud SDK packages: they resolve a destination, carry the token and put the resilience around the call, and the call then takes the shape their clients give it.","relationship":"unassessed","note":"Until 2026-09-27 this was assessed from who provides it, because no capire page had been found to cite; the Outbound Authentication and Remote Services pages are that page.","community_adds":"[cdse](artifact:cdse) reads the destination from the CAP configuration and hands the request to [axios](external:axios), so the url, the method and the body are written at the call site.","what_core_does":"Built in: the connectivity component behind every remote service resolves where the target is, a local destination, an SAP BTP destination or a service binding, sets up the trusted channel, IAS, XSUAA, X.509 or ZTID, and propagates the user, technical or named, from configuration and not from application code. In Node.js the runtime's own fetch client resolves a named BTP destination since the September 2026 release; the SAP Cloud SDK client is used when installed and still covers on-premise connectivity and the authentication types the native client does not.","sources":[{"url":"https://cap.cloud.sap/docs/guides/security/remote-authentication","title":"Outbound Authentication — capire","checked":"2026-09-27","quote":"decouples the protocol level (exchanged content) from the connection level (established connection channel)"},{"url":"https://cap.cloud.sap/docs/guides/security/remote-authentication","title":"Outbound Authentication — capire","checked":"2026-09-27","quote":"At the connectivity layer, the following basic tasks can be addressed generically: Authentication (how to set up a trusted channel) Destination (how to find the target service) User propagation (how to transport user information)"},{"url":"https://cap.cloud.sap/docs/node.js/remote-services","title":"Remote Services Concept — capire","checked":"2026-09-27","quote":"CAP provides a built-in remote client that uses the native Node.js fetch API, including support for resolving named destinations from the SAP BTP Destination service."},{"url":"https://cap.cloud.sap/docs/releases/2026/sep26","title":"CAP Release Notes — September 2026","checked":"2026-09-18","quote":"So far, the Node-native Fetch API, as introduced in April 2026, couldn't resolve SAP BTP Destinations. Hence, in production, SAP Cloud SDK was still required. With this release, we added built-in support for resolving destinations with these limitations:"},{"url":"https://cap.cloud.sap/docs/releases/2026/sep26","title":"CAP Release Notes — September 2026, Destinations w/o Cloud SDK","checked":"2026-09-18","quote":"Install @sap-cloud-sdk/http-client in your project, to have that used automatically instead of the built-in native fetch client. Do so if you use an authentication type that's not supported yet — for example, OnPremise connectivity."}]},"changed_in":[{"version":"@sap-cloud-sdk/connectivity 4.0.0","date":"2025-03-04","what_changed":"SAP Cloud SDK for JavaScript 4.0 turned destination caching on by default for lookups made through the destination service — getDestination(), getAllDestinationsFromDestinationService(), and the generated client's execute() all now cache what they resolve. Before 4.0, every one of those calls re-fetched credentials from the destination service; the same release also stopped requiring an XSUAA service binding to retrieve a destination and disabled iasToXsuaaTokenExchange by default.","invalidates":"Advice written before March 2025 that assumes every destination lookup is a fresh call to the destination service. A stale cached destination, not a slow round trip, is now the first thing to check.","source":{"url":"https://sap.github.io/cloud-sdk/docs/js/release-notes","title":"SAP Cloud SDK for JavaScript — Release Notes, 4.0.0","checked":"2026-09-08","quote":"Enable destination caching by default when retrieving destinations via the destination service."},"applies_to":{"ecosystems":["cap"]}}],"coverage_by_ecosystem":{"btp":{"state":"core-only","assessed_at":"2026-09-09","where_it_stops":"At the address and the credential. Reaching a system that is not on the internet also needs [SAP Connectivity service](artifact:btp-connectivity) and a Cloud Connector in front of it.","note":"SAP's own pieces around the destination are [SAP Private Link Service](artifact:btp-private-link-service), which gives a bound service a private endpoint to a service in a partner cloud account, and [btp-cloud-connector-setup-automation](artifact:sap-samples-btp-cloud-connector-setup-automation), which generates the destination files for a Cloud Connector mapping."},"ui5":{"state":"core-only","assessed_at":"2026-10-19","what_core_does":"SAP's [backend-proxy-middleware](https://github.com/SAP/open-ux-tools/tree/main/packages/backend-proxy-middleware) forwards a path of the UI5 dev server to a backend named by `destination` instead of a URL, optionally read by a given Destination service instance through `destinationInstance`, with forwarded headers for a destination that uses principal propagation.","where_it_stops":"In SAP Business Application Studio. Its README makes the backend URL mandatory unless a destination is given and the proxy runs there, so on a local machine the address is written into `ui5.yaml`.","community_adds":"[ui5-middleware-destination](artifact:preetamkajalrout-ui5-middleware-destination) reads destinations from WebIDE-style destination files kept outside the project and answers the routes of `neo-app.json` with them, and [ui5-middleware-approuter](artifact:ui5-community-ui5-middleware-approuter) connects the dev server through [@sap/approuter](artifact:sap-approuter) to Cloud Foundry or XS Advanced destinations.","sources":[{"url":"https://github.com/SAP/open-ux-tools/tree/main/packages/backend-proxy-middleware","title":"SAP/open-ux-tools — @sap-ux/backend-proxy-middleware README","checked":"2026-10-19","quote":"Required if the backend system is available as destination in SAP Business Application Studio."},{"url":"https://github.com/SAP/open-ux-tools/tree/main/packages/backend-proxy-middleware","title":"SAP/open-ux-tools — @sap-ux/backend-proxy-middleware README","checked":"2026-10-19","quote":"URL pointing to the backend system is mandatory, unless a destination is provided and the proxy is running on SAP Business Application Studio."},{"url":"https://github.com/SAP/open-ux-tools/tree/main/packages/backend-proxy-middleware","title":"SAP/open-ux-tools — @sap-ux/backend-proxy-middleware README","checked":"2026-10-19","quote":"If the backend destination is configured to use principal propagation, then in some cases the requests might fail."},{"url":"https://github.com/SAP/open-ux-tools/tree/main/packages/backend-proxy-middleware","title":"SAP/open-ux-tools — @sap-ux/backend-proxy-middleware README","checked":"2026-10-19","quote":"This will add the x-forwared headers to the proxy requests."},{"url":"https://github.com/preetamkajalrout/ui5-middleware-destination","title":"preetamkajalrout/ui5-middleware-destination — README","checked":"2026-10-19","quote":"Works with destinations from destination files, as WebIDE does"},{"url":"https://www.npmjs.com/package/ui5-middleware-approuter","title":"ui5-middleware-approuter — npm","checked":"2026-10-19","quote":"UI5 middleware using the @sap/approuter to connect against Cloud Foundry or XS Advanced destinations"}]}},"framing_by_ecosystem":{"btp":{"description":"This is a BTP capability first and a CAP one second. [SAP Destination service](artifact:btp-destination) is where the address and the credentials live, resolved at runtime; the framework support for reading them is a client of it. An application holds no URL and no secret of its own, and the same code reaches a different system in every landscape."},"ui5":{"description":"A UI5 app calls a path on its own origin, and whatever serves it maps that path to a destination. On this door the question is the dev server: reaching the same system the deployed route names without writing its address into the project."}},"history":[{"date":"2026-09-09","field":"ecosystems","from":"cap","to":"cap, btp","reason":"The BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install."},{"date":"2026-09-13","field":"name","from":"Destinations and connectivity","to":"Destinations","reason":"The map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans."},{"date":"2026-09-18","field":"core_coverage.state","from":"core-only","to":"core-and-community","reason":"The earlier assessment rested on every provider being SAP-official and said in its own note that a community alternative appearing would make core-only wrong. [cdse](artifact:cdse) is one: it reads the destination from the CAP configuration and makes the call with [axios](external:axios), and it is independent. The samples that demonstrate this capability are unaffected, since a sample is evidence and not an option. The relationship is recorded as unassessed because nothing checked here says how the two came to be present side by side."},{"date":"2026-09-27","field":"core_coverage.what_core_does","from":"none, read from the providers","to":"the connectivity component, from the Outbound Authentication and Remote Services pages","reason":"P1 backfill 2026-09-27: the paragraph shared no page with the runtime edge because it had no page at all. capire documents the connectivity component under Outbound Authentication; the paragraph now rests on it and on the pages the edge cites."},{"date":"2026-10-19","field":"ecosystems","from":"cap, btp","to":"cap, btp, ui5","reason":"ui5-middleware-destination was staged in intake-20261019-bestofui5 under ui5-build-tooling; its drafter left out a destinations edge because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware."},{"date":"2026-10-26","field":"coverage_by_ecosystem.btp.note","from":"Every provider behind this door is an SAP BTP service, so core-only is a assessment of the corpus rather than a quote from the core. what_core_does is left empty: ...","to":"Names SAP Private Link Service and btp-cloud-connector-setup-automation as the SAP pieces around the destination.","reason":"Reassessed against the graph (check:capabilities): the old note was an absence claim about the providers and went stale as providers arrived; the note now says what SAP adds beyond the Destination service, from the providers' own provides edges."},{"date":"2026-10-26","field":"coverage_by_ecosystem.ui5.state, coverage_by_ecosystem.ui5.relationship","from":"core-and-community, relationship unassessed","to":"core-only, relationship removed","reason":"Reassessed against the graph (check:capabilities): the core is present through the sourced what_core_does on SAP's backend-proxy-middleware, but no artifact provides this capability on the UI5 door; the community middleware entries provide ui5-build-tooling. The community_adds text is kept as a sourced fact."},{"date":"2026-10-26","field":"coverage_by_ecosystem.ui5.community_adds","from":"[ui5-middleware-destination](https://github.com/preetamkajalrout/ui5-middleware-destination) reads ...","to":"[ui5-middleware-destination](artifact:preetamkajalrout-ui5-middleware-destination) reads ...","reason":"Reassessed against the graph (check:capabilities): the entry is in the graph, so the name links to it and not to its repository (WRITING section 3.6)."}],"normative_relevance":[{"instrument":"instrument:sap-developer-license-3-2-cap","prominence":"contextual","sections":["1"],"applies_when":"A destination used by a covered CAP application sends SAP product data to a non-SAP product rather than only addressing a remote endpoint.","note":"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.","applies_to":{"ecosystems":["cap"]},"sources":[{"url":"https://cap.cloud.sap/resources/license/developer-license-3_2_CAP.txt","title":"SAP Developer License Agreement 3.2 CAP","checked":"2026-09-16","quote":"permit mass data extraction from an SAP product to a non-SAP product"}]}],"drafted_with_ai":true},"sap_delivery":{"door":"cap","all":{"built_in":[{"ref":"artifact:sap-cds","name":"@sap/cds","json":"/artifacts/sap-cds.json"}],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:sap-cloud-sdk-connectivity","name":"@sap-cloud-sdk/connectivity","json":"/artifacts/sap-cloud-sdk-connectivity.json"},{"ref":"artifact:sap-cloud-sdk-http-client","name":"@sap-cloud-sdk/http-client","json":"/artifacts/sap-cloud-sdk-http-client.json"},{"ref":"artifact:sap-cloud-sdk-odata-common","name":"@sap-cloud-sdk/odata-common","json":"/artifacts/sap-cloud-sdk-odata-common.json"},{"ref":"artifact:sap-cloud-sdk-openapi","name":"@sap-cloud-sdk/openapi","json":"/artifacts/sap-cloud-sdk-openapi.json"},{"ref":"artifact:sap-cloud-sdk-resilience","name":"@sap-cloud-sdk/resilience","json":"/artifacts/sap-cloud-sdk-resilience.json"},{"ref":"artifact:sap-cloud-sdk-util","name":"@sap-cloud-sdk/util","json":"/artifacts/sap-cloud-sdk-util.json"},{"ref":"artifact:capire-s4","name":"capire/s4","json":"/artifacts/capire-s4.json"},{"ref":"artifact:cap-java-cds-feature-remote-odata","name":"com.sap.cds:cds-feature-remote-odata","json":"/artifacts/cap-java-cds-feature-remote-odata.json"},{"ref":"artifact:cap-java-cds-integration-cloud-sdk","name":"com.sap.cds:cds-integration-cloud-sdk","json":"/artifacts/cap-java-cds-integration-cloud-sdk.json"}]},"by_flavor":{"node":{"built_in":[{"ref":"artifact:sap-cds","name":"@sap/cds","json":"/artifacts/sap-cds.json"}],"documented_pattern":[],"announced":[],"packages":[]},"java":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:cap-java-cds-feature-remote-odata","name":"com.sap.cds:cds-feature-remote-odata","json":"/artifacts/cap-java-cds-feature-remote-odata.json"},{"ref":"artifact:cap-java-cds-integration-cloud-sdk","name":"com.sap.cds:cds-integration-cloud-sdk","json":"/artifacts/cap-java-cds-integration-cloud-sdk.json"}]}}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:sap-cloud-sdk-connectivity","name":"@sap-cloud-sdk/connectivity","json":"/artifacts/sap-cloud-sdk-connectivity.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-cloud-sdk-http-client","name":"@sap-cloud-sdk/http-client","json":"/artifacts/sap-cloud-sdk-http-client.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-cloud-sdk-odata-common","name":"@sap-cloud-sdk/odata-common","json":"/artifacts/sap-cloud-sdk-odata-common.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-cloud-sdk-openapi","name":"@sap-cloud-sdk/openapi","json":"/artifacts/sap-cloud-sdk-openapi.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-cloud-sdk-resilience","name":"@sap-cloud-sdk/resilience","json":"/artifacts/sap-cloud-sdk-resilience.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-cloud-sdk-util","name":"@sap-cloud-sdk/util","json":"/artifacts/sap-cloud-sdk-util.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sap-cds","name":"@sap/cds","json":"/artifacts/sap-cds.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:sapmentors-cds-scp-api","name":"@sapmentors/cds-scp-api","json":"/artifacts/sapmentors-cds-scp-api.json","ecosystem":"cap","origin_ring":"community-org"},{"ref":"artifact:sap-samples-btp-cloud-connector-setup-automation","name":"btp-cloud-connector-setup-automation","json":"/artifacts/sap-samples-btp-cloud-connector-setup-automation.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:capire-s4","name":"capire/s4","json":"/artifacts/capire-s4.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:cdse","name":"cdse","json":"/artifacts/cdse.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:cap-java-cds-feature-remote-odata","name":"com.sap.cds:cds-feature-remote-odata","json":"/artifacts/cap-java-cds-feature-remote-odata.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:cap-java-cds-integration-cloud-sdk","name":"com.sap.cds:cds-integration-cloud-sdk","json":"/artifacts/cap-java-cds-integration-cloud-sdk.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:btp-destination","name":"SAP Destination service","json":"/artifacts/btp-destination.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:btp-private-link-service","name":"SAP Private Link Service","json":"/artifacts/btp-private-link-service.json","ecosystem":"btp","origin_ring":"sap-official"}],"samples":[{"ref":"artifact:martinpankraz-az-private-linky-cap","name":"az-private-linky-cap","json":"/artifacts/martinpankraz-az-private-linky-cap.json"},{"ref":"artifact:sap-samples-btp-private-link-approuter","name":"btp-private-link-approuter","json":"/artifacts/sap-samples-btp-private-link-approuter.json"},{"ref":"artifact:miyasuta-cap-ams-a2a","name":"cap-ams-a2a","json":"/artifacts/miyasuta-cap-ams-a2a.json"},{"ref":"artifact:miyasuta-cap-external-northwind","name":"cap-external-northwind","json":"/artifacts/miyasuta-cap-external-northwind.json"},{"ref":"artifact:miyasuta-cap-oauth-destination","name":"cap-oauth-destination","json":"/artifacts/miyasuta-cap-oauth-destination.json"},{"ref":"artifact:miyasuta-cap-openai","name":"cap-openai","json":"/artifacts/miyasuta-cap-openai.json"},{"ref":"artifact:miyasuta-cap-openapi","name":"cap-openapi","json":"/artifacts/miyasuta-cap-openapi.json"},{"ref":"artifact:miyasuta-cap-principal-propagation","name":"cap-principal-propagation","json":"/artifacts/miyasuta-cap-principal-propagation.json"},{"ref":"artifact:miyasuta-cap-rfc","name":"cap-rfc","json":"/artifacts/miyasuta-cap-rfc.json"},{"ref":"artifact:miyasuta-cap-ui","name":"cap-ui","json":"/artifacts/miyasuta-cap-ui.json"},{"ref":"artifact:sap-samples-private-link-aws-services","name":"private-link-aws-services","json":"/artifacts/sap-samples-private-link-aws-services.json"},{"ref":"artifact:sap-samples-cap-service-integration-codejam","name":"SAP-samples/cap-service-integration-codejam","json":"/artifacts/sap-samples-cap-service-integration-codejam.json"},{"ref":"artifact:sap-samples-cross-stack-partner-reference-extension","name":"SAP-samples/cross-stack-partner-reference-extension","json":"/artifacts/sap-samples-cross-stack-partner-reference-extension.json"}],"explained_by":[{"ref":"content:no-code-mcp-servers-with-sap-integration-suite-from-rest-api-to-ai-agent","name":"No-Code MCP Servers with SAP Integration Suite: From REST API to AI Agent","json":"/content/no-code-mcp-servers-with-sap-integration-suite-from-rest-api-to-ai-agent.json"},{"ref":"content:cap-foundry-engineering-sap-cap-applications-from-business-intent-with-guardrail","name":"CAP Foundry: Engineering SAP CAP Applications from Business Intent with Guardrailed AI","json":"/content/cap-foundry-engineering-sap-cap-applications-from-business-intent-with-guardrail.json"},{"ref":"content:connect-sap-cap-nodejs-to-private-postgresql-using-cloud-connector","name":"Connect SAP CAP (Node.js) to On-Premise/Private PostgreSQL using SAP Cloud Connector","json":"/content/connect-sap-cap-nodejs-to-private-postgresql-using-cloud-connector.json"},{"ref":"content:expose-s-4hana-cloud-odata-api-as-an-mcp-server-via-cap-node-js","name":"Expose S/4HANA Cloud OData API as an MCP Server via CAP Node.js","json":"/content/expose-s-4hana-cloud-odata-api-as-an-mcp-server-via-cap-node-js.json"},{"ref":"content:principal-propagation-from-btp-web-app-to-s-4hana-via-sap-integration-suite","name":"Principal Propagation from BTP Web App to S/4HANA via SAP Integration Suite","json":"/content/principal-propagation-from-btp-web-app-to-s-4hana-via-sap-integration-suite.json"},{"ref":"content:using-rfc-function-modules-and-bapis-in-sap-build-process-automation","name":"Using RFC Function Modules and BAPIs in SAP Build Process Automation","json":"/content/using-rfc-function-modules-and-bapis-in-sap-build-process-automation.json"},{"ref":"content:creating-an-sap-sd-billing-document-using-a-bapi-in-sap-build-and-accessing-it-t","name":"Creating an SAP SD Billing Document Using a BAPI in SAP Build and Accessing It Through 'Joule Work'","json":"/content/creating-an-sap-sd-billing-document-using-a-bapi-in-sap-build-and-accessing-it-t.json"},{"ref":"content:fullstack-cap-with-hana-cloud-part-5-btp-destination","name":"Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-5]","json":"/content/fullstack-cap-with-hana-cloud-part-5-btp-destination.json"},{"ref":"content:building-custom-joule-skills-via-rfc-guide-for-sap-s-4hana-and-ecc-integration","name":"Building Custom Joule Skills via RFC: Guide for SAP S/4HANA and ECC Integration","json":"/content/building-custom-joule-skills-via-rfc-guide-for-sap-s-4hana-and-ecc-integration.json"},{"ref":"content:implementing-dynamic-subaccount-based-routing-in-sap-cap","name":"Implementing Dynamic Subaccount-Based Routing in SAP CAP with SAP BTP Destinations","json":"/content/implementing-dynamic-subaccount-based-routing-in-sap-cap.json"},{"ref":"content:sap-btp-platform-technical-user-for-ctms-integration","name":"SAP BTP Platform Technical User for CTMS Integration","json":"/content/sap-btp-platform-technical-user-for-ctms-integration.json"},{"ref":"content:ui-for-the-btp-application-vulnerability-report","name":"UI for the BTP Application Vulnerability Report","json":"/content/ui-for-the-btp-application-vulnerability-report.json"},{"ref":"content:use-rest-services-in-graph","name":"Use REST services in Graph","json":"/content/use-rest-services-in-graph.json"},{"ref":"content:architecting-saas-resilience-against-s4hana-variance","name":"Part 2: Architecting SaaS Resilience Against S/4HANA Variance","json":"/content/architecting-saas-resilience-against-s4hana-variance.json"},{"ref":"content:connectivity-between-a-local-cap-runtime-and-on-premise-systems","name":"Establishing connectivity between a local CAP runtime and on-premise systems","json":"/content/connectivity-between-a-local-cap-runtime-and-on-premise-systems.json"},{"ref":"content:from-rest-to-datasphere-a-cap-based-integration-approach","name":"From REST to Datasphere: A CAP-based Integration Approach","json":"/content/from-rest-to-datasphere-a-cap-based-integration-approach.json"},{"ref":"content:configuring-sap-cloud-integration-for-an-ibp-to-s-4hana-on-prem-private-cloud-in","name":"Configuring SAP Cloud Integration for an IBP to S/4HANA (on prem / private cloud) integration","json":"/content/configuring-sap-cloud-integration-for-an-ibp-to-s-4hana-on-prem-private-cloud-in.json"},{"ref":"content:sending-emails-from-sap-cap-applications-with-any-smtp-provider","name":"Sending Emails from SAP CAP Applications with Any SMTP Provider","json":"/content/sending-emails-from-sap-cap-applications-with-any-smtp-provider.json"},{"ref":"content:call-a-remote-odata-api-from-a-local-cap-java-project","name":"How to Call a Remote OData API from Your Local CAP Java Project","json":"/content/call-a-remote-odata-api-from-a-local-cap-java-project.json"},{"ref":"content:exposing-sap-s4-onprem-data-to-external-system-odata-service-btp-destination-con","name":"Exposing SAP S4 Onprem data to external System || Odata Service || BTP || Destination-Connectivity","json":"/content/exposing-sap-s4-onprem-data-to-external-system-odata-service-btp-destination-con.json"},{"ref":"content:connect-to-a-public-cloud-api-in-nodejs-via-authorisation-code","name":"Connect to Public Cloud API in Node.js via Authorisation Code","json":"/content/connect-to-a-public-cloud-api-in-nodejs-via-authorisation-code.json"},{"ref":"content:extending-sap-sales-and-service-cloud-v2-using-cap","name":"Extending SAP Sales and Service Cloud V2 Using CAP","json":"/content/extending-sap-sales-and-service-cloud-v2-using-cap.json"},{"ref":"content:set-up-the-sap-cloud-connector-integrating-on-premise-systems-with-cloud-service","name":"Set up the SAP Cloud Connector: Integrating On‑Premise Systems with Cloud Services","json":"/content/set-up-the-sap-cloud-connector-integrating-on-premise-systems-with-cloud-service.json"},{"ref":"content:consuming-data-from-sap-datasphere-in-cap-applications","name":"Consuming data from SAP Datasphere in SAP BTP CAP Applications","json":"/content/consuming-data-from-sap-datasphere-in-cap-applications.json"},{"ref":"content:developing-mobile-apps-with-sap-build","name":"Developing Mobile Apps with SAP Build","json":"/content/developing-mobile-apps-with-sap-build.json"},{"ref":"content:configure-journal-entry-posting-approval-from-store-template-in-build-process-au","name":"Configure Journal Entry Posting Approval from Store Template in Build Process Automation","json":"/content/configure-journal-entry-posting-approval-from-store-template-in-build-process-au.json"},{"ref":"content:microsoft-sentinel-for-sap-goes-agentless","name":"Microsoft Sentinel for SAP goes agentless","json":"/content/microsoft-sentinel-for-sap-goes-agentless.json"},{"ref":"content:develop-and-deploy-a-html-angular-vue-react-app-on-sap-btp-access-s-4-op-part-ii","name":"Develop and deploy a HTML (Angular/Vue/React) app on SAP BTP access S/4 OP, Part III","json":"/content/develop-and-deploy-a-html-angular-vue-react-app-on-sap-btp-access-s-4-op-part-ii.json"},{"ref":"content:hey-abap-cloud-please-let-me-save-my-data-export-to-azure-storage-please-part-4","name":"Hey ABAP Cloud please let me save my data export to Azure Storage please🥺🙏- part 4","json":"/content/hey-abap-cloud-please-let-me-save-my-data-export-to-azure-storage-please-part-4.json"},{"ref":"content:btp-launchpad-sapui5-cpi-iflow","name":"从BTP Launchpad里的sapui5应用里调用部署的CPI IFLOW","json":"/content/btp-launchpad-sapui5-cpi-iflow.json"},{"ref":"content:cap-service-to-fetch-create-sales-order-in-s4-hana-public-cloud","name":"CAP Service to Fetch + Create Sales Order in S4 HANA Public Cloud","json":"/content/cap-service-to-fetch-create-sales-order-in-s4-hana-public-cloud.json"},{"ref":"content:sap-btp-destinations-in-a-nutshell-part-1-motivation-noauthentication-destinatio","name":"SAP BTP Destinations in a Nutshell Part 1 - Motivation & NoAuthentication Destinations","json":"/content/sap-btp-destinations-in-a-nutshell-part-1-motivation-noauthentication-destinatio.json"},{"ref":"content:sap-successfactors-extensibility-from-btp-kyma-runtime","name":"SAP SuccessFactors extensibility easy with SAP BTP, Kyma runtime","json":"/content/sap-successfactors-extensibility-from-btp-kyma-runtime.json"},{"ref":"content:sending-email-through-an-on-premise-mail-destination-from-cap","name":"Connecting On Premise Mail Destination and Sending Email Using SAP Cloud SDK JavaScript Version 3 on SAP CAP","json":"/content/sending-email-through-an-on-premise-mail-destination-from-cap.json"},{"ref":"content:surviving-and-thriving-with-the-sap-cloud-application-programming-model-local-de","name":"Surviving and Thriving with the SAP Cloud Application Programming Model: Local development hurdles","json":"/content/surviving-and-thriving-with-the-sap-cloud-application-programming-model-local-de.json"},{"ref":"content:cap-application-with-successfactors-and-hana-cloud","name":"SFSFとHANA Cloudを使用するCAPのアプリケーション開発","json":"/content/cap-application-with-successfactors-and-hana-cloud.json"},{"ref":"content:how-to-connect-to-remote-services-locally-in-a-cap-application","name":"BTP CAP : How to Connect to Remote Services Locally in CAP Application","json":"/content/how-to-connect-to-remote-services-locally-in-a-cap-application.json"},{"ref":"content:architecting-multiple-s4hana-backends-with-principal-propagation-part-1","name":"Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]","json":"/content/architecting-multiple-s4hana-backends-with-principal-propagation-part-1.json"},{"ref":"content:architecting-multiple-s4hana-backends-with-principal-propagation-part-2","name":"Part2: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]","json":"/content/architecting-multiple-s4hana-backends-with-principal-propagation-part-2.json"},{"ref":"content:architecting-multiple-s4hana-backends-with-principal-propagation-part-3","name":"Part 3: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]","json":"/content/architecting-multiple-s4hana-backends-with-principal-propagation-part-3.json"},{"ref":"content:html5-timeout-for-cap-destinations-in-mta-yaml","name":"HTML5.Timeout for CAP destinations in mta.yaml longer than default","json":"/content/html5-timeout-for-cap-destinations-in-mta-yaml.json"},{"ref":"content:useful-cap-cds-and-fiori-commands-to-accelerate-development-and-deployment","name":"Useful CAP CDS and Fiori Commands to Accelerate Development and Deployment","json":"/content/useful-cap-cds-and-fiori-commands-to-accelerate-development-and-deployment.json"},{"ref":"content:qualtrics-integration-with-domain-based-authorization-in-a-cap-project","name":"Qualtrics integration with domain based authorization in CAP project on HANA cloud","json":"/content/qualtrics-integration-with-domain-based-authorization-in-a-cap-project.json"},{"ref":"content:invoke-openapi-documented-apis-remotely-with-cap","name":"Invoke OpenAPI-documented APIs remotely with SAP Cloud Application Programming Model","json":"/content/invoke-openapi-documented-apis-remotely-with-cap.json"},{"ref":"content:execute-oauth2-client-credentials-protected-rest-request-from-cap","name":"Execute [OAuth2 client credentials] protected REST request with SAP CAP Application","json":"/content/execute-oauth2-client-credentials-protected-rest-request-from-cap.json"},{"ref":"content:extend-sap-successfactors-on-sap-btp-with-cap-import-sap-successfactors-odata-se","name":"Extend SAP SuccessFactors on SAP BTP with CAP - Import SAP SuccessFactors OData Services definitions","json":"/content/extend-sap-successfactors-on-sap-btp-with-cap-import-sap-successfactors-odata-se.json"},{"ref":"content:sap-cap-remote-services-and-sap-fiori-elements","name":"SAP CAP Remote Services & SAP Fiori Elements","json":"/content/sap-cap-remote-services-and-sap-fiori-elements.json"},{"ref":"content:building-an-s4hana-cloud-extension-with-cap-cloud-sdk-and-fiori-elements-part-2","name":"Part 2: How to build an extension application for SAP S/4HANA Cloud using CAP, SAP Cloud SDK and SAP Fiori elements","json":"/content/building-an-s4hana-cloud-extension-with-cap-cloud-sdk-and-fiori-elements-part-2.json"},{"ref":"content:building-an-s4hana-cloud-extension-with-cap-cloud-sdk-and-fiori-elements-part-1","name":"Part 1: How to build an extension application for SAP S/4HANA Cloud using CAP, SAP Cloud SDK and SAP Fiori elements","json":"/content/building-an-s4hana-cloud-extension-with-cap-cloud-sdk-and-fiori-elements-part-1.json"},{"ref":"content:cap-consume-external-service-part-3","name":"CAP: Consume External Service – Part 3","json":"/content/cap-consume-external-service-part-3.json"},{"ref":"content:how-to-access-on-premise-odata-from-bas-in-capm-development","name":"How to Access On-premise OData from the Business Application Studio - CAPM Development","json":"/content/how-to-access-on-premise-odata-from-bas-in-capm-development.json"},{"ref":"content:use-the-destination-service-in-nodejs-locally","name":"Use SCP CF Destination service in NodeJs locally","json":"/content/use-the-destination-service-in-nodejs-locally.json"},{"ref":"content:cap-deep-insert-5-consume-remote-service-with-cloud-sdk","name":"SAP Cloud Application Programming Model: Deep Insert (5) Consume Remote Service with SAP Cloud SDK","json":"/content/cap-deep-insert-5-consume-remote-service-with-cloud-sdk.json"},{"ref":"content:cap-deep-insert-4-consume-remote-service","name":"SAP Cloud Application Programming Model: Deep Insert (4) Consume Remote Service","json":"/content/cap-deep-insert-4-consume-remote-service.json"},{"ref":"content:sap-group-consume-remote-services-in-a-full-stack-cap-application","name":"Consume Remote Services in a Full-Stack CAP Application","json":"/content/sap-group-consume-remote-services-in-a-full-stack-cap-application.json"},{"ref":"content:sap-mission-extend-successfactors-with-cap","name":"Extend SAP SuccessFactors on SAP BTP with the SAP Cloud Application Programming Model","json":"/content/sap-mission-extend-successfactors-with-cap.json"},{"ref":"content:sap-tutorial-cap-soap-service","name":"Consume SOAP Web Services in SAP Cloud Application Programming Model","json":"/content/sap-tutorial-cap-soap-service.json"},{"ref":"content:sap-tutorial-cloudsdk-integrate-cap","name":"Use the SAP Cloud SDK in the SAP Cloud Application Programming Model","json":"/content/sap-tutorial-cloudsdk-integrate-cap.json"}],"normative_context":[{"ref":"instrument:sap-developer-license-3-2-cap","name":"SAP Developer License Agreement","json":"/instruments/sap-developer-license-3-2-cap.json","prominence":"contextual","sections":["1"]}]}}