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 sme.sap.com 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

Considerations

• 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.