In June 2020 we have launched a brand new documentation portal which consolidates all the knowledge, feature documentation, comprehensive guides, video tutorials, troubleshooting, release notes, API documentation, and more. Please, use it as a single reference point about SAP Cloud SDK. From now on it’s the most complete and up-to-date source of information about the product.
This is a collection of answers to frequently asked questions (FAQ) about the SAP Cloud SDK, announced today.
We have announced the SAP Cloud SDK as the easiest way to interact with SAP solutions when developing Cloud-native applications. The SAP Cloud SDK is based on and replaces the previously available SAP S/4HANA Cloud SDK. It draws on the existing capabilities of the SDK to communicate to many SAP solutions.
The SAP Cloud SDK reduces development effort, improves quality, and helps adopting Cloud-native best practices when developing applications that interact with SAP solutions. The SAP Cloud SDK is a set of components to consume services and messages* of many SAP solutions in the Cloud and on-premise, access services of SAP Cloud Platform, continuously deliver Cloud-native applications on SAP Cloud Platform. For more information, read the news article and the technical blog post.
The SAP Cloud SDK is the next evolution of the SAP S/4HANA Cloud SDK. It consists of the components known from the SAP S/4HANA Cloud SDK, now rebranded as SAP Cloud SDK. Users of the SAP S/4HANA Cloud SDK do not need to adapt and can leverage the capabilities of the SAP Cloud SDK immediately for also accessing other SAP solutions beyond SAP S/4HANA.
You can continue to use the components of the SAP S/4HANA Cloud SDK as before, now under the new name. We have not changed any technical artifacts names. You are in a good position to then leverage the SAP Cloud SDK.
No, you do not need to migrate your code in order to leverage the SAP Cloud SDK. The technical artifacts that you know from the SAP S/4HANA Cloud SDK are the same ones used by the SAP Cloud SDK. We did not change any names of technical artifact. Note: in a future release of the SDK, we plan to deliver updates to names and other improvements. We will clearly explain this once the new major version is available. For now, continue to use the SAP Cloud SDK.
No, the SAP Cloud SDK does not replace the SAP Cloud Application Programming Model. The SAP Cloud SDK is rather an integral part of the SAP Cloud Application Programming Model for capabilities for consuming remote services of SAP and other solutions. The SAP Cloud Application Programming Model additionally contains many capabilities for modeling an application’s business domain and automatically exposing this functionality as services.
No, both will typically be used together. Depending on your use case and requirements, you can use SAP Cloud SDK and SAP Cloud Application Programming Model individually or in combination.
The SAP Cloud Application Programming Model supports you in developing business services and applications on SAP Cloud Platform by providing a holistic approach allowing you to model your domain and services in Core Data Services (CDS), to add your business logic and expose it via service APIs. It also allows to import and mash-up APIs of external services. It uses the SAP Cloud SDK for consuming external services, both internally and in code written by users.
The SAP Cloud SDK focuses on giving you the tools and support for developing code that connects to other services such as SAP S/4HANA Cloud, SAP SuccessFactors, SAP Cloud Platform services, and many others in a convenient, secure way ensuring Cloud qualities. Additionally, it contains components for continuously delivering applications that extend SAP solutions such as SAP S/4HANA Cloud.
The SAP Cloud SDK is the strongly recommended approach for accessing other services as well as for continuously delivering projects following the SAP Cloud Application Programming Model. However, you can also decide to not use the capabilities offered by the SAP Cloud SDK. If you do not interact with other services or SAP solutions, you also may not need the capabilities of the SAP Cloud SDK.
The SAP Cloud SDK is also used internally by the SAP Cloud Application Programming Model.
No, both will typically be used together. SAP Cloud Platform Extension Factory gives administrators the capabilities needed to connect SAP systems to their SAP Cloud Platform account and gives developers a consistent approach to discovering and accessing available APIs in connected systems.
The SAP Cloud SDK then gives developers the tools to write source code that calls services in connected systems, and handle messages received from them. Furthermore, the SAP Cloud SDK contains tools to continuously deliver those applications.
Depending on your use-case you can use Extension Factory and SAP Cloud SDK independently or in combination.
No, you don’t have to. However, SAP Cloud SDK offers simplified access to SAP LoB solutions, like SAP S/4HANA by using information and capabilities of Extension Factory.
No, the various SAP Cloud Platform SDKs, for example, for Android, iOS or the Neo environment, are separate SDKs with specific purposes, different than the SAP Cloud SDK.
Yes, SAP Cloud Platform is the target environment of applications built with the SAP Cloud SDK. On SAP Cloud Platform, you get the full convenience for connecting to and communicating with SAP solutions. The continuous delivery pipeline of the SAP Cloud SDK deploys the application to SAP Cloud Platform.
Can I also run application built with the SAP Cloud SDK outside SAP Cloud Platform, for example, on my local machine?
Yes, the libraries of the SAP Cloud SDK, especially the platform abstractions, make it easy to run applications locally where you do not have access to SAP Cloud Platform. This is mostly meant for making testing and debugging easy.