Skip to Content
Technical Articles

SAP BTP, Kyma runtime: How to get started

I hope you got excited about the newly launched SAP BTP, Kyma runtime. To get started, follow the steps outlined below.

Enabling the Kyma runtime

A Global Account in SAP BTP which is enabled for the consumption-based model (i.e. has Cloud Credits) is required to use the Kyma Runtime. Start by creating a New Subaccount and selecting “Microsoft Azure” as Provider and any desired Region. Provide the other required values and choose “Create”.

Once the creation of the subaccount has completed, open it and choose the option “Enable Kyma”. Provide a name and description, select “Microsoft Azure” as provider, and select your preferred region where the Kyma runtime should be created.  It will take some time until it’s fully deployed.

Provide Authorization to access Kyma runtime

SAP BTP’s XSUAA is used for the access to the Kyma runtime. Open your sub-account, choose “Security” > “Role collections” and create a “New Role Collection”. Open the newly created item and choose “Add Role”. Search for the technical name of your Kyma runtime which you can get e.g. out of the URL of the Kyma runtime. Assign the “KymaRuntimeNamespaceAdmin” role template to this role collection and save the assignment.

Go back to the subaccount and open the menu item “Trust Configuration”, choose your IDP, and assign the newly created role collection to the respective user by searching for their e-mail address, choosing the option to “Show Assignments” and finally choosing “Assign Role Collection” to assign the role.

In some cases, it will still take 5-10 minutes to get access to Kyma Runtime and you only need to wait. Assigning the Role Collection to the user is the last step you need to do.

Connect your applications

To make use of the newly launched Management Plane service for connecting applications, go back to your Global Account. Open the menu item “System Landscape” > “Systems” in your Global Account. Choose “Register System”, provide a name and select a type for the application you want to connect. Choose “Register” to generate a one-time token which will be used by the application you want to connect. (example descriptions of this process can be found for SAP Commerce Cloud, SAP Cloud for Customer, SAP Field Service Management).

Once the registration is completed, choose the menu item “Formations”, choose “Create Formation”, provide a name, select the subaccount and the just-connected system and finally choose “Create”. This will pair the application to the Kyma runtime.

Important: to connect SAP Cloud for Customer, you need to first create the Formation before using the one-time token in SAP C4C’s configuration.


Additional resources:


You must be Logged on to comment or reply to a post.
  • hi Marco, for C/4 HANA, in particular for C4C - is there an option to use any other runtime apart from Kyma in the context of the Extension Factory? In particular, can I utilize the Extension Factory to extend C4C with an app hosted within SCP?

    (Note that the C4C event notification allows for posting even driven messages either for Extension Factory or to any "external system")


    • Hello Mariusz Cisek,

      As of today, only Kyma can be connected via the "System Landscape" section in the Global Account menu. We have it on our roadmap to add the other runtimes in the same way which is when it will become fully harmonized.

      Best regards,

      • Thanks Marco Dorn . Just to be clear. My question was if C/4 products (including C4C) can be also extended with apps running in SCP (as it is described here for S/4 and SF: And if in the future Kyma will become also available for non C/4 products. Ideally, it would be good to see both options - Kyma and SCP available for all SAP products.

        Additionally, is there still any future for the CX Cockpit (it seems it becomes redundant)? And, lastly, any hope to get the Extension Factory and System Landscape in the trial SCP?


        • Hello Mariusz Cisek,

          Yes, both is what we are working towards: giving you the choice to pick any runtime (ABAP runtime, (CF) Application runtime, Serverless runtime, Kyma runtime) to extend any solution (C/4, S/4, SuccessFactors). The foundation is now there with Kyma runtime being available and the System Landscape as one central point to register applications.

          I can't say anything on the plans of the SAP C/4HANA Cockpit besides the blog post of Viktor Kehayov.

          Lastly, we are planning to make Kyma runtime as well available on SCP Trial and on the Partner Test, Demo & Development offerings. We just need some time to be ready.

          Best regards,

  • Hi Marco,

    Good to know this and thanks for detailed steps.

    In the future, can we create Kyma runtime in the C/4HANA cockpit or the only way to create Kyma runtime from the SCP global account?

    Could you please help me with this.





  • Please focus on the word "catalog".

    The service catalog is the first place we all go when something new appears in SAP CP.

    It's just an entry pointing to the documentation.

    FYI, "Serverless Runtime" is in the catalog.

  • Hi Marco,

    I am in bit confusion, as Kyma supports both synchronous and asynchronous calls(correct me if I am wrong), can we use Kyma instead of CPI?.



  • Hi Marco Dorn,


    very nice addition to the portfolio indeed. Is there a way to get a trial? I'd like to dig into the specifics and compare AKS with Kyma especially from SCP developer perspective.




    • Hey Martin Pankraz,

      Thanks for your interest! We are working on adding Kyma runtime to the SCP Trial (and Partner Test, Demo & Development price list). But we still require a couple of months. We will for sure announce it here in the SAP Community.

      You can already look into Kyma via, but that's outside of the SAP Cloud Platform context.

      Best regards,

  • Hi Marco

    I was wondering how do we use a serverless function made in the Kyma Runtime (enabled with ApiRule) into an app (in the html5 app repo / managed approuter ) in the Application Runtime

    Function works fine in Postman but how do we use this in apps already made in app-runtime?

    Looks to me I need a service of some sort in my xs-app.json to connect to serverless functions

    Some info / help would be nice






    • Hello Bert Deterd,

      Have a look at this sample on in which Jamie Cawley shows how to call an API from within an UI5 app. The sample is part of a bigger set of steps, but in the end the context of this sample doesn't matter for your case.

      Let me know if this helps.

      Best regards,