SAP Community - Geert-Jan Klaps

Re: CAP multitenancy - Error on subscription: Tenant 'sap-provisioning' does not exist

2023-07-06T22:35:26+02:00

Hi mioyasutake,

In the meanwhile, I’ve logged a support ticket for this issue. If I get an update, I’ll post it here.

Re: CAP multitenancy - Error on subscription: Tenant 'sap-provisioning' does not exist

2023-07-07T14:52:45+02:00

Hi mioyasutake,

This seems to be fixed in @sap/mtxs 1.9.1!

Regards,

Geert-Jan

CAP 7 - Transaction Already Closed error on SAP HANA Cloud

2023-07-08T13:53:03+02:00

Hi,

After upgrading our multitenant solution to CAP 7, I'm facing an issue when performing multiple UPDATE transactions on HANA Cloud. Important remark, the first update transaction seems to work, as soon as I try to do a second update the server crashes and states: "Transaction already closed in the logs". Multiple SELECT statements don't have issues.

Good to know, this was working perfectly fine on latest CDS 6 release AND works perfectly fine when running the application with CDS 7 in BAS with SQLITE.

We're running all latest package versions and updated all the dependencies to the latest versions.

Code excerpt (1st update works, seconds update crashes the server):

Logs:

Am I doing something wrong here? Something that changed in CDS 7 that I might have missed? Or is this a bug?

Best regards,

Geert-Jan

Re: CAP 7 - Transaction Already Closed error on SAP HANA Cloud

2023-07-10T09:54:00+02:00

Hi willem.pardaens,

Seems I've missed the fact that there's an additional package for sqlite, so at this point I'm still using the old approach, I guess. I'm going to change the dependencies and switch to the new approach for sqlite as well and will come back asap.

Re: CAP 7 - Transaction Already Closed error on SAP HANA Cloud

2023-07-10T10:03:52+02:00

Hi willem.pardaens,

Just switched to the new @cap-js/sqlite package and everything is still working as expected. So the issue still only occurs on SAP HANA Cloud. (double checked the configuration using cds env requires.db and the sqlite package is properly loaded)

Re: CAP 7 - Transaction Already Closed error on SAP HANA Cloud

2023-07-10T11:19:09+02:00

Hi willem.pardaens,

This is really small volume testing, in this case one header record and one item record. Updates are not really in parallel due to the await statements I guess.

Anyway, as I suspected, it's really the second update statement that causes the crash of the server, but when going through the debug log of the database, I noticed a strange thing in the generated SQL statement. So I compared it to the sqlite SQL statement.

On HANA it looks like:

On sqlite it looks like:

Might seem like a bug in the generation of the SQL statements in the HANA DB driver?

Re: CAP 7 - Transaction Already Closed error on SAP HANA Cloud

2023-07-10T18:52:50+02:00

Hi Florin,

Moving all the updates into an array was one of the improvements I was going to implement tomorrow. I'll let you know if this solves anything. (but I'm afraid the end result will be the same, in the end the current implementation worked before the upgrade to CDS 7 and is working fine on sqlite)

Re: Issue on CAP deploy after updating cds/cds-dk with latest version (7.0.2)

2023-07-10T19:15:46+02:00

Hi Alessio,

Did you also update the @sap/cds library and added all the necessary dependencies? As of cds 7, the library became more modular. (e.g. separate libraries for databases, fiori, ...)

If you haven't already, I suggest you go through the release notes of the release and implement all the necessary changes. (there are some breaking changes in major releases)

June 2023 | CAPire (cloud.sap)

Re: CAP 7 - Transaction Already Closed error on SAP HANA Cloud

2023-07-12T14:52:52+02:00

Hi Sebastian,

Thank you for clarifying, reworked the whole logic to perform all database updates without using promises. Strange thing is that this issue doesn't occur on sqlite, so from a development perspective it's hard to determine what the root cause is. (I'm expecting the same issue to occur when running this locally in BAS)

I do think this definitely is in improvement, but I don't seem to find the warning about the new protection mechanism in the release notes. Maybe it would be good to mention it in the release notes as well?

Best regards,

Geert-Jan

CAP Typescript - @cap-js/typer namespace missing

2023-07-31T13:49:09+02:00

Hi,

I'm currently working on switching a project to the new typescript approach using @cap-js/typer. Unfortunately, when using the newly generated types it looks like the namespace is missing when performing CQL queries.

I'm using the same approach as described here in the documentation.

Code sample:

When the query get executed, it fails to due to the namespace not being present in the SQL query:

I'm using following package versions:

@cap-js/cds-typer: 0.5.0
@cap-js/sqlite: 1.0.1
@sap/cds: 7.1.0
@sap/cds-compiler: 4.0.2
@sap/cds-dk: 7.0.3
@sap/cds-dk (global): 7.0.3
@sap/cds-fiori: 1.0.0
@sap/cds-foss: 4.0.2
@sap/cds-mtxs: 1.9.2
@sap/eslint-plugin-cds: 2.6.3
@thevaluechain/cap-number-range: 1.1.5
Node.js: v16.19.0
home: /home/user/projects/icm-reuse-numberrange/node_modules/@sap/cds

Am I missing something here? Any pointers on how to get this resolved?

Geert-Jan

Re: CAP Typescript - @cap-js/typer namespace missing

2023-07-31T14:31:33+02:00

Hi 20eed143c19f4b82bc4cf049916102cb,

I'm going to that right away, completely looked over the fact that there's a public repo available 🙂

Cheers,

Geert-Jan

Event: SAP Community watch-and-code party (3rd of November, Kontich)

2023-09-29T08:25:11.723000+02:00

With SAP Inside Track Belgium in our rear view mirror, we're already looking forward to our next SAP Community Event: SAP Community watch-and-code party in Friday 3rd of November. The concept is quite straight forward and serves as a local alternative to SAP TechEd which is hosted only in Bangalore this year. You can read more on the concept here.

We hope to welcome you all again for a day full of content, hands-on sessions and networking opportunities!

What to expect?

Time	Topic
10:00 - 10:30 a.m.	Welcome and Introduction
10:30 - 12:30 p.m.	Keynote SAP TechEd & Expert Q&A Session
12:30 p.m.	Lunch & Drinks
1:45 - 3:45 p.m.	Mini Code Jam Session
4:00 - 5:30 p.m.	Learnings
5:30 p.m. - ...	Afterwork Snacks & Drinks

Location

Satenrozen 10, 2550 Kontich (Belgium).

Registration

Want to attend? Great! You can register here.

Hope to see you there!

cds-launchpad-plugin supercharged & ready for the future - CAP Plugin, UI5 Tooling support & Async Launchpad

2023-12-11T08:43:46+01:00

If you're developing SAP CAP-based applications in combination SAPUI5 apps, you might already be familiar with the cds-launchpad-plugin. The plugin allows you to easily test all your apps in a single launchpad by automatically indexing all SAPUI5 projects in your workspace and providing the necessary configuration to a sandbox launchpad.

Recently the plugin has undergone some major changes, in this blog I'll guide you through the most important changes, how you can enable them & why they are beneficial to enable.

SAPUI5 strategy & direction

SAPUI5 is evolving fast and since recently there's official support for TypeScript (as of SAPUI5 1.116) using the UI5 Tooling. The future is even more bright with the release of SAPUI5 v2.0 which introduces the removal of deprecated API's (slimming down the library dramatically and thus improving the performance) and the move to Async API's only.

Future strategy of SAPUI5 announced at UI5con 2023 (credits stefan.beck & peter.muessig)

CAP Plugin technique

With the release of CAP 6.7.0 the new plugin technique was introduced. Up until a few weeks ago, the cds-launchpad-plugin still needed a custom server.js file to be activated. Luckily, smarten was kind enough to introduce the CAP plugin technique in the cds-launchpad-plugin.

This means you can now just install the plugin as a dev dependency and it get activated automatically. If you want to configure custom plugin settings, you can still do so in the package.json file.

Installation

npm install --save-dev cds-launchpad-plugin

Custom configuration:

"cds": {

  "launchpad": {

    theme:'sap_horizon', // SAPUI5 Theme

    version: '1.120.1', // SAPUI5 Version

    basePath: '', // Path under which you want the sandbox to be served

    appConfigPath: '', // External sandbox appconfig json file to be merged with generated appconfig

    locale: '', // Language to be used for the sandbox environment

    template: '' // 'legacy' (non-async launchpad, default) or 'async' (async launchpad)

  }

}

UI5 Tooling support

A few weeks back, thanks to the efforts of peter.muessig, the cds-plugin-ui5 was introduced to bridge the gap between CAP & SAPUI5 development.

The library integrates the UI5 Tooling into the default CAP server, which means you're now able to use a single server to perform both CAP & SAPUI5 developments, leveraging the power of both development tools in one.

The cds-launchpad-plugin now automatically detects the cds-plugin-ui5 presence and changes the way the application descriptors are generated for the launchpad. (side-note, the plugin currently only supports the default routes used by cds-plugin-ui5, customized routes are not supported yet)

This means you're now able to use TypeScript for both CAP & SAPUI5 in combination with the cds-launchpad-plugin!

cds-launchpad-plugin combined with cds-plugin-ui5

Async launchpad

An additional configuration option "template" was introduced, to allow changing the template used to generate the launchpad. You can either leave the template untouched, set it to "legacy" or "async". For now the default setting is still legacy, in the next major release this will probably be switched to async as this is the best-practice and more future-proof.

Good to know, the way the legacy launchpad template is loaded (using the createRenderer method of class sap.ushell.Container) is deprecated as of SAPUI5 1.120.

Why should you use the async template, next to the fact that you'll have to in the future? Performance! In below screenshots you can see the difference when loading a launchpad with the same configuration using both the legacy & async template.

Results: legacy - 9,5 seconds vs async - 2,2 seconds!!

Legacy launchpad performance

Async launchpad performance

Wrap-up

As you can see, quite some changes in only a few weeks, improving the useability & future-proofness of the plugin. Be sure to try them out!

Having troubles or ideas for new features? please use GitHub to report any issues / ideas.

Are you already using the cds-launchpad-plugin? Be sure to leave a comment!

Happy coding!

Usage metrics per tenant / subscription in a multitenant solution

2023-12-11T14:24:48+01:00

Hi,

I'm looking for a solution to easily monitor the consumption of a multitenant solution built on SAP BTP. We have the out-of-the-box global metrics in the provider subaccount but want to be able to monitor certain metrics on the level of the subscription.

Some of the things that pop up in my mind at first sight:

Number of unique logins
HDI container size
SAP Document Management Service Consumption
Number of API calls
...

Is there any re-use service we can implement to get these kind of metrics per subscription? Or is this something we have to build from scratch ourselves?

Best regards,

Geert-Jan

Re: Usage metrics per tenant / subscription in a multitenant solution

2023-12-12T08:19:39+01:00

Thanks for the tip gregorw, I'll log a ticket to see if I can get some more information about it. Will post an update here when I get feedback!

SAP Build Code blog series: 1 - Welcome to the lobby

2024-03-27T09:00:00.033000+01:00

As announced during SAP TechEd in November 2023: SAP has been working on SAP Build Code, a new developer experience to ease pro-code development efforts on SAP Business Technology Platform. Enriching existing solutions and adding a touch of Generative AI, SAP Build Code streamlines development and promotes fusion development (combining low-code / no-code developments with pro-code development).

During the pilot phase, I was one of the lucky ones to be able to test-drive this new developer experience. In this blog series, I’ll give you some insights based on my experience.

(Re)-introducing The Lobby

If you’re familiar with SAP Build Process Automation, SAP Build Apps or SAP Build Work Zone, you’ll already know “The Lobby”. As a pro-code developer using SAP Business Application Studio might have missed this central development experience.

Up until now, “The Lobby” was a central library of all your existing low-code / no-code development projects and allowed you to start new developments based on SAP Build Apps & SAP Build Process Automation. With SAP Build Code, pro-code developments now are also stored and started from within that same user experience.

Let’s have a look at how starting a new project with SAP Build Code looks like! (We’ll use this development project throughout the rest of the blog series, to give you a clear view on the end-to-end development process using SAP Build Code)

Start by clicking the "Create" button on the central right corner of the screen:

You’ll immediately be greeted by a popup to guide through the rest of the process. Based on the enabled services in the subaccount, you’ll see more functionality enabled in this guided experience.

Since we’re here to explore pro-code development using SAP Build Code, this is obviously going to be our choice for today. But as you can see if you have SAP Build Apps enabled, you’ll be able to start your low-code / no-code app development journey from here as well.

Next step is to choose the right type of application you’d like to start. Since I’ll be showing a full end to end development, building both backend & frontend applications, we’ll choose for Full-Stack application here.

As a last step, we’ll need to enter some data to identify our project. As a pro-code developer these settings are already common knowledge. By entering these details here already, SAP Build Code will generate the project with the right project name, namespace and default service name.

SAP Build Code will generate the project and corresponding dev space. Once generation is finished, you can open the dev space by clicking the project name.

To end this part of the blog series, let’s open the dev space. You’ll see the storyboard of the new project with all the necessary elements in place as defined through the guided experience.

This concludes the first part in the blog series, you’ve now learned about the lobby and have setup your first project with SAP Build Code. In the next blog posts we’ll enrich the generated application by using SAP Joule and configure deployment.

Blog series navigation

SAP Build Code blog series: 2 – Kickstarting your project with SAP Joule

2024-03-27T09:01:00.034000+01:00

SAP Build Code comes with SAP Joule as your personal pair developer. If you have never heard of SAP Joule, I recommend you to read this article. To summarize in short, Joule is SAP’s generative AI copilot which will be embedded throughout their product portfolio. You can already activate SAP Joule in SAP SuccessFactors & SAP S/4HANA Cloud (early adopter program) for example.

In this blog we’ll use SAP Joule to generate a data model & some test data for our custom logic.

To open SAP Joule in your dev space, you can use the Joule plugin in the left side of your screen.

Generating a new data model & service for our project

After opening up SAP Joule, the guided experience will show up which allows you to start the SAP Joule experience based on what you want to achieve. In this case we’ll go for “Data Model and Service Creation”.

Once you open Joule with the button in the central of the screen, you’ll be able to provide the input you want to give Joule to generate a new data model and service.

I used following input:

“Create an app to manage sales orders with entities salesorders and salesorderitems where each salesorderitem is linked to its salesorder.”

If you’re happy with Joule’s proposed data model, you can easily accept these changes with the button in the top right corner of the proposal. After accepting the proposal, you’ll see the storyboard gets updated automatically to reflect the changes applied by SAP Joule.

We now have an updated data model and a service reflecting the data model in our project.

Generating test data for our project

As a developer, the development as such is our main responsibility, but what would we be without doing at least some testing to verify that everything is working as expected?

Instead of creating test data manually, we can use SAP Joule to do this for us! Let’s create some test data using SAP Joule! To do this, open up the SAP Joule experience again through the SAP Joule plugin in the left side of the screen.

In the guided experience open the Sample Data topic and open SAP Joule. After opening SAP Joule, you can very easily ask Joule to generate some test data for you.

I’ve used following input: “Generate sample data for entities salesorders and salesorderitems”.

If you’re happy with the test data, you can easily accept the test data with the button in the top right corner of the proposal.

After accepting the test data, you’ll be greeted by the sample data editor where you can very easily browse through the test data.

If you have a close look at the generated sample data, you’ll notice that SAP Joule even took into consideration that the totalAmount of the SalesOrders entity should be the sum of the totalPrice of the SalesOrderItems entity.

SalesOrders entity:

Sales Order Items entity:

Isn’t this beautiful? With only a few simple interactions with SAP Joule, we already have a working backing service with some realistic sample data to test our development in SAP Build Code!

While it is great SAP Joule took into consideration that the totalAmount of our SalesOrders entity should be the sum of our totalPrice of the SalesOrderItems entity, we’d like to see this logic reflected when actually creating / updating a new Sales Order. In the next blog post, we’ll use SAP Joule to add some application logic to this automatically and a unit test to validate the logic applied in our application logic.

Blog series navigation

SAP Build Code blog series: 3 – Adding application logic and unit tests with SAP Joule

2024-03-27T09:02:00.070000+01:00

Up until now, we’ve already covered creating a project through the lobby, we’ve added a basic data model and service to our project including some local testing data. We’ve seen that SAP Joule takes our data model into consideration when generating sample data, as the sum of our item prices is reflected in our sales order header entity as a total amount.

In this blog post we’re going to extend our existing project with application logic to automatically calculate the total amount based on the item prices. And since application logic needs to be tested, we’ll also create a unit test to automatically test our new application logic.

Adding application logic to our project

Fire up the SAP Joule plugin again and choose the “Application Logic” step to get started. Adding application logic takes a few steps, as a first step we’ll need to open up the CDS Graphical Modeler and click the entity we’d like to extend with application logic. Once you’ve selected the entity you’ll notice a small menu appears next to the entity with some options. In this case be sure to click the “Add Logic” button as shown below.

In the “add application logic” screen you’ll need to provide some details about the logic you’d like to implement. In this case we’re aiming to calculate the total value of the order when creating / updating an order, which means we’re going to apply our logic to the service entity. The service entity should already be preselected for you, if not please manually select the SalesOrders entity.

Next to that you’ll need to provide a name for the logic you’d like to implement, in this case I’ve used “calculateTotalAmount”. You can also add an optional description to the logic. Creating the empty application logic handler is just a matter of clicking the “Add” button as shown below.

As a next step define when the application logic should be executed, in this case we’ll use the “on” phase of the CAP handlers and choose the “UPDATE” and “CREATE” events to make sure our total amount is calculated on each update or create of a sales order.

Once you’ve selected the phase and events, open up the code editor with the “Open Code Editor” button, so we can use SAP Joule to generate some logic for us.

After opening the application logic code editor, open SAP Joule through the “Implement Application Logic” step and provide the requirement so SAP Joule can create a proposal implementation. In this case I used the following requirement: “Calculate the total amount based on the item total price”.

If you’re happy with the proposed implementation, accept it through the button in the top right corner of the proposal to add it to the application logic.

We’ve now successfully implemented our application logic to calculate the total amount of the order. In the next step we’ll create a unit test, to automatically validate the implementation during e.g. our build / deployment pipelines.

Adding unit tests to our project

To add a unit test to our project, we have to follow a similar approach as we did to add application logic. In the application logic screen, select the previously created application logic and choose “Open Code Editor”. Now choose the option “Unit test” instead of “Application Logic”.

Now you can use SAP Joule again to generate the unit test. In this case I’ve used following requirement: “Generate a unit test to validate if the total amount is equal to the sum of the total price of the order items”.

After SAP Joule generates a proposal, you’ll even see that you get an explanation of what the test should do below the proposal. If you’re fine with the proposal, you can accept the proposal again using the button in the top right of the proposal to add it to the unit test logic.

We can now test our application through the unit test, by opening a terminal (menu -> terminal -> new terminal) and executing command: “npm run test”. Below I’ve highlighted each step in the unit test and the corresponding result in the terminal.

Running and previewing our backing service

To run the application, simply open the run configurations menu and open the generated run configuration. By clicking the run button, the application will be started with the test data we created earlier.

When you open the running application, you’ll be greeted by a new beautiful overview screen listing both UI applications and backend services. In this case we only have a backend service for now. To preview the service you have two options, with the table view you’ll get a Fiori Elements (list report) preview with the code preview you’ll just see the resulting JSON data.

When opening up the table preview, you’ll notice that when SAP Joule generated our data model it already included the necessary list report annotations and labels.

Opening up the code preview just gives a JSON response with our test data:

We’ve now successfully created a fully functional backend service with application logic, corresponding unit test and are able to run the application in preview mode. In the next blog we’ll see how we can add a SAP Fiori Elements template and deploy it to SAP Business Technology Platform.

Blog series navigation

SAP Build Code blog series: 4 – Adding a SAPUI5 application and deploying to SAP BTP

2024-03-27T09:03:00.059000+01:00

In the previous blog posts, we’ve created a project in which we now have a fully functional CAP backend service, but what is a backend service without a user interface? In this blog post we will extend our project with an SAPUI5-based application and deploy it to SAP Business Technology Platform.

Adding a SAPUI5 application to manage sales orders to our project

In the project story board, click the “+” button under the UI applications section to get started.

In the first step, add a display name, application name and description for your application and click the “next” button.

In the next step, select the type of UI application you want to add to the project. There are two options here, either a Template-Based, Responsive Application (SAPUI5 application) or a Mobile-Centric, Freestyle Application (SAP Mobile Services-based application).

For the sake of simplicity in this blog series, we’ll use a Template-Based, Responsive Application. But now you can perfectly create a native mobile application from here as well leveraging SAP Mobile Services.

Choose the right template you’d like to use; in the case of our project the most logical / recommended template would be the List Report Page.

After selecting the right template, configure the necessary data objects. In this case we’ll just select the SalesOrders entity and select none as the navigation entity.

After finishing the guided experience, the SAPUI5 app will be generated, added to the story board and you’ll see the Fiori Tooling Page Map show up after clicking the UI Application.

There’s no need to do changes at this point, since we saw in the previous blog post that SAP Joule already generated the necessary annotations for our project. If you run the project again, you’ll now see that the project overview also contains an application. By clicking the tile, you can start the application.

Deploying our project to SAP Business Technology Platform

As a final step for our project, we’ll deploy our project to SAP Business Technology Platform. I’m not going to dive into the details on how to prepare your cloud foundry space here, since this is well documented.

Just make sure your cloud foundry organization has access to following services for this example:

Connectivity Service (lite plan)
SAP HANA Schemas & HDI Containers (hdi-shared plan)
Destination Service (lite plan)
HTML5 Application Repository Service (app-host plan)
Application Logging Service (lite plan)
Authorization and Trust Management (application plan)

To deploy the full project to SAP Business Technology Platform, SAP Build Code has a task available. You’ll find the task in the Task Explorer. Open the task and click the “Deploy” button to start the deployment process.

If you’re not logged in to Cloud Foundry yet, you’ll be asked to login to Cloud Foundry and select the space you want to deploy to.

Once the deployment process is complete, you’ll see the overview URL displayed in the terminal.

Going to the SAP Business Technology Platform cockpit you’ll find the HTML5 applications as usual.

Same applies for the backend services.

We’ve now manually deployed our application to SAP Business Technology Platform, which is great! We actually have a fully working application created through generative AI without changing anything manually. (disclaimer: for more complex cases, you’ll need to do manual implementations as well)

In the next blog post, I’ll give you some last insights, personal experience and final thoughts on using SAP Build Code.

Blog series navigation

SAP Build Code blog series: 5 – My personal experience and final thoughts

2024-03-27T09:04:00.036000+01:00

We’ve now completed an end-to-end application development cycle using SAP Build Code. We have a minimal application running which we generated using generative AI offered to us by SAP Joule.

In this last blog post, I’ll give you some last insights and my personal thoughts on SAP Build Code.

Using SAP Build Code from VS Code

Since SAP Build Code uses SAP Business Application Studio as a foundation it is possible to connect SAP Build Code to VS Code using the SAP Business Application Studio Toolkit plugin. I was very happy to see this was still working fine, including all the SAP Build Code plugins (which also includes SAP Joule).

If you’ve never tried this out with Business Application Studio, I suggest you read my previous blog post. (the instructions are identical for SAP Build Code)

My personal experience

It’s been fun to be able to play around with SAP Build Code during the pilot phase. I’m 100% convinced that SAP Build Code can make a difference in terms of development efficiency. The way of working through the lobby definitively feels like SAP is bridging the gap between pro-code developers and low-code / no-code developers, thus improving the so-called fusion development projects.

If you’ve used SAP Business Application Studio before, you’ll definitely find your way through the development flow of SAP Build Code. I didn’t need any specific documentation to get started with SAP Build Code, so in my opinion the way of working in SAP Build Code definitely feels intuitive.

Next to being intuitive and the fact that I was able to generate the application, test data, application logic & unit test using SAP Joule, it really felt like my focus was now more on the pure development process compared to using Business Application Studio. SAP Build Code guided me through generating the right development artifacts and took away the complexity of creating deployment descriptors, so that’s definitely a big plus for me.

My final thoughts

Generative AI has a huge potential and personally I think we’ve seen nothing yet, I’m very interested in seeing what the future holds for us as pro-code developers. However, even though generative AI is a great technology to assist us developers, a fair warning should be issued: never (ever!) blindly trust the results of generative AI! While the proposed solutions may look very promising, this is not always the case. It’s still up to us developers to:

Verify the generated logic
Check if the proposed logic is the most efficient implementation (if not, manually adapt!)
Ensure that the generated logic is not causing bugs with other existing logic
…

To put it in short: we as developers are still responsible for the final result!

When it comes to SAP Build Code, as an experienced developer, I personally hope to see some more advanced features in the future, like for example: TypeScript support, support for existing CAP projects not created with SAP Build Code and combining GitHub Co-pilot with SAP Build Code. As this is the first release of SAP Build Code, which already covers a lot, I’m not calling these a dealbreaker. I’m 100% convinced that we’ll see SAP Build Code’s feature set grow in the coming months and years.

Apart from those more advanced features, I think this definitely is a major game changer for developers setting their first steps into the world of SAP Cloud development or to developers who are not that experienced in SAP Cloud development yet.

All in all, I definitely recommend you to try out SAP Build Code yourself, regardless of the fact that you’re an experienced or a beginner in SAP Cloud Development! Happy (SAP Build) Coding!