Skip to Content
Author's profile photo Ginger Gatling

SAP Cloud for Customer Tenant Landscapes: Tenant Landscape Recommendations with SDK

This blog series discusses C4C tenants from the aspect of how many you need and examples of recommended tenant landscapes.    The blog series includes the following topics:

1. Determine how many tenants you need

2. Tenant landscape use case examples

3. Considerations for tenant copies

4. Tenant landscape recommendations with SDK – this blog

5. Deployment recommendations with SDK

Tenant Landscape Recommendations with SDK

Early in the project you should determine if you will use the SDK or not.   Keep in mind, if you are using the Adaptation tools to add custom fields, if those fields require business logic, the SDK is required.   For example, if you add a field called “bonus plan” and you need to calculate the field value, or base the field value based on a comparison of other fields, then you need the SDK.

When you need the SDK, the recommended landscape is described below.   As mentioned in the previous blogs, an additional tenant is needed.  For SDK, you need a tenant designated as the Development tenant.  Only development work is done on this tenant.


One of the test tenants is designated TEST, the other DEV.   In the TEST tenant you do the main configuration and all testing.    From this tenant the development tenant is created. The DEV tenant is done by requested a solution profile with full copy.    The DEV tenant has only developers an only has basic scoping and whatever is required for the development.  Unit tests are performed in the DEV tenant.  The solution is then deployed to TEST where it is scoped and tested.   This is an iterative process until the solution is accepted and is ready to move to production.     Once deployed to production, the SDK solution is scoped, configured, with cut over to production.

The next blog goes into the details of the deployment process with the SDK.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Thanks, Ginger good one.

      Author's profile photo Anne-Birgitte Kofoed
      Anne-Birgitte Kofoed

      Hi Ginger,

      We have a scenario at a client where the following tenant environment exists:

      Company A: Test Tenant A -> Production tenant A

      Company B: Test Tenant B -> Not yet in production

      The test and production tenants are integrated to one SAP ERP backend system (QA + PROD)

      SDK development has been done directly in test tenant A and contains both development for company A & B. Due to this fact we cannot get a change project from the production tenant A to the test tenant A as the test tenant contains a partner solution that is only relevant for company B.

      This is not a sustainable solution so we are thinking about letting the test tenant A be the future development tenant for both companies, and then request a new test tenant as a copy of the production A tenant.


      It is possible to designate a current TEST tenant as the future DEV tenant?

      If yes, do we have to issue an incident to SAP about this request?


      Kind regards,

      Anne Kofoed