Skip to Content
Product Information

Good to know- How to know if I can download the App Cloud Application Studio (SDK).

Hello everyone,

Today we have the 1911 version in the development environment of C4C. Therefore, probably if you have a project with development in Cloud Application Studio (known as CAS or PDI) you will not be able to access. How to know if I can download the app in the Launchpad? Look at this article and learning how.

  1. What license you need to download the application on the Launchpad?

In the following table, you will see the version required for Sales and Services Cloud Edition.

Check the link from SAP with all Feature Availability Based on Product Licenses: https://help.sap.com/viewer/5d3ae4aa1f174b2cb6ec625c93ef8884/1911/en-US/20086074005a4f9e81e830ea0933b823.html

Key Feature Standard Edition Professional Edition Enterprise Edition
SAP Cloud Applications Studio (SDK) No Yes Yes

 

2. What S-User is available for download the app on the Launchpad?

In this case, you must ask the customer, which S- User is available. However, if you have one S- User you can try this.

In the Launchpad and go to the Product and fill SAP CLOUD APP STUDIO 1911 and if the section Download is empty you not have the access. Check the pictures below for more details.

 

Conclusion:

This will be necessary for all SAP C4C updates on the development tenant. These updates are planned every three months and, for this reason, you must update the SDK four times a year.

I hope this is useful for you. 🙂

Best regard!

DRT

 

3 Comments
You must be Logged on to comment or reply to a post.
  • Hi,

    I have an S-User, but our SAP partner is telling us that we need to purchase another Test environment in order to use the product. Is there a license fee for CAS, and does it need a separate environment? (Using ByDesign)

     

    Cheers.

    • Hi Rick Beecroft ,

      Firstly, we use SDK (CAS) to extend the SAP Cloud for Sales and Service (fka C4C) or SAP By Design SaaS solutions – provided the correct license like Professional or Enterprise as mentioned on the blog.

      If you have correct license, then next step is to understand why you need to do some CAS/SDK developments, for example a fully custom business process would need a custom development in which case use of CAS/SDK is necessary . For many minor extensions, Key User Tools & custom Object builder(COB) option would suffice( keeping in mind, you can’t write the business logic script with COB)

      SAP best practice says if any project has integration or developments in scope then additional tenant is required. So what your System Integrator is telling is right. Mainly because SDK development are tightly coupled to the tenant. Without an additional tenant you have only 1 test tenant in which simultaneously configurations & testing is going on. If you also add development to this tenant then while developers are working, the environment would be unstable to carry out other configurations& testing.

      Also SDK lifecycle is Original solution & then ongoing changes via Patch solution after the first solution is deployed. If you have only 1 tenant to do everything, your first solution will then be deployed first time, directly in the production at go-live readiness. Thus practically you have done development & UAT of your solution in the same tenant when you have only 1 test tenant. Once your solution in deployed on Production tenant, if there is any issue or say new requirement or changes over the time , you would need to make changes in your SDK solution. For this, you will have to create a Patch solution. The First time a patch solution is created, it is technically a copy of your initial solution BUT has a different namespace behind the scene. To make changes, you need to first enable the patch solution and the moment you do it, all the test data vanishes ( it’s not deleted as such but remained save in DB under the first solution namespace & with Patch solution activation, the fields remain empty as they are under new namespace). This problem is only limited to Test tenant and not the production tenant ( thus production data will not vanish when you deploy the patch to production) & this data vanish problem in Test occurs only one time when you create the first patch. There are these and such implications and therefore it is recommended to have an additional tenant for developments ( which is like your dev tenant) and you can then properly handle your development cycle through Dev-QA-Prod landscape.

       

      Thanks,

      Suchita