LISTCUBE TEST CASE EXECUTION
When a ListCube 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 for the Test Plan and the Test Case. All ListCube Variants that were selected during the ListCube Test Case creation are automatically added into the ListCube Variant selection for the generated Test Run.
To execute the ListCube Test Case from the Test Management click on 
'Execute' and a screen for the ListCube Testing scenario is displayed. Please refer to 'Test Scenario EQS_LIST ' section for a more detailed description about each scenario step.
ListCube based testing
Currently there are two Test Scenarios using the ListCube functionality outputs. The ListCube testing uses the same functionality as found in the standard RSA1 'Display Data' to collect the data from the InfoProviders that is to be tested.
Recommendations:
- For one ListCube testing run a maximum of 5000 ListCube variants should be used.
- Highly recommended is to use the 'Use DB Aggregation' parameter when creating the ListCube Variants. When there are multiple lines with the same key in the image, then the performance is decreased during the comparison phase of this test scenario.
Test Scenario EQS_LIST (ListCube testing)
ListCube Testing Scenario
...
- Selecting ListCube Variants
- Generation of before image tasks
- Creation of before images
- Performing specific tasks in system outside KATE outside Datavard Validate (like conversion, migration, etc.)
- Generation of after image tasks
- Creation of after images
- Generation of comparison tasks
- Execution of comparison tasks
- Display of results
Select ListCube Variants
By double clicking on the first Test Step 'Select ListCube Variants' you can define which ListCube variants are to be used in the specified run for testing, or you can create new ListCube Variants, these consist of all the selected ListCube Variants for this Test Run.
Once you have the variants selected for the Test Run you need to save the selection by clicking on the 'Save' button (Ctrl + s) in main screen of the ListCube variants selection.
You can add ListCube Variants in the following ways:
Create New ListCube Variant- You can create new ListCube Variant by clicking on 'Create New ListCube Variant' button (Shift + F1). For more information please refer to Create new ListCube Variant chapter.
Add Existing ListCube Variant – You can display all of the existing ListCube variants in system and by clicking on the 'Add Existing ListCube Variant' button (SHIFT + F4), select one or more variants to be added into the Test Run.
Add ListCube Variants of Run - By clicking on the 'Add ListCube Variants of Run' button (SHIFT + F5) you can select another (distinct from current) run, and add all of the ListCube Variants used also into the current Test Run.
Copy ListCube Variants of Run - By clicking on the 'Copy ListCube Variants of Run' button (SHIFT + F8) you can choose another (distinct from current) run and copy the ListCube Variants into the current Test Run.
Generate ListCube Variants - By clicking on the 'Generate ListCube Variants' button (SHIFT + F2) a dialog for the ListCube variants generation is displayed. Please refer to 'Generate ListCube Variants' chapter.
Generate RFC ListCube Variants - By clicking on the generation ListCube variants with RFC destination is displayed. Please refer to 'Generate RFC ListCube Variants'.
Add Variants of Test Case - By clicking on the 'Add Variants of Test Case' button (SHIFT + F11) you can select from existing ListCube Test Cases and add the ListCube Variants in it also into the current Test Run.
Copy Variants of Test Case - By clicking on the 'Copy Variants of Test Case' button (SHIFT + F12) you can select from existing ListCube Test Cases, and add all of the ListCube Variants in it also into the current Test Run as copies.
Copy Variants - Please refer to 'Copy ListCube Variants' section for function details.
Generate tasks for before image
To generate the tasks, you can double click to execute, this will prepares the tasks for the following step 'Create before image'.
Create before images
By double clicking on this step, you first define number of background jobs to be used to create the before image for each of the specified ListCube variants. The Image creation of some ListCube variants can fail due to too many rows read. This is safety limit can be adjusted by changing the setting 'Max. ListCube image row size'. See Settings section for more details on how to change this setting.
If KATE If Datavard Validate setting 'ListCube additional aggreg.' is set to 'X' the image that is returned from an InfoProvider during the task execution is aggregated again. This functionality can be used for cases when a ListCube returns multiple rows with same key because of unsupported functions.
KATE is Datavard Validate is capable of handling numeric aggregation overflows. Automatic overflow handling is executed when 'ListCube additional aggreg.' 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 as if it was used. This feature enables you to create images for InfoProviders that normally would not be possible because of an overflow error on DB level. By turning off "DB Aggregation" in ListCube variants all aggregations will be performed in KATE in Datavard Validate and all non-overflowing key figures will be correctly saved in the image. "DB Aggregation" is always preferred for performance reasons and additional aggregation should be used for handling special situations.
| Warning |
|---|
| During additional aggregation the whole data image of returned rows from the InfoProvider needs to be loaded into memory at once. Memory restrictions of work processes can cause a fail of the task execution if these thresholds are reached during additional aggregation. |
Generate tasks for after image
To generate the tasks, you can double click to execute, this will prepares the tasks for the following step 'Create after image'.
Create after images
You define the number of background jobs to be used in the creation of the after image of the specified ListCube variants. The Image creation of some ListCube variants can fail due to too many rows read. This is safety limit can be adjusted by changing the setting 'Max. ListCube image row size'. See Settings section for more details on how to change this setting.
If KATE If Datavard Validate setting 'ListCube additional aggreg.' is set to 'X' the image that is returned from an InfoProvider during the task execution is aggregated again. This functionality can be used for cases when a ListCube returns multiple rows with same key because of unsupported functions.
KATE is Datavard Validate is capable of handling numeric aggregation overflows. Automatic overflow handling is executed when 'ListCube additional aggreg.' is set to 'X' and aggregation of results fails because of numeric overflow. In this case problematic overflowing key figure is set to 0 for all returned rows. In case of multiple overflowing key figures all of them will be set to 0. Overflow handling is always logged if it was used. This feature enables you to create images of InfoProviders that would be not possible because overflow error on DB level. By turning off "DB Aggregation" in ListCube variants all aggregation will be done in KATE in Datavard Validate and all not overflowing key figures will be correctly saved in image. "DB Aggregation" is always preferred for performance reasons and additional aggregation should be used for handling special situations.
...
| Warning |
|---|
| It is not possible to ignore characteristic columns as those are used as unique keys for record matching during comparison. |
Compare before and after images
You define the number of jobs/ background jobs to be used for tasks execution each of the tasks compares the before image data with the after image data for one ListCube Variant, please refer to the (Comparison logic) chapter.
Display results
You can view the outputs and their comparison results for the ListCube Variants executions, please refer to ('Results overview') chapter.
ListCube with mapping
Test Scenario EQS_SLO_L (
...
ListCube with mapping testing)
The SLO ListCube with mapping scenario shares many of the same steps as with the standard ListCube scenario, the difference is with the additional functions to create converted images based on the defined mappings.
SLO ListCube with mapping - Testing Scenario
SLO ListCube with mapping testing contains following steps:
- Selecting ListCube Variants
- Generation of before image tasks
- Creation of before images
- Defining mapping
- Generation of convert tasks
- Creation of converted images
- Performing specific tasks in system outside KATE outside Datavard Validate (conversion, etc.)
- Generation of after image tasks
- Creation of after images
- Generation of comparison tasks
- Execution of comparisons tasks
- Display of results
Select ListCube Variants
By double clicking on the first Test Step 'Select ListCube Variants' you can define which ListCube variants are to be used in the specified run for testing, or you can create new ListCube Variants, these consist of all the selected ListCube Variants for this Test Run.
Once you have the variants selected for the Test Run you need to save the selection by clicking on the 'Save' button (Ctrl + s) in main screen of the ListCube variants selection.
You can add ListCube Variants in the following ways:
Create New ListCube Variant- you can create new ListCube Variant by clicking on 'Create New ListCube Variant' button (Shift + F1). For more information please refer to 7.2.1 Create new ListCube Variant chapter.
Add Existing ListCube Variant – You can display all of the existing ListCube variants in system and by clicking on the 'Add Existing ListCube Variant' button (SHIFT + F4), select one or more variants to be added into the Test Run.
Add ListCube Variants of Run - By clicking on the 'Add ListCube Variants of Run' button (SHIFT + F5) you can select another (distinct from current) run, and add all of the ListCube Variants used also into the current Test Run.
Copy ListCube Variants of Run - By clicking on the 'Copy ListCube Variants of Run' button (SHIFT + F8) you can select another (distinct from current) run, and add all of the ListCube Variants used also into the current Test Run as copies.
Generate ListCube Variants - By clicking on the 'Generate ListCube Variants' button (SHIFT + F2) a dialog for the ListCube variants generation is displayed. Please refer to 7.2.2 ('Generate ListCube Variants') chapter.
Generate RFC ListCube Variants - By clicking on the generation ListCube variants with RFC destination is displayed. Please refer to 7.2.3 ('Generate RFC ListCube Variants')
Add Variants of Test Case - By clicking on the 'Add Variants of Test Case' button (SHIFT + F11) you can select from existing ListCube Test Cases and add the ListCube Variants into the current Test Run.
Copy Variants of Test Case - By clicking on the 'Copy Variants of Test Case' button (SHIFT + F12) you can select from existing ListCube Test Cases, and the ListCube Variants into the current Test Run as copies.
Copy Variants - Please refer to 7.2.11 ("Copy ListCube Variants") section for function details.
Generate tasks for before image
To generate the tasks, you can double click to execute, this will prepares the tasks for the following step 'Create before image'.
Create before images
By double clicking on this step, you first define number of background jobs to be used to create the before image for each of the specified ListCube variants. Image creation of some SLO ListCube with mapping variants can fail due to too many rows read. This is safety check while this behavior can be adjusted by changing setting 'Max. ListCube image row size'. See Settings section for more details how to change this setting.
Define mapping
By clicking on this step you can define mapping that should be used to convert before images and create converted images. Currently there are two types of mapping that user can use/create.
...
Creation of custom mapping is confirmed by pressing 'Enter' button. KATE SLO Datavard Validate ListCube with mapping scenario expects that the called form have this parameter:
...
The cs_line parameter holds actual line that should be changed based on your custom mapping logic.
| Warning |
|---|
| KATE Datavard Validate always tries to call the supplied Form once before the actual conversion of data, providing an empty line to check the correct specification of custom mapping. This first call should be ignored in your implementation of conversion Form. |
...
If this form exists in a custom mapping program, KATE Datavard Validate calls it once before actual conversion of data. This way you can make decisions based on the InfoProvider name that is converted and/or components of line to be converted.
KATE Datavard Validate standard mapping
By clicking on 
button screen is displayed (Figure 203) where you can define standard KATE standard Datavard Validate mapping without need of creation of custom mapping reports.
KATE Datavard Validate Standard mapping creation
...
You can define the separator character that is used in the CSV file and the number of lines that should be ignored in the file from the top. The Data structure in the CSV file has to adhere to rules that are described in help text available under 
'Information' button.
Generate tasks for conversion
To generate the tasks, you can double click to execute, this will prepares the tasks for the following step 'Convert Before Images'.
Converted before images
By double clicking on this step, you first define number of background jobs to be used to create the converted image for each of the specified ListCube variant before images.
Generate tasks for after image
To generate the tasks, you can double click to execute, this will prepares the tasks for the following step 'Create after image'.
Create after images
You define the number of background jobs to be used in the creation of the after image of the specified ListCube variants. Image creation of some SLO ListCube with mapping variants can fail due to too many rows read. This is safety check while this behavior can be adjusted by changing setting 'Max. ListCube image row size'. See Settings section for more details how to change this setting.
Generate tasks for comparison
By clicking on this task you can define which already created image you would like to compare with the after image. You can either select standard before image or converted image created by use of specified mapping.
...
After clicking on 
button comparison tasks are generated in next scenario step 'Compare Images'.
Display results
You can view the outputs and their comparison results for the ListCube Variants executions, please refer to ('Results overview') chapter.