...
When a Table Test Case is added to the Test Plan a new backend Test Run is automatically created and a Run ID is generated. The description holds the technical name of the Test Plan and the Test Case. All Table Variants selected during creation of Table Test Case are automatically added into the Table Variant selection for the generated Test Run.
To execute a Table Test Case from Test Management, click on 
'Execute' afterwards and the standard Table Testing scenario is displayed. Please refer to 8.5.1 ('Test Scenario EQS_TABLE (Table testing)') section for a more detailed description about each scenario step.
...
Table based testing uses data directly from the database tables. Based on specifications set by the user specification set, the table columns are read from the database table and are used to create before and after image. These images are then compared.
Recommendations:
...
Table testing contains following steps:
- Selecting of Table Variants
- Generation Generating of before image tasks
- Creation Creating of before images
- Performing of specific tasks in the system outside Validate (like conversion, migration, etc.)
- Generation Generating of after image tasks
- Creation Creating of after images
- Generation Generating of comparison tasks
- Execution Executing of comparison tasks
- Display Displaying of results
Select Table Variants
By double clicking on the first Test Step 'Select Table Variants', you can define which Table variants are to be used in this Test Run for testing, or you can simply create new Table variants.
Once you have the variants selected for the Test Run, you need to save the selection by clicking on the 'Save' button (Ctrl + sS) in the main screen of the Table variants selection.
You can add Table Variants in the following ways:
Create New Table Variant – You can create new Table Variant by clicking on 'Create New Table Variant' button (Shift + F1). For more information please refer to Create new Table Variant chapter.
Add Existing Table Variant – You can display all of the existing Table variants in the system by clicking on the 'Add Existing Table Variant' button (Shift + F2). You can then select one or more variants to be added into this Test Run.
Add Table Variants of Run – By clicking on the 'Add Table Variants of Run' button (Shift + F4), you can select another (distinct from current) run , and add all of the Table Variants of selected run into the current Test Run.
Copy Table Variants of Run – By clicking on the 'Copy Table Variants of Run' button (Shift + F8), you can select another (distinct from current) run and add all of the Table Variants of selected run into the current Test Run as copies.
Add Variants of Test CaseCase – By clicking on the 'Add Variants of Test Case' button (Shift + F11), you can select an existing Test Case , and add the all Table Variants of selected Test Case into the current Test Run.
Copy Variants of Test CaseCase – By clicking on the 'Copy Variants of Test Case' button (Shift + F12), you can select an existing Test Case , and add all of the Table Variants of selected Test Case into the current Test Run as copies.
Copy Variants - Please – Please refer to 'Copy Table Variants' section for function details.
Generate tasks for before image
To generate the tasks, you can double click the Test Step 'Generate tasks for before image' to execute it. This will prepare the all tasks for the following step 'Create before images'.
...
By double clicking on this step, you first define the number of background jobs to be used to create the before image for each of the specified Table variants. The Image creation of some Table variants can fail due to too many rows read. This is a safety limit and can be adjusted by changing the setting 'Max. Table image row size'. See Settings section for more details on how to change this setting.
Validate is capable of handling numeric aggregation overflows. Automatic overflow handling is executed when 'Table own aggregation' setting is set to 'X' and aggregation of results fails because of numeric overflow. In cases of a problematic overflowing, the key figure is set to 0 for all returned rows. And in cases of multiple overflowing key figures these will be set to 0. Overflow handling is always logged. This feature enables you to create images for Tables that normally would not wouldn't be possible because of an overflow error on DB level. DB aggregation is always preferred for performance reasons and own aggregation should be used for handling special situations.
Generate tasks for after image
To generate the tasks, you can double click the Test Step 'Generate tasks for the after image' to execute it. This will prepare the all tasks for the following step 'Create after images'.
...
To generate the tasks, you can double click the Test Step 'Generate tasks for comparison' to execute it. This will prepare the all tasks for the following step 'Compare before and after images'.
...
You define the number of background jobs to be used for tasks execution. Each of the tasks compares the before image data with the after image data for one Table Variant, please refer to the (Comparison logic) chapter.
Display results
You can view the outputs and their comparison results for the Table Variants executions, please refer to ('Results overview') chapter.