...
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 ' /wiki/spaces/KATE/pages/16886436section for a more detailed description about each scenario step.
...
- Selecting ListCube Variants
- Generation of before image tasks
- Creation of before images
- Performing specific tasks in system outside KATE 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
...
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 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 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 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.
...
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 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 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 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.
...
- 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 Validate (conversion, etc.)
- Generation of after image tasks
- Creation of after images
- Generation of comparison tasks
- Execution of comparisons tasks
- Display of results
...
Creation of custom mapping is confirmed by pressing 'Enter' button. KATE 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 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 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 Validate standard mapping
By clicking on 
button screen is displayed (Figure 203) where you can define standard KATE Validate mapping without need of creation of custom mapping reports.
KATE Validate Standard mapping creation
...