A data variant represents a specific set of values used to execute an automated test process. These variants are managed within a Test Data Container (TDC). The structure of the TDC, meaning the specific data fields it contains, is defined by binding the UI control parameters from the test process steps to the TDC. Only after this binding is established does the TDC have the necessary field structure to hold data. Consequently, the logical and required next step is to populate this structure by creating one or more data variants with the actual test values.

A. After creating a test plan.

A test plan is created after the test process and its associated data (including variants) are fully prepared; the plan consumes the variants for execution.

B. After customizing a test process.

While customizing the process is a necessary preceding step, the direct prerequisite for defining a data variant is linking the process fields to a data container.

D. After providing consent for Post-Upgrade Testing.

This is an administrative step related to a specific testing scenario (PUT) and is not part of the core technical workflow for creating test data variants.

1. SAP Help Portal

SAP S/4HANA Cloud

"Test Your Processes": In the section "Test Data Container

" the documentation states: "You can create data variants for a test data container. A data variant is a set of data that is used for a test run... Before you can create a data variant

you must bind the parameters of a test process to the fields of the test data container." This explicitly confirms that binding precedes the creation of data variants.

2. SAP Help Portal

SAP S/4HANA Cloud

"Manage Your Test Processes": The procedural documentation for this application details the workflow. Step 6 of the procedure "Adapt a Test Process" is "Bind UI Control Parameters to a Test Data Container." The subsequent application to be used is the "Test Data Container" app

where variants are created

reinforcing the sequence.

3. SAP Best Practices Explorer

Scope Item 5SL (Automated Test Scripts): The process flow and setup instructions for this scope item describe the end-to-end process. The test script configuration steps show that after recording or copying a standard process

you create a Test Data Container

bind the process parameters to it

and then define the data variants within the container before assembling everything into a test plan.