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 Business ByDesign/ Cloud for Customer/ Cloud for Travel. 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.
•The customer is requesting a full copy (clone = 1:1 copy containing all data from Production to Test only)
•The customer is not LIVE yet and has not closed the first implementation project (Only possible before Go-Live).
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 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:-
Part 1: https://blogs.sap.com/2016/03/16/tenant-refresh-adaptation-support-for-integration/
Part 2: https://blogs.sap.com/2016/04/06/tenant-refresh-adaptation-support-for-integration-part-ii/
Part 3: https://blogs.sap.com/2016/04/10/tenant-refresh-adaptation-support-for-integration-part-iii/