3528524 - Frequently Asked Questions on C4C Tenant Refresh.

This KBA answers commonly asked questions about C4C Tenant Refresh.

SAP Cloud for Customer. 

1. What is a tenant refresh?
A. A tenant refresh is a special provisioning process by which one existing test tenant can be refreshed with data from another existing tenant.

   This process will only be applicable to standard customer test and production tenants.

   Different types of refresh:

   Empty system refresh: This method can be used to clear all the data in an existing tenant. The URL and tenant ID of tenant remains the same. However, there will not be any data in the tenant.

   Refresh from source system: In this method, the existing test tenant URL and tenant ID are kept and refreshed with data from another test or productive tenant. This means that we make a full copy of the source (another test or productive) tenant.

2. How can I request a tenant refresh?
A. You can request for a system refresh from tenant via Service Control Center work center.

   Go to Service Control Center  Systems and select the tenant for which refresh is to be requested.

   Click the Refresh System button.

   Refer KBA: 2751824 - How to Request Tenant Refresh for SAP Cloud for Customer for more details.

3. Is a tenant refresh request subject to restrictions?
A. Yes, a tenant refresh request is subject to restrictions. 

   - During a tenant refresh, the source tenant must be down for at least four hours. Note that over and above, four-hour downtime is subject to the size of the source tenant and will be estimated while the request is being created.

  - This activity can only be performed outside of the contractual maintenance window.

  - If an existing development tenant needs to be refreshed, save all existing PDI solutions. The refreshed tenant is the clone of the source tenant, which will have only the PDI solutions of the source tenant.

  - If customer-specific solutions (PDI solutions or one-time projects) are in place, this will only work when the versions of the existing customer-specific solutions in the source tenant and the tenant to be refreshed are the same.

  - If there are any open cases on the tenant to be refreshed, this process cannot be executed unless the cases are closed.

  - Customers who have closed their first implementation project (GO-LIVE) must ensure that all open change projects are closed in the source tenant. The tenant refresh process requires a clean-up of all change projects. The tenant refresh procedure does not support open change projects.

  - This service is available for standard SAP Cloud for Customer customers. SAP Digital CRM (D4C), C4C Edge, sales demo partner, partner development tenants, or test tenants are NOT supported.

  - Note that the refreshed tenant will be available normally 8-10 hours after release of the source tenant. The customer will be informed of completion via email.

  - All communication arrangements must be rebuilt for the refreshed tenant.

  - Certificate mapping should be redone on the refreshed test tenant. However, the refreshed production tenant will have the certificates already copied.

  - In total, a tenant refresh can take anywhere from 14 to 48 hours or even more, depending on the tenant data.

4. Are the existing cases carried over to the new tenant during a refresh?
A. No, the existing cases will not be carried over to the new tenant.

5. Will both the URL and tenant ID be retained in the new tenant?
A. Yes, the new tenant will have the same URL and tenant ID as the tenant being refreshed.

6. Is it necessary to rebuild integration scenarios with other systems?
A. Yes, all integrations to other systems must be rebuilt from the refreshed tenant.

7. Are PDI solutions copied from the test tenant when they are refreshed?
A. No, PDI solutions will not be copied from the test tenant when they are refreshed. It will be copied from the productive tenant when refreshed.

8. Can I request a refresh after go live?
A. Yes, if there are no open change projects and only a full copy refresh is required. The case must, however, be validated by the operations team once they receive it.

9. How much downtime is needed for a source productive tenant?
A. A minimum of four hours of downtime outside the contractual maintenance period (CMP) is needed from the source to copy the data. The actual downtime required may vary depending on the source tenant (productive) size. This will be communicated to you via case before the downtime.

10 When will the original test tenant that is being refreshed become inaccessible?
A. After the tenant refresh process begins, the tenant to be refreshed will be terminated. As a result, the original test tenant will be deleted.

11 Is there any limitation on tenant size?

A. Yes, 500GB is the limit. If, tenant size cross 500GB tenant refresh is not possible as part the Supplementary Terms and Conditions, we are not allowed to exceed the data size 500 GB for a test tenant.

Tenant Request from Service Control Center | SAP Blogs 

Tenant Refresh, PDI, Source, tenant, refresh , KBA , LOD-CRM-ADM , Administration UI , Problem

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions