Skip to Content

SAP Cloud for Customer Tenant Landscapes: Determine how many tenants you need

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 – this blog

2. Tenant landscape use case examples

3. Considerations for tenant copies

4. Tenant landscape recommendations with SDK

5. Deployment recommendations with SDK

Before we get started, there is a full landscape deck available at business center site (primarily for partners).  This blog provides perspective from our consulting team on tenant management.

Determine how many tenants you need

When a production subscription of SAP Cloud for Customer is purchased, the subscription includes a production tenant and a test tenant.  Each tenant has a unique URL. Additional test tenants may be purchased as well.


The following summarizes what is delivered with C4C tenants.

Productive Tenant subscription for C4C

  • Provides a single productive tenant
  • Provides a test tenant to support the initial implementation and post go-live application lifecycle management using change projects.  This tenant is often referred to as the ‘sandbox’ tenant.
  • If you require a fresh tenant, you need to decommission the older one first

Test Tenants

  • You can purchase additional test tenants
  • SAP recommends buying an additional test tenant for every additional tenant you want to have available in your permanent landscape


  • If planning integration or SDK work, you should purchase a minimum of one (1) additional test tenant, often referred to as the permanent test tenant.

Questions to ask when deciding how many tenants you need

  1. Do you know what tenants you purchased?   Default for each production subscription includes production and 1 test tenant.  Any other tenants must be purchased. 
  2. Do have you custom development? Purchase an additional test tenant.
  3. Do you have integration?  Purchase an additional test tenant.
  4. Do you have a phased project with functional changes going on while other end user training and testing is going on?  A second test tenant may be required (4 tenant landscape).
  5. Is there anything specific in business-as-usual to consider additional tenants (for example, complex on-premise landscape where tenants should always connected to DEV/PRE-PROD, etc)?  Additional test tenants may be required. This is an exception scenario and a specific tenant design should be created with the customer and the SAP account team or partner account team so that the financial impact of the required tenants is understood.
  6. Are there organizational reasons for separate tenants for different lines of business with separate projects that require more tenants?  Additional test tenants may be required. This is an exception scenario and a specific tenant design should be created with the customer and the SAP account team or partner account team so that the financial impact of the required tenants is understood.

In the next blog we will discuss example tenant landscapes.

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

    Thanks for this amazing guide.

    We have ECC SDK integration using HCI with an additional C4C Test tenant (3 total).

    Could you please also specify how many HCI tenants we should prepare?

    Again, we have 3 C4C tenants connected to 3 ECC clients (DEV, TST, PRD)

    Thanks in advance,


    1. What is the process if we want to request for a quality tenant (already development test tenant and production tenant present)? i.e. which system's copy should it be?... test or production?
    2. what will be the implications, if we have a solution profile copy and we have SDK extension fields?
    3. Should a full copy be done with an active patch solution available in development test tenant?
    4. If a full copy of development test tenant is done to the quality tenant with an active ongoing patch solution, can the quality tenant be reset back? i.e. will it be possible to delete the patch solution or both solutions from the quality tenant?
  • Hi Ginger,
    could You please add some Information to question No.3?
    WHY shall I purchase an additional test tenant if I plan to integrate C4C with my ERP? (Doesn´t everybody need any kind of Integration, I can´t immagine a solitaire CRM System ...)
    BR Hartwig 

  • Hi Ginger,

    Thank you so much for the blog,

    The same question  I have that is asked by Hartwig Gfreiner why should one has purchase something separately, the existing test system cannot it serve the integration/SDK development purpose? 

    also why the new system is called permanent test system? 

    could you please throw some light on this.

  • Hello Ginger,

    Can I you more information about Sandbox Tenant, you mention?

    • Is it come it with production tenant? That make it free?
    • After "the initial implementation and post go-live application lifecycle management using change projects", can we still able to use the Sandbox Tenant?

    Longing for your answer,

    Thank you very much.


    • Hello Phat Huynh Tan

      Basically with one subscription, you will be getting one production( this is the live system with real data) and  one test Tenant ( you do testing here )  and these will be with you as long as you are subscribed, even after your implementations are completed 

      Any thing extra is billed

      To me Sandbox tenant is just a terminology which is used for test tenant.

      So, if you take 2 test tenants( call it Development/sand box  tenant and the other  as QA tenant) and want to have one production tenant , then the second test tenant is billed.

       Your Account Manager / Sales Advisor can provide more details on this further.

      • Hi Prasanth,

        Years ago the initial test tenant was temporary and that was the need for the additional test tenant for integrated or SDK projects (at least that is my understanding). If the initial test tenant is permanent, then why shouldn't it be used for integrated or SDK projects? What are the limitations or potential issues that come with only using the initial test tenant and the associated production when the project isn't complex but involves integration? Most AE's rely on partners to provide these inputs not the other way around.



  • Dear Soraya,

    Actually there is no separate category called initial system or sandbox system.

    All these are the test systems which are provided to customers. Its upto customers how they need to use  and define in their  landscape for development  based on requirement.

    From PDI side, we always recommend to use the permanent source test/ development system so that the Addon deployments are taken care of. As customer ID plays a vital role for you custom specific solitions.

    You can also use your initial test system for development there should not be any issues. Its based on your licensing and contract for that test system.

    I would recommend you to please discuss once with your CEEs or account manager on the same.

    You can refer below reference documents about landscape for customization.

    Please refer help documentation - SAP Cloud Application Studio - Landscape details.