SAP Knowledge Base Article - Public

3739049 - Prerequisites for Requesting the Test Data Refresh Service for the Parallel Line for Early Adopter Customers

Symptom

An early adopter customer plans to refresh test data from the test tenant (T.100) to the parallel test tenant (T.120) and requires clarification on the prerequisites before requesting the refresh.  

 

Environment

SAP S/4HANA Cloud Public Edition

Cause

The test data refresh service transfers application and transaction data from the test tenant (T.100) to the parallel test tenant (T.120). Both tenants must be on the same configuration level to ensure a consistent state after the refresh is performed. A test data refresh can only be requested after a branch or after a rebase of the parallel line. Certain prerequisites must be fulfilled.

Resolution

To ensure a successful test data refresh, two distinct readiness dimensions must be considered.  

The first dimension relates to parallel line readiness, which includes ensuring that all required configuration settings are correctly applied and that any necessary manual follow-up activities after a branch or rebase have been completed.  

The second dimension focuses on test data refresh readiness, covering the specific technical conditions and requirements needed to perform the test data refresh itself. 

Parallel Line Readiness:  

After Branch: 

After branching, the test tenant (T.100) and the parallel test tenant (T.120) should be almost identical in configuration and content. This is a prerequisite for requesting a test data refresh. However, some configuration activities are excluded from branching. You need to manually maintain these configuration activities in the main line and then in the parallel line (double maintenance) after branching. After double maintenance of these configuration activities in the parallel customizing tenant (D.120), transport them to the parallel test tenant (T.120). For more information, refer to Excluded Configuration Activities (Branch) and SAP Note 3680907. 

It is recommended to plan the branch close to the scheduled test data refresh window. To ensure configuration consistency between the main line and the parallel line during the test data refresh, no configuration or customizing activities should be performed in either the main line or the parallel line between the branching point and the test data refresh request.

After Rebase: 

A rebase of the tenant will lead to changes in the configuration and content in several areas. Complete the following actions before you request a test data refresh:  

  1. Ensure all staging entries are successfully activated. If any activation fails, choose one of the following options: 

    • Create a support case under the application component specified for the particular IMG activity to enable successful activation at a later time.  

    • Manually perform double maintenance to keep configuration data in sync with the main line. 

           For more information, refer to Process the Failed or Not Processed Activities. 

       2. Double maintain any configuration activities that are excluded from rebase. For more information, see SAP Note 3680907. 

       3. Finalize the staging by setting the overall status to Staging Completed. 

       4. Import all transports from the customizing tenant (D.100) and the parallel customizing tenant (D.120) to the test tenant (T.100) and the parallel test tenant (T.120), respectively.

Test Data Refresh Readiness 

  • Execute the test data refresh readiness check after you have fulfilled all the prerequisites to understand if your landscape is ready for the test data refresh. You will find details on: Check Your System Readiness 

  • If the readiness check shows findings, fix them according to the details provided in the readiness check output file. 

  • The test data refresh readiness check will not check if your parallel line readiness is fulfilled.   

  • Additional information about test data refresh service including out of scope items and considerations are listed in SAP Note 3070606. 

 

 

See Also

Excluded Configuration Activities (Branch) and SAP Note 3680907. 

Test Data Refresh - Help  

SAP S/4HANA Cloud Public Edition, Test Data Refresh (TDR) - Information Note 3070606 

Keywords

Test Data Refresh, Parallel Line, TDR, refresh T.120 , KBA , CA-DT-TDR , SAP S/4HANA, Test data refresh: Content , Problem

Product

SAP S/4HANA Cloud Public Edition all versions