...
When a DTP Case is added to the Test Plan, a new backend Test Run is automatically created and a Run ID is generated. The description holds technical name of the Test Plan and the Test Case. All the DTP Variants that were selected during creation of the DTP Test Case are automatically added to the DTP Variant selection for the generated Test Run.
You can execute DTP Test Case from Test Management by clicking on 
'Execute' button and the screen for standard Transformation Testing scenario is displayed.
...
Transformations are used during the execution of Data Transfer Process. This scenario is used to test the changes/updates of logic used in the transformations (lookupsLookups, rules, routines).
Test Scenario EQS_DTP (Transformations testing)
...
- Select DTP Variants
- Generate tasks for DTP generation
- Generate DTPs
- Generate tasks for before DTP load
- Load DTP for Before Image
- Generate tasks for before DTP images
- Create Before Images
- Performing Perform some specific task in the system outside Validate (like conversion, archiving, migration, etc.)
- Generate tasks for after DTP load
- Load DTP for After Image
- Generate tasks for after DTP images
- Create DTP for After Image
- Generate tasks for comparison
- Compare before and after images
- Display Results
- Display Lookup Results
- Generate tasks for clean up
- Clean up
- Clean up DTP
...
First in the list is a screen for defining the DTP variants to be tested during the run.
Figure 210: Selection of DTP variants
You can use standard Validate functionality to create a new DTP variant, add existing variants or add collection of variants from another Test Run.
After selecting the DTP variants, you should save the selection 'Save' button (Ctrl + sS) for current Test Run.
Create New DTP Variant - (Shift + F1) a dialog is displayed where you can specify the new variant. Please refer to 7.3.1 ('Create New DTP Variant').
Add existing DTP Variant – (Shift + F2) you can view a list of all the existing DTP Variants in the systems. Here you can select the variants to be added to the Test Run.
Add DTP Variants of Run - (Shift + F4) you can choose to add all variants used in another run to this Test Run.
Copy DTP Variants of Run - (Shift + F8) you can choose to add all variants used in another run to this Test Run as copies.
Add variants of Test Case - (Shift + F11) you can choose to add all variants used in existing Test Case to this Test Run.
Copy variants of Test Case - (Shift + F12) you can choose to add all variants used in existing Test Case to this Test Run as copies.
Copy Variants - Please refer to 7.1.147.3.7 ("Copy DTP Variants") section for function details.
Generate tasks for DTP generation - Generates the tasks for all DTP variants in the Test Run for the following step 'Generate DTPs'
Generate DTPs - This step groups the tasks to be executed into multiple background jobs. Each task generates one DTP based on the transformations specified in the DTP variant. However, if you are using a different after image, another variant is specified for the DTP variant as well. This DTP is generated for this variant settings and the same logic is applied.
Generated DTPs are created with these settings:
...
Extraction from – Active Table (Without Archive) – can be changed with Validate settings (see Settings chapter).
Note: You can always modify the generated DTP settings and filters through the standard RSA1 transaction and the generated DTPs are also visible there.
Note: DTPs generated by the Validate tool have their description generated in the same way as in standard DTPs; the only difference is an added prefix to the beginning. This Prefix can be changed in the Validate settings and can be up to 8 characters long. Please refer to Settings chapter.
...
Each task executes one DTP (If RFC Destination was specified for DTP Variant, the DTP load is executed on specified target system). If a different after image DTP Variant is specified then it's its generated DTP is used for loading.
In Validate the settings for the maximum waiting time can be specified (parameter 'DTP load wait time') for each task. If this time is exceeded (load takes too long), you are informed via the log and should check the status of load manually. It is necessary to wait for all loads to finish before you continue to the next scenario steps.
...
You can select InfoObjects that are ignored during comparison for the DTP Variants for this run, these . These ignored InfoObject columns are not visible when you 'Display Results'. Generation of task is executed by clicking on 'Create Tasks' (F8) button.
...
Double click to view results of testing is displayed , please refer to (Results overview) chapter for more information.
Display Lookup Results (Optional)
Here the lookup data testing results are displayed, when . When DVD Lookup Translator is installed in the system and configured to provide Validate pre and post lookup data, Validate will also create images of the provided data and compares these with the 'Compare before and after images' step.
...
Each task looks into saved parameters of a variant and finds the before/after image load requests executed and then deletes these from the system.
The saved image data with comparison results are preserved after the clean up steps have finished their execution. If the DTP Test Case is defined with a RFC Destination, these requests are deleted in appropriate system. By executing this step prior to 'Create Before Images' step, you can separately clear test loads from systems after the before image is taken. The status can also be reset after the 'Create After Images' step and then rerun to clear also clear the after image loads.
Clean up DTP
The These tasks look into the saved parameters for one variant; searches for the generated DTPs and these are then deleted from the system. If the DTP Test Case is defined with a RFC Destination, the DTPs are deleted on appropriate system. The saved image data with comparison results are preserved after these steps finish their execution.