Skip to Content
Product Information
Author's profile photo Shashank Singor

Tenant Refresh for SAP Cloud For Customer,SAP Cloud for Sales & SAP Cloud for Service


This process will provide you a flexibility where you can request for a tenant refresh of an existing test tenant. This service is available for Cloud for Customer/ Cloud for Travel/ Cloud for Sales/Cloud for Service . D4C/ Edge customers cannot request this service.

The tenant refresh process contains of the following steps:

•Copy of the source tenant (which requires a downtime about at least 4 hours)

•Switch of the tenant identities (switch of tenant ID and tenant URL)

•Invalidation/Decommissioning of original test tenant

That means that we do a full copy of a source tenant, this could be a productive or an existing test tenant and switch the identities (tenant ID and URL) of the test tenant which should refreshed.

In the end, the original test tenant will be decommissioned by this process.

The result of this process is to retain the URL and tenant ID of an existing test tenant and to refresh it with data of source tenant (mainly your productive tenant but it could also be your existing test tenant).

For example, a tenant refresh can be used for integration tests of a SAP Cloud for Customer test tenant which is already integrated with an ERP system and testing requires new data of the productive tenant.


Only a full copy (clone = 1:1 copy containing all data from Production to Test OR Test to Test)


Please note that when customer-specific solutions (PDI solutions/one-off projects) are in place, this will only work when version of existing customer-specific solutions are the same in source tenant and tenant to be refreshed.

How to Request a Tenant Refresh via an Incident

To request a tenant refresh, please create an incident out of your Cloud tenant.

Provide the following information in the incident to request tenant refresh:

  • Customer name.
  • Customer number/ID (Business Partner Number).
  • Tenant ID or URL of tenant which is source of the copy.
  • Tenant ID or URL of test tenant which should be refreshed.
  • Requested downtime of source tenant: Start time, start date.

(During the tenant refresh creation, the source tenant needs to be stopped for 4 hours.)

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

  • Confirmation about short downtime of test tenant to be refreshed and new tenant during identity switch.
  • Confirmation that you can agree with deletion of original test tenant (test tenant which should be refreshed)
  • Requester Contact Person It is important that you provide with the name and e-mail address of the   person who should be informed when we face issues during this process.

The tenant refresh is generally provided within 1 business day of the customer making the request. The customer will be informed of completion via update on the incident.

Tenant refresh process is only available for the Customer tenants. Reference or Partner Development Tenants are NOT supported.

NOTE: After the source tenant downtime, it will take another 8-10 hours for completing the further steps and getting ready the test tenant.

NOTE: For the On-premise customers, Post refresh activity in order to sync the integration between On-premise & C4C system, Kindly refer to the below three blogs:-

Adaptation Part 1

Adaptation Part 2

Adaptation Part 3

Shashank Singor

Assigned Tags

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

      Hi Shashank,

      Our system is live since 2016 and In Last 2 years we have couple of instances that the refresh process was aborted by SAP due to reasons that the 4 hours downtime was not enough for SAP to do the copy.

      We give SAP the requested production downtime by restricting our business users to use the system but finally our intended business purpose is not achieved.

      For refresh, I think there should be proper planning in place, SAP can do some pre-requisite checks to understand how much time will be needed to copy the source tenant and it can be communicated to customers for better planning of downtime and business disruption.

      Recent SAP Incident 521391/2019 regarding the same issue we faced .



      Author's profile photo Shashank Singor
      Shashank Singor
      Blog Post Author

      Hi Vignesh,

      Downtime depends upon the size of the tenant, However when a customer requests for a refresh, pre-checks are being done. If more downtime is required then, it is informed to the customer and based on the customer permission, SAP will execute the process in the given downtime only.

      Hope this helps you.

      Shashank Singor

      Author's profile photo Vignesh Dharmaraj
      Vignesh Dharmaraj

      Thanks Shashank, Let me wait for the support feedback in the Incident then.

      I have one more query on the below restriction part you mentioned in the blog.

      "Please note that when customer-specific solutions (PDI solutions/one-off projects) are in place, this will only work when version of existing customer-specific solutions are the same in source tenant and tenant to be refreshed."

      Basically in the refresh process a new tenant is created as a copy of Production and the test tenant identity is switched. Why we need to keep the Patch version of the source and target as same to start the refresh?