We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:
- Java libraries in version 3.13.0
- Java libraries in version 2.28.0
At the end of the article, you will find a set of instructions on how to update to the new versions.
Java Libraries: Release Highlights 3.13.0
You can update your dependencies of the SAP Cloud SDK for Java to version 3.13.0 and consume the new version from Maven Central.
WorkItems in the service Commercial Project – Read is no longer allowed as of SAP S/4HANA Cloud release 2002. Thus, the method
updateWorkItem() was removed from
CommercialProjectService. Please review your implementation in case you use this service.
OData client: The updated OData client library includes completely new services (available as usual in package com.sap.cloud.sdk.s4hana.datamodel.odata.services), new operations in previously existing services, and new entity types according to the latest updates in the release 2002 of SAP S/4HANA Cloud.
Several further improvements are listed in the full release notes.
Java Libraries: Release Highlights 2.28.0
We have also released the SDK for Java in a new maintenance version 2.28.0. Everyone who did not yet upgrade to version 3 of the SDK for Java can consume that version from Maven Central.
For a complete view on what has changed, take a look at the full release notes.
OData client: The updated OData client library includes completely new services (available as usual as global modules called
@sap/cloud-sdk-vdm-*), new operations in previously existing services, and new entity types according to the latest updates in the release 2002 of SAP S/4HANA Cloud.
In this release, the SAP Cloud SDK considers the variables
https_proxy for configuring proxy settings for outbound requests, that do not use the SAP Cloud Connector. The
no_proxy variables can be used to exclude certain destinations from using the proxy. See
ProxyConfiguration for more details.
As usual, the full release notes contain a list of all improvements in this release.
How to Update
To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:
- Open the pom.xml file in the root folder of your project.
- Locate the dependency management section and therein the
- Update the version of that dependency to
With this, you are already done thanks to the “bill of material” (BOM) approach. Your dependency should look like this:
<dependencyManagement> <dependencies> <dependency> <groupId>com.sap.cloud.sdk</groupId> <artifactId>sdk-bom</artifactId> <version>3.13.0</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> <!-- possibly further managed dependencies ... --> </dependencyManagement>
If you update from a version prior to 3.0.0, have a look at our migration guide.
If you are using the SAP Cloud SDK in a project of the SAP Cloud Application Programming Model, replace
sdk-modules-bom to only update the version of SDK modules, not further dependencies.
You can now recompile your project (be aware of the compatibility notes, though) and leverage the new features of the SAP Cloud SDK in version 3.13.0.
Of course, you can also generate a new project that uses version 3.13.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with
npm update in the root folder of your module. Note that this will also update other modules, unless you explicitly specify which packages to update. If you want to check beforehand what will change, use
SAP SuccessFactors Learning in the pipeline?
Thank you for your comment. Are you asking about a SuccessFactors learning on SAP Cloud SDK or about consuming the learning API using the SDK?