(KATE-146) Variant Editor

Owned by Lenka Mackovicova
Jul 18, 2017

Variant editor provides a central location where you can manage all the backend-testing variants.
For each logical type of backend testing the screen tabs lets you see all existing test variants for the corresponding test scenario. The title of the screen as well as buttons for the available functions in toolbar change as you navigate through the different tabs. 



Figure 120: Variant Editor Tabs


The variant editor provides following different tabs for the following variants:

  1. Query Variants Editor Tab
  2. ListCube Variants Editor Tab
  3. Transformations Variants Editor Tab
  4. Drill Down Variants Editor Tab
  5. Table Variants Editor Tab
  6. Report Variants Editor Tab

Query Variants Editor Tab

Query Variant Editor provides an overview for all Query Variants used in Backend Testing. You can manage all Query Variants from this screen. 



Figure 121: Query Variant Editor


The Query Variant Editor provides following functionalities:

  • Create new Query Variant
  • Create new Bookmark Variant
  • Generate Variants from DVD Extended Query Statistics
  • Create Variants of Web Templates
  • Generate Web Template Bookmark Variants
  • Delete Query/Bookmark Variants
  • Copy Query/Bookmark Variants
  • Transport Query/Bookmark Variants
  • Edit Query/Bookmark Variant
  • Mass Edit Variants
  • Create After Images as copies
  • Compare Settings
  • Copy Settings
  • Copy Query Variants
  • Clean up Query Variants

Create new Query Variant

The screen for creating new Query Variant is accessible by clicking on the 'Create new Query Variant' button (Shift + F1).



Figure 122: Creating new Query Variant


In this screen you can define:

  1. RFC Destination – RFC destination of the Query Variant. When the RFC destination is specified using 'F4' help, this will display the query name values from the specified destination system. RFC with 'F4' help is only available if the dialog RFC connection (does not need to be same as filled one) is available in the system in the specified RFC destination.
  2. Query name (required) – the technical name of a query. 'F4' help is available for this field.
  3. Query Variant Description – lets you add a description for the new Query Variant.
  4. Set query variables (button) –you can specify the filtering values (if any) for a query. For RFC Query Variants there is the possibility to specify the filtering values that are available only if the dialog RFC connection (does not need to be same as filled one) is available in the system to the specified RFC destination and KATE is also installed on the RFC destination system.


Figure 123: Query Filters


  1. After image variant – Query/Bookmark Variant ID enables you to compare the outputs for different queries or for the same query on a different system. This can be executed instead of the variant during the creation of an after image.

To save, click on 'Continue' (Enter) and the Query Variant is saved. Various checks are done to ensure the correctness of variant definition before the Variant is saved.
 If different Query/Bookmark Variants are specified for the after image creation then the following rules apply, in order for outputs to be compared. Both of the compared query/bookmark variants must have exactly same structure of columns/rows to allow KATE to compare them. If the structure of the variants differs, then the correctness of comparison cannot be guaranteed. 

Create new Bookmark Variant


Figure 124: Create new Bookmark Variant


Screen for creating a new Bookmark Variant is accessible by clicking on the 'Create New Bookmark Variant' button (Shift + F2). In this screen you can define:

  1. RFC Destination – RFC Destination of a system on which the bookmarked query is run on. KATE must be installed on the RFC destination system in order to successfully create a RFC enabled Bookmark Variants.
  2. Bookmark ID (required) – identification for the query bookmark. Bookmarks that were also created with data can also be used here. In such a case, the bookmarked data is not being read from the bookmark; only the query is executed using the bookmark structure information.
  3. Bookmark Variant Description –to specify the description for a new Query Variant.
  4. After Image Variant – Query/Bookmark Variant ID that is executed during the creation of after image. This allows you to compare outputs for different queries or even the same queries on different systems.

The Query Variant is saved when clicking on 'Continue' button (Enter); before saving is complete various checks are performed to ensure the correctness of variant definition.

Generate Query Variants from HeatMap Statistics

This functionality is available, only if the HeatMap Query Statistics is already installed on the system. After clicking on the button 'Generate Query Variants from HM' (Shift + F6), the screen displayed is where you can define which InfoProvider and Query selection are to be searched for in statistics. 



Figure 125: Specification of filter for queries search


After a filter is specified (optional) you can click on the 'Continue' (Enter) button. The next screen displays the information about queries that are present in HeatMap Statistics and the number of times the query was executed in the system. 
You can generate the Query Variants from these statistics by selecting queries and specifying the number of variants to be created for each of the selected queries. This number only specifies the maximum number of variants that are to be generated. If there are not enough distinct (in terms of used filters) query executions in the statistics, then fewer Query Variants are generated. Variants are then generated after clicking on 'Continue' button (Enter). 



Figure 126: Generation of Query Variants

Create Variants of Web Templates

You can also create Query Variants for all of the queries used in specified Web Template, to do this you can click on 'Create Based on Web Template' button (Shift + F8). 



Figure 127: Selection of Web Template


In this screen you can define the Web Template ID and after clicking on 'Continue' button (Enter) the Web Template is searched for all the used queries. These queries are presented in a table afterwards (Figure 128) and this table you can choose the queries to be generated for the Query Variants by using the checkboxes. 



Figure 128: Queries of web template


For each selected query you are presented with the standard 'Create New Query Variant' screen where you can define or change the prefilled variant values.

Generate Web Template Bookmark Variants

You can create Query Variants based on a specified Web Template Bookmarks, click on 'Gen. Based on Web Template Bookmark' button (Shift + F12). The Screen for Web Template Bookmark ID selection is then displayed (Figure 129). 



Figure 129: Selection of Web Template Bookmarks for Query Variant generation


Afterwards, click on 'Continue' button (Enter); each Web Template Bookmark selected is searched for all the used queries. For each query found a new Query Variant is created. All the Query Variants filters are filled with the corresponding filtering values from Web Template Bookmark they were found in. 
 If a change was done in Web Template regarding the drill down in query results (i.e. change in displayed columns/rows) this change is also reflected in the output of query in backend testing.

Delete Query/Bookmark Variants

To delete an existing Query/Bookmark Variants, select the rows and then clicking on the delete button in the ALV toolbar. 
 Any Query/Bookmark Variants that are still in use in the Backend Testing will be locked; therefore it is necessary to delete the Query Variants from the in the run before deleting them permanently from the Query Variant Editor.

Copy Query/Bookmark Variants

To create a copy of the existing Query/Bookmark Variants select the rows with the variants you want to copy and then click on the 'Copy Query Variants' button in toolbar of the table, for each selected Query/Bookmark Variant a copy is then created.

Transport Query/Bookmark Variants

It is possible to add specified Query Variants to a transport so they can be transferred to another system (with KATE installed). To specify which Query/Bookmark Variants should be transported you need to select these from a list as shown on Figure 130. Options for filtering and sorting in ALV table can be used to select specified Query Variants more easily. 



Figure 130: Selecting Query Variants to be transported


After selecting the desired Query Variants click on the  'Transport Query Variants' button, a dialog is display (Figure 131), where you can select a request and confirm the transport for the selected Query Variants.

 

Figure 131: Export Query Variants Request Dialog


It is important to note that Query Variants carry information about the query names and filtering values, but not the query structures themselves; therefore these should be imported only to a system where KATE is installed and where the same queries with the same structure exist.

Edit Query/Bookmark Variant

You can edit the existing Query/Bookmark variants by double clicking on them in the table, only Variants that are not used in other Test Runs can be edited. If Query/Bookmark Variant is already used in another Test Run it's details can be only reviewed but not changed. 
When variant details are displayed you can check where this variant is used, by pressing the 'Where Used'  button; a table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 



Figure 132 Where Used List for Variant


By clicking on  'Copy Settings to After Image' button you can copy specified settings of this variant into its after image variant if it is specified.

Mass Edit Variants

You can edit more Query/Bookmark variants at once, and is done by selecting the required variants from the list and clicking on the 'Mass Edit Variants'  button. Dialog for mass edit of variants is displayed. 



Figure 133 Mass Edit Of Query Variants


You can define new values for the before and after image RFC destination. Changing of these values is done after clicking on 'Continue' (Enter) button. By marking the 'Edit' checkbox only the values, which you specify to be changed, will be replaced in selected variants. If Query/Bookmark variant has a different After Image specified the After Image RFC destination will be replaced in that variant otherwise there will not cause any change. Only variants that are not yet used in test runs can be changed by mass edit.

Create After Images as Copies

Select multiple variants and create after image variants from them. To access this functionality you need to right click on the selected variants and choose 'Create After Images as copies'. A Dialog is displayed where you can define RFC destination that will be applied to all generated after image variants. All other settings are copied from source variants. 



Figure 134 Create After Image Variants as copies

Compare Settings

You can compare the chosen settings for variant with its defined after image variant (if there is one). Select the requested variants and choose 'Compare Settings' option from the context menu. 


Figure 135 Compare settings of before and after image variant


It is possible to check the settings and you can choose what should be compared between variants. After you confirm the selection check is done and the table with compare status messages is displayed.

Copy Settings

You can copy settings of variant to its defined after image variant. After the selection of variants is done you can choose 'Copy Settings' context menu option. A dialog is displayed where you can define which settings should be copied and the source variant for after image variant (if there is any). 



Figure 136 Copy settings of variant to its after image variant


After you confirm the selection, the specified settings are then copied and a message table is displayed with information about updated variants.

Copy Query Variants

You can create copies of Query variants by selecting on multiple variants in the selection table and clicking on  'Copy Query Variants' toolbar button. For each selected variant a new variant is created with exactly the same settings as the source variant. If a copied source variant has a different after image variant specified a copy of this would also be created. The copied after image variant is then assigned to copied source variant as its after image variant. 



Figure 137 Copy Variants

Cleanup Query Variants

You can delete all unused Query variants by clicking on  'Cleanup Query Variants' button. The First screen displays a preselection of filters of the variants where you can restrict which variants should be checked for deletion. After you confirm this screen check is performed to find all unused variants. A variant is unused if it is not assigned to any Test Case or Test Run. If a variant is used in another variant as an after image variant and that variant is used in any Test Case or Test Run it is evaluated as used on not presented for deletion. 



Figure 138 Query Variant Cleanup Preselection


All variants evaluated as not used are then displayed in the dialog window. When you confirm the selection in this window the variants are deleted from the system.

ListCube Variants Editor Tab

ListCube Variant Editor serves as an overview for all the ListCube Variants used in Backend Testing (Standard ListCube scenario and SLO ListCube scenario). You can manage all ListCube Variants in this screen. 



Figure 139: ListCube Variant Editor


The ListCube Variant Editor provides following functionalities:

  • Create new ListCube Variant
  • Generate ListCube Variants
  • Generate RFC ListCube Variants
  • Delete ListCube Variants
  • Transport ListCube Variants
  • Edit ListCube Variants
  • Mass Edit Variants
  • Create After Images as copies
  • Compare Settings
  • Copy Settings
  • Copy ListCube Variants

As from KATE version 1.4.2 a new column called 'Data Access' was added into the ListCube Variants overview table. There are three possible values that this column can have:

  • 'O' – ListCube Variant will read only the Online data
  • 'ON' – ListCube Variant will read the Online and NLS data
  • 'N' – ListCube Variant will only read the NLS data

Create new ListCube Variant

The screen for creating a new ListCube variant is displayed after clicking on the 'Create New ListCube Variant' button (Shift + F4). 



Figure 140: Create new ListCube Variant screen


In this screen you can specify the following variant detail:

  1. RFC Destination – RFC Destination of the system where the InfoProvider is to be read. When RFC destination is specified, the F4 help displays values from specified RFC destination in the InfoProvider field.
  2. Variant Description – description of the new ListCube Variant.
  3. InfoProvider (required) – technical name of the InfoProvider to be read. F4 help is available for this field.
  4. Max. Rows. – Max. Rows. – Maximum number of rows to be read from the InfoProvider. If this field is set to 0 or left empty, then all possible rows will be selected. 0 value should be always used as ListCube functionality does not guarantee the order of rows returned.
  5. Data Access Type:
    1. Read Online Data – option to read only online data via the ListCube.
    2. Read Online + NLS Data – option to read the NLS Data via the ListCube. This option is ignored for releases below 7.3 (i.e. only online data will be read for such releases).
    3. Read Only NLS Data – option to read only data from NLS. InfoProvider that will be read will need to have an active DAP created. This option is not release dependent.
    4. Read Online / Read NLS Data – when this option is selected two variants are generated with the only difference being in the data access type. One variant is generated with Read Online Data option selected while second one is created with Read Only NLS Data option selected.
  6. Use DB Aggregation – option to use DB Aggregation for the ListCube execution. It is always recommended to use DB aggregation so the output of ListCube is aggregated on the Database level. This reduces the chance of multiple rows with the same key and image memory footprint. Turning this setting off should only be done in special cases when the KATE additional aggregation is used.
  7. Display number of Hits – option for the column 'ROWCOUNT' to be added to the output of ListCube.
  8. Use mat. Aggregates – option to use materialized aggregates during the ListCube execution. If selected the defined aggregates should be used for the InfoCube when preparing the output list. If you choose to use materialized aggregates, the query is not executed directly in the fact table, instead aggregate tables are used and performance is improved. However if aggregates are not recalculated there may be differences in the data returned.
  9. Characteristics in Output – selection of the defined characteristics to be selected from the InfoProvider (from KATE version 1.4.2 also navigational attributes are supported). All the key figures are always selected together with the unit characteristics*.
  10. Set Filters (button) – used for defining the filter values to be displayed and you can define the filtering values to be used during ListCube execution.


Figure 141: ListCube filters selection


  1. After Image Variant – ID of the ListCube variant that are used for the after image creation. Allowing you to compare the output of different InfoProviders or InfoProviders from different systems.
  2. Referenced Time point – click on the 'Advanced Settings', an option to set up the reference time point is displayed. The referenced time point is the date and time setting that is used in the following way: When a ListCube Variant has a referenced time point set up, a check is done before each execution. This check searches for the load request ID from all of the requests in the system that has an update time equal to or lower than the specified referenced time point. This request ID is then used in ListCube execution as filter on 0REQUID field where condition is set to – Select all the data with 0REQUID equal to or lower to the found request ID. You can make a snapshot of only part of this data available in InfoProvider. Please see the important notes below for any restrictions that apply to this functionality.

 Important: the update request times that you see in the RSA1 transaction are transformed based on your defined Time Zone setting. Prior to the execution of the Before/After image creation (before search for global request is done) the user defined time is transformed from its local time to the UTC time. 
It is also important that the referenced time point specified by the user is the same Time Zone setting as the user who will execute the test in KATE. In addition, when searching for a referenced time point on the remote server you need to also check that the user (or RFC user if used) has same time zone setting as the user who will execute the tests in KATE. 

  1. Exclude old data – mark this checkbox if you want ListCube variant to read data newer than the specified referenced time point instead of the older ones.
  2. Excluded Key Figures – All Key Figures specified here will be not read from the InfoProvider during the image creation. If excluded, the key figure does use a unit that is not used by any of the non-excluded key figures this unit will also not be read from the InfoProvider.
  3. Excluded Units – You can define which units that are not to be read from InfoProvider during the image creation. For each excluded unit all key figures that are dependent on this unit will be excluded automatically from the InfoProvider read.

To save the ListCube Variant click 'Continue' (Enter), before saving various checks are done to ensure the correctness of variant definition.
*Important Notes:

  • All the key figures and appropriate unit/currency characteristics are always returned in the ListCube output. There is an exception for Key Figures with the aggregation function NOP. When the 'Use DB Aggregation' setting is active, Key Figures of this type are not returned in the output.
  • All characteristics of the InfoProvider (from KATE version 1.4.2 navigational attributes are also supported) are checked for compliance with the specified characteristic selection. If yes then they are returned in ListCube output.
  • Reference Time Point setting usable only for InfoCubes and MultiProviders. For other InfoProviders this setting is ignored, as it is not possible to use the filtering on 0REQUID field in the ListCube. For InfoCubes this setting influences only the read data from the Fact table. Please note that in MultiProvider Cubes, this setting will be affect the InfoCubes below but not the DSOs as their data have 0REQUID set to value '0'.

 If a different after image variant is specified for the ListCube variant some restrictions are then applied in terms of comparing results of the before/after image. The used ListCube variants must have exactly the same number, type, and name of characteristics and units of the InfoObjects selected for output. When so, KATE is able to compare the before/after image, if some Key Figures are missing in one of the variants in comparison to another variant then these columns are ignored during the comparison.

Generate ListCube Variants

The Screen for generation of ListCube variants is displayed after clicking on 'Generate ListCube variants' button (Shift + F5). 



Figure 142: Generate ListCube Variants screen


In this screen you can define:

  1. InfoProviders – The selection of InfoProviders for which ListCube variants are to be generated.
  2. Characteristics in Output – The selection of characteristic InfoObjects that are to be selected in ListCube output (from KATE version 1.4.2 navigational attributes are also supported).
  3. Filter Objects – The selection of characteristic InfoObjects on which you want to define filters (from KATE version 1.4.2 navigational attributes are also supported).
  4. Set Filters (button) –You can define the filtering values of the characteristics selected in the 'Filter objects' select option. KATE does not support more than a 100 different characteristics for filtering.


Figure 143: Filter values for generation of ListCube Variants


  1. Maximum Rows – You can define maximum number of rows to be selected in all generated ListCube variants.
  2. Data Access Type:
    1. Read Online Data – option to read only the online data in the generated ListCube variants.
    2. Read Online + NLS Data – option to read the NLS Data in generated ListCube variants. This option does not apply for releases below 7.3 (i.e. only online data will be read for such releases).
    3. Read Only NLS Data – option to read only the data from NLS. InfoProviders that are to be read need to have an active DAP created.
    4. Read Online / Read NLS Data – when this option is selected two variants are generated with the only difference being in the data access type. One variant is generated with Read Online Data option selected while second one is created with Read Only NLS Data option selected.
  3. Use DB aggregation – To choose if the DB aggregation should be used in generated ListCube variants.
  4. Display Number of Hits – The option to add column 'ROWCOUNT' to the output of generated ListCube Variants.
  5. Use mat. aggregates – To choose if mat. aggregates are to be used in the generated ListCube variants.
  6. Referenced Time point – After clicking on the 'Advanced Settings' button an option for the referenced time point specification is displayed. When this is filled, a reference time point is set for all of the generated ListCube Variants.
  7. Excluded Key Figures – Key figures that should be excluded in the generated ListCube variants.
  8. Excluded Units – You can define units that are to be excluded in all generated ListCube variants.

The Generation of ListCube variants are executed by clicking on the 'Continue' (Enter) button. For each InfoProvider that matches the InfoProvider Selection a ListCube Variant is generated (except if the 'Read Online / Read NLS Data' option is selected because two variants would then be generated for each InfoProvider). Using the selection of specified characteristics a cross-section of the InfoProvider characteristic is the used as range of characteristics for the InfoObject to be displayed in the ListCube output. This is also done the same way for filtering objects; with only those that can be applied for the specific InfoProvider are then added to the specific ListCube variant.

Generate RFC ListCube Variants

The screen for generation ListCube Variants is displayed after clicking on 'Generate RFC ListCube Variants' button (CTRL+F1). 



Figure 144: Generate RFC ListCube Variants screen



In this screen you can define:

  1. Characteristics in Output – The selection of characteristics for the InfoObjects that are to be selected in the ListCube Variants (from KATE version 1.4.2 navigational attributes are also supported).
  2. Filter Objects – The selection of characteristic InfoObjects on which you want to define the filters (from KATE version 1.4.2 navigational attributes are also supported).
  3. Description suffix – Is what will be added to the description of generated variants. Description of the variants are generated in the form 'Gen. Variant for $INFOPROVIDER_NAME'. If the description suffix is a specified string then '- $SUFFIX' is added to the description.
  4. Set Filters (button) –Defines the filtering values for the characteristics you have selected in the 'Filter objects' select option. KATE does support using more than 100 different characteristics for the filtering.


Figure 145: Filter values for generation of ListCube Variants


  1. Maximum Rows – You can define maximum number of rows to be selected in all of the generated ListCube variants.
  2. Data Access Type:
    1. Read Online Data – option to read only the online data in the generated ListCube variants.
    2. Read Online + NLS Data – option to read the NLS Data in the generated ListCube variants. This option is ignored for releases below 7.3 (i.e. only online data will be read for such releases).
    3. Read Only NLS Data – option to read only data from NLS. The InfoProvider that will be read needs to have an active DAP created.
    4. Read Online / Read NLS Data – when this option is selected two variants are generated for each of the selected InfoProvider with only difference being in the data access type. One variant is generated with the Read Online Data option selected while second one is created with the Read Only NLS Data option selected.
  3. Use DB aggregation – The option to select if DB aggregation should be used in the generated ListCube variants.
  4. Display Number of Hits – The option if the column 'ROWCOUNT' is to be added to output of generated ListCube Variants.
  5. Use mat. aggregates – To choose if the mat. aggregates are to be used in the generated ListCube variants.
  6. Excluded Key Figures – Key figures selection that defines, which key figures are not to be read from InfoProviders of generated ListCube variants.
  7. Excluded Units – Units selection that defines which units should be not read from InfoProviders of generated ListCube variants.
  8. Use different after image filter – If this option is set to 'X' and after image variants are generated for all of the before image variants. These variants will be created with a filter that is specified in the following option rather than filter specified at the top of the window.
  9. After Image Filter Objects – Selection of characteristics InfoObjects on which you want to use as a filter for the after image variants.
  10. InfoProviders Table – To specify if the InfoProviders are used in each of the generated variants. For each InfoProvider you can also specify the RFC Destination where this InfoProvider exists. When the After Image InfoProvider is specified, the second ListCube Variant is generated and used as an After Image Variant for the ListCube Variant of Before Image InfoProvider. If the After Image InfoProvider column is left empty then the same InfoProvider as the one specified in the Before Image is used for the After Image. It is also possible to display the columns for referenced Time Point, if these are specified then they are used during the generation of ListCube Variants.

From KATE version 1.4.2 it is possible to execute the generation of RFC ListCube variants in a background job. The Background job can be executed after you click on  'Generate Variants in Background' button. 
 When the variant generation is executed in the background, you can check the background job state through SM37 transaction. It is important to note that you should not try to adjust/ change the variants in the selection screen while the generating jobs are running. You can exit the selection screen but should not save the variants selection because variants that are generated in the background are automatically saved under the appropriate Test Case / Run.

Delete ListCube Variants

To delete the existing ListCube Variants, select the rows and click on the delete button in the ALV toolbar. 
 Any ListCube Variants still in use in the Backend Testing will be locked; therefore it is necessary to delete the ListCube Variants from the given runs before they can be deleted from the ListCube Variant Editor.

Transport ListCube Variants

You can add ListCube Variants to a transport so these can be transferred to another system (with KATE installed). Specify the ListCube Variants you want to transport by selecting them from the list (Figure 146). There are options for filtering and sorting in the ALV table and can be used to select specified ListCube Variants more easily. 



Figure 146: Selecting ListCube Variants to be transported


After selecting the desired ListCube Variants and clicking on the  'Transport ListCube Variants' button, a screen for choosing the transport request is displayed, once selected press confirm. 
It is important to note that ListCube Variants only carry the information about KATE related items and not the InfoProvider structures. These Variants should only be imported to a system where KATE is installed and the same InfoProviders with the same structure exist.

Edit ListCube Variant

To edit the existing ListCube variants, you double click on these in the table, only Variants that are not already used in a Test Run can be edited. If a ListCube Variant is already being used, their details can be only reviewed but not changed. 
When variant details are displayed you can check where this variant is used. By pressing the 'Where Used'  button, a table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 



Figure 147 Where Used List for Variant


By clicking on  'Copy Settings to After Image' button you can copy specified settings of this variant into its After image variant if it is specified.

Mass Edit Variants

You can edit more ListCube variants at once. Mass edit is performed by selecting the variants in list and clicking on 'Mass Edit Variants'  button, a dialog for mass editing the selected variants is displayed. 



Figure 148 Mass Edit Of ListCube Variants


You can define new values for the before, the after images, RFC destination, reference time point and exclude old data setting. Changing of these values is done after clicking on 'Continue' (Enter) button. Only the values which you specified to be changed, using the marking 'Edit' checkbox will be replaced in the selected variants. If a ListCube variant has a different After Image specified, then only the After Image parameters will be replaced in that variant, as nothing else needs to be updated with the changes. Note: Only variants that are not yet used in test runs can be changed by mass edit.

Create After Images as Copies

Select multiple variants and create after image variants for them. To access this functionality, right click on the selected variants and choose 'Create After Images as copies' . A Dialog is displayed where you can define RFC destination that will be applied to all generated after image variants. All other settings are copied from source variants.



Figure 149 Create After Image Variants as copies

Compare Settings

You can compare chosen settings for variant and its defined after image variant (if there is one). Select the requested variants and then choose 'Compare Settings' option from the context menu. 



Figure 150 Compare settings of before and after image variant


Settings that can be checked are displayed and you can choose what is to be compared between the variants. After you confirm the selection check is done and table with compare status messages is displayed.

Copy Settings

You can copy settings of variants to its' defined after image variant. After the selection of variants, choose 'Copy Settings' from the context menu. A dialog allows you to define which settings are to be copied from source variant to after image variant (if there is any). 



Figure 151 Copy settings of variant to its after image variant


After you confirm the selection, the specified settings are copied and message table is displayed with information about the updated variants.

Copy ListCube Variants

You can create copies of ListCube variants by selecting multiple variants in the selection table and clicking on  'Copy ListCube Variants' toolbar button. For each selected variant a new variant is created with exactly the same settings as the source variant. If a copied source variant has a different after image variant specified then a copy of this will also be created. The copied after image variant is then assigned to a copied source variant as an after image variant. 



Figure 152 Copy Variants

Cleanup ListCube Variants

You can delete all unused ListCube variants by clicking on  'Cleanup ListCube Variants' button. First screen with preselection filters of variants is displayed and you can restrict which variants should be checked for deletion. After you confirm this screen, a check is done to find all unused variants. A variant is classed as unused if it is not assigned to any Test Case or Test Run. If a variant is used in other variant as after image variant and that variant is used in any Test Case or Test Run it is evaluated as used on not presented for deletion. 



Figure 153 ListCube Variant Cleanup Preselection


All variants evaluated as not used are then displayed in dialog window. When you confirm the selection in this window variants are deleted from the system.

Transformation Variants Editor Tab

The Transformation Variant Editor provides an overview for all the DTP Variants used in the Backend Testing and these DTP Variants can be managed from this screen.

 

Figure 154: Transformation Variants Editor


The Transformation Variant Editor provides you with the following functionalities:

  1. Create New DTP Variant
  2. Delete DTP Variants
  3. Transport DTP Variants
  4. Edit DTP Variant
  5. Mass Edit Variant
  6. Create After Images as copies
  7. Copy DTP Variants

Create New DTP Variant

The Screen for creating new DTP Variant is displayed by clicking on the 'Create New DTP Variant' button (Shift + F7). 



Figure 155: Create new DTP Variant screen


In this screen you can define:

  1. RFC Destination – RFC destination that is to be used for the DTP Variant execution. When the RFC destination is specified, in the Transformation field the F4 help displays F4 help displays the values for the RFC destination.
  2. Variant Description – The description of the new DTP Variant.
  3. Transformation route (required) – The technical name of the transformations on top of which the DTP is to be generated. Transformation route consist of single transformation directly from source to target or several transformations forming the route from source to target that are connected through InfoSources. Transformations have to be set in order from source to target. Only transformations with the source of type InfoCube, DataSource, SPO and DSO is supported.Last or only transformationwith target type InfoCubes, DSOs and WODSs is supported in the current version of KATE .
  4. After image variant – If a different DTP variant is specified for the after image then this will be used as the source for the after image data. Therefore it's own DTP is generated and is also used for the load execution.

The DTP Variant is created after you click on the 'Continue' button (Enter).

Delete DTP Variants

Deleting the existing DTP Variants can be done easily by selecting the desired rows and clicking on the delete button in the ALV toolbar. 
 Any DTP Variants that are still in use in the Backend Testing will be locked; therefore it is first necessary to delete these DTP Variants from the given runs (or specific runs) before proceeding in deleting them permanently from the DTP Variant Editor.

Transport DTP Variants

It is possible to add the specified DTP Variants to a transport to be transferred to another system (with KATE installed). To specify which of the DTP Variants are to be transported you need to select from the list as shown on Figure 146. There are options for filtering and sorting in the ALV table that can be used to select the specified DTP Variants more easily. 



Figure 156: Selecting DTP Variants to be transported


After selecting the desired DTP Variants and clicking on the  'Transport DTP Variants' button, choose your transport request. You can select the request and confirm the transport for the selected DTP Variants. 
It is important to note that the DTP Variants only carry information about KATE related items, and not the transformation structures themselves so they should be imported only to system where KATE is installed and the same transformations with same structure exist.

Edit DTP Variant

You can edit the existing DTP variants by double clicking on them in the table view, only Variants that are not already in use in Test Runs can be edited. If a DTP Variant is already used in the Test Runs, then the details can only be reviewed but not changed. 
When variant details are displayed you can check where this variant is used. By pressing the 'Where Used'  button table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 



Figure 157 Where Used List for Variant

Mass Edit Variants

You can edit more DTP variants at once. Mass edit is performed by selecting the variants in list and clicking on 'Mass Edit Variants'  button, a dialog for mass editing the selected variants is displayed. 



Figure 158 Mass Edit Of DTP Variants


You can define new values for the before, the after image and the RFC destination. Change of values is done after clicking on 'Continue' (Enter) button. By marking the 'Edit' checkbox only the values, which you want to be changed will be replaced in selected variants. If the DTP variant has a different After Image specified, then only the After Image parameters will be replaced in that variant, as nothing else needs to be updated with the changes. Only variants that are not yet used in test runs can be changed by mass edit.

Create After Images as Copies

Select multiple variants and create after image variants for them. To access this functionality, right click on the selected variants and choose 'Create After Images as copies'. A Dialog is then displayed where you can define RFC destination that will be applied to all generated after image variants. All other settings are copied from source variants.



Figure 159 Create After Image Variants as copies

Copy DTP Variants

You can create copies of DTP variants by selecting on multiple variants in the selection table and then clicking on  'Copy DTP Variants' toolbar button. For each selected variant a new variant is created with exactly same settings as source variant. If the copied source variant has a different after image variant specified , the a copy of this will also be created. The copied after image variant is then assigned to copied source variant as its after image variant. 



Figure 160 Copy Variants

Cleanup DTP Variants

You can delete all unused DTP variants by clicking on  'Cleanup DTP Variants' button. The First screen with preselection filters of variants is displayed where you can restrict which variants should be marked for deletion. After you confirm this screen, a check is done to find the unused variants. A variant is unused if it is not assigned to any Test Case or Test Run. If a variant is used in other variant as after image variant and that variant is used in any Test Case or Test Run it is evaluated as used on not presented for deletion. 



Figure 161 DTP Variant Cleanup Preselection


All variants evaluated as not used are then displayed in dialog window. When you confirm the selection in this window variants are deleted from the system. 

Drill Down Variants Editor Tab

The Drill Down Variant Editor provides an overview of all Drill Down Variants used in Backend Testing and you can manage these Drill Down Variants from here.



Figure 162: Drill Down Variant Editor


The Drill Down Variant Editor provides following functionalities:

  • Create new Drill Down Variant
  • Generate Drill Down Variants
  • Delete Drill Down Variants
  • Transport Drill Down Variants
  • Edit Drill Down Variants
  • Mass Edit Variants
  • Copy DrillDown Variants

Create new Drill Down Variant

The Screen for creating a new Drill Down variant is displayed after clicking on 'Create New Drill Down Variant' button (SHIFT + F11).



Figure 163: Create new Drill Down Variant screen


In this screen you can specify following variant details:

  1. Description – Add a description of the new Drill Down Variant.
  2. RFC Destination A – Is the RFC Destination of the system where InfoProvider A is to be read. When the RFC destination is specified in the InfoProvider A field, the F4 help is available.
  3. InfoProvider A – The technical name for InfoProvider A. F4 help is available for this field.
  4. Data Access Type A:
    1. Read Online Data – option to read the only online data in the generated ListCube variant for InfoProvider A.
    2. Read Online + NLS Data – option to read both the online and the NLS Data in the generated ListCube variant for InfoProvider A. This option is ignored for releases below 7.3 (i.e. only the online data will be read for lower releases).
    3. Read Only NLS Data – option to read only the NLS data in the generated ListCube variant for InfoProvider A. InfoProviders that are to be read needs to have an active DAP created.
  5. Read NLS Data – Gives you the option to use NLS Data in the ListCube for InfoProvider A.
  6. Use mat. aggregates – To choose if mat. aggregates should be used in the generated ListCube variant for InfoProvider A.
  7. RFC Destination B – Is the RFC Destination the system where InfoProvider B is to be read. When the RFC destination is specified in the InfoProvider B field, the F4 help is available.
  8. InfoProvider B – The technical name of InfoProvider B. F4 help is available for this field.
  9. Data Access Type B:
    1. Read Online Data – option to only read the online data in the generated ListCube variant for InfoProvider B.
    2. Read Online + NLS Data – option to read the NLS Data in the generated ListCube variant for InfoProvider B. This option is ignored for releases below 7.3 (i.e. only online data will be read for such releases).
    3. Read Only NLS Data – option to read only the NLS data for the generated ListCube variant for InfoProvider B. InfoProviders that are to be read needs to have an active DAP created.
  10. Use mat. aggregates – To choose if mat.aggregates are to be used in the generated ListCube variant for InfoProvider B.
  11. Drill Down Characteristics – is the list of characteristics that are going to be used during Drill Down execution for the two specified InfoProviders. F4 help for this select option, but only displays characteristics that exist in both of the InfoProviders. The Order of characteristics is an important select option because it needs to define the order of how they are to be added to the ListCube execution in case errors are found.
  12. No BWA Characteristics – You can define the selection of characteristics (as subset of Drill Down Characteristics) because when added to the ListCube read during Drill Down execution the use of BWA is excluded.
  13. Display Number of Hits – Gives the option to choose if the column 'ROWCOUNT' is to be added to output of ListCube for both of the InfoProviders.
  14. InfoProvider A Referenced Time point – Is a date and time setting that is used in following way: When a Drill Down Variant references a time point for InfoProvider A, a check is performed before the execution for a load request ID from all of the requests in system that has an update time equal or lower than the specified referenced time point. This request ID is then used in the ListCube read during the Drill Down execution as a filter on the 0REQUID field. Please refer to ('Create new ListCube Variant') section for more information regarding the Reference Time point behavior.
  15. InfoProvider B Referenced Time point – Performs the same check but for InfoProvider B. Please refer to ('Create new ListCube Variant') section for more information.
  16. Exclude InfoProvider A old data – changes the behavior of A InfoProvider referenced time point setting, so only the records newer then specified time point would be read.
  17. Exclude InfoProvider B old data – changes the behavior of B InfoProvider referenced time point setting, so only records newer then specified time point would be read.
  18. Excluded Key Figures – Key figures that will be excluded from selection of both InfoProviders. If the excluded key figure uses a unit and no other non-excluded key figure depends on the unit it is also excluded from selection.
  19. Excluded Units – Units that will be excluded from selection of both InfoProviders. For all excluded units the appropriate key figures are as well excluded.

To save the Drill Down Variant click the 'Continue' button (Enter), various checks are done to ensure the correctness of variant definition before saving
*Important Notes:

  • If any 'No BWA Characteristic' is specified, then the ListCube read in the Drill Down scenario stops to use the BWA immediately after any of these characteristics are added to output during the test cycle.

 Requirement for Drill Down testing InfoProviders A and B is that both should contain all of the specified Drill Down Characteristics and use the same number of unit/currency InfoObjects. If the Number of Key Figure differs, the missing Key Figure columns are ignored during comparison.

Generate Drill Down Variants

The Screen for the generation of Drill Down variants is displayed after clicking on 'Generate Drill Down Variants' (SHIFT + F9). 



Figure 164: Generate Drill Down Variants screen


From this screen you can define:

  1. Drill Down Characteristics – Is the list of characteristics that are used during the Drill Down execution for the two specified InfoProviders. F4 help for this but only displays the characteristics that exist in both InfoProviders because only these can be used. The order of characteristics as a select option is important because it needs to define the order of how they are added to the ListCube execution in case errors are found.
  2. No BWA Characteristics – Defines the selection of characteristics (as subset of Drill Down Characteristics) because when these are added to ListCube read during Drill Down execution the use of BWA is excluded.
  3. Description suffix – Is the suffix to be added in the description of the generated variants. The Description of variants that are generated in the form 'Gen. variant: $INFOPROVIDER_A_NAME <> $INFOPROVIDER_B_NAME'. If a description suffix is specified then the string '- $SUFFIX' is added to the description.
  4. Data Access Type A:
    1. Read Online Data – option to only read the online data in all the generated ListCube variants for InfoProviders A.
    2. Read Online + NLS Data – option to read the NLS Data in all of the generated ListCube variants for InfoProviders A. This option is ignored for releases below 7.3 (i.e. only the online data will be read in lower releases).
    3. Read Only NLS Data – option to only read the NLS data in all of the generated ListCube variants for InfoProviders A. InfoProviders are to be read needs to have an active DAP created.
  5. Data Access Type B:
    1. Read Online Data – option to only read the online data in all of the generated ListCube variants for InfoProviders B.
    2. Read Online + NLS Data – option to read the online and NLS Data in in all of the generated ListCube variants for InfoProviders B. This option is ignored for releases below 7.3 (i.e. only online data will be read for lower releases).
    3. Read Only NLS Data – option to only read the NLS data in all of the generated ListCube variants for InfoProviders B. InfoProviders that are to be read needs to have an active DAP created. This option is not release dependent as previous one.
  6. Use mat. aggregates A – To choose if the mat. aggregates should be used in all the generated ListCube variants for A InfoProviders.
  7. Use mat. aggregates B – To choose if the mat. aggregates should be used in all the generated ListCube variants for B InfoProviders.
  8. Excluded Key Figures – Defines the selection of key figures that will be excluded for all generated variants.
  9. Excluded Units – Defines the selection of units that will be excluded for all generated variants.
  10. InfoProviders Selection – In this table, you can specify the pairs of A and B InfoProviders together with their RFC Destinations. For each pair a new Drill Down Variant is generated with all of the settings specified in the header of screen. It is possible to display the Referenced Time point columns for InfoProviders by changing ALV Layout. These Referenced Time point settings are then used also in generated Drill Down Variants.

Generation of Drill Down variants is executed by clicking on 'Continue' (Enter) button.

Delete Drill Down Variants

To delete existing Drill Down Variants, select the rows and clicking on the delete button in the ALV table toolbar.
 Any Drill Down Variants that are still use in the Backend Testing will be locked and are not deleted. It is necessary to delete these first from the test runs and then proceed in deletion in the Drill Down Variant Editor.

Transport Drill Down Variants

It is possible to select and add the Drill Down Variants to a transport to be transferred into another system (with KATE installed). To specify which Drill Down Variants should be transported you need to select them (Figure 165). There are options for filtering and sorting in the ALV table to select the ListCube Variants more easily. 



Figure 165: Selecting Drill Down Variants to be transported


After selecting the Drill Down Variants and clicking the on  'Transport Drill Down Variants' button, choose the transport request and confirm the transport of selected Drill Down Variants. 
It is important to note that the Drill Down Variants carry information only related to KATE and not about InfoProvider structures themselves so these should only be imported to systems where KATE is installed and where the same InfoProviders with the same structure exist.

Edit Drill Down Variant

You can only edit existing Drill Down variants, if they are not yet used in Test Runs. If a Drill Down Variant is already used in the Test Runs, then its details can be reviewed but not changed.

Mass Edit Variants

You can edit more Drill Down variants at once. Mass edit is performed by selecting the variants in list and clicking on 'Mass Edit Variants'  button, a dialog for mass editing the selected variants is displayed. 



Figure 166 Mass Edit Of Drill Down Variants


You can define new values for the before image, the after image, the RFC destination, referenced time point and exclude old data setting. By marking the 'Edit' checkbox only the values, which you want to be changed will be replaced in selected variants. Only variants that are not yet used in test runs can be changed by mass edit.

Copy DrillDown Variants

You can create copies of DrillDown variants by selecting on multiple variants in the selection table and then clicking on  'Copy DrillDown Variants' toolbar button. For each of the selected variant a new variant is created with exactly same settings as source variant. 



Figure 167 Copy Variants

Cleanup DrillDown Variants

You can delete all unused DrillDown variants by clicking on  'Cleanup DrillDown Variants' button. The First screen with preselection filters of variants is displayed and here you can restrict which variants should be checked for deletion. After you confirm this screen, a check is done to find all unused variants. A variant is classed unused if it is not assigned to any Test Case or Test Run. 



Figure 168 DrillDown Variant Cleanup Preselection


All variants evaluated as not used are then displayed in dialog window. When you confirm the selection in this window variants are deleted from the system.

Table Variants Editor Tab

The Table Variant Editor provides an overview for all the Table Variants used in the Backend Testing. You can manage all these Table Variants in this screen. 



Figure 169 Table Variant Editor


The Table Variant Editor provides following functionalities:

  • Create new Table Variant
  • Generate RFC Table Variants
  • Delete Table Variants
  • Transport Table Variants
  • Edit Table Variants
  • Mass Edit Variants
  • Create After Images as copies
  • Compare Settings
  • Copy Settings
  • Copy Table Variants

Creating new Table Variant

The screen for creating a new Table variant is displayed after clicking on the 'Create New Table Variant' button (Ctrl + F2).



Figure 170 Create new Table Variant screen


In this screen you can specify the following variant detail:

  1. RFC Destination – RFC Destination of the system where the Database Table is to be read. When the RFC destination is specified, the F4 help display values from the specified RFC destination in the Table Name field.
  2. Variant Description – description of the new Table Variant.
  3. Characteristics Fields – selection of the table fields to be used as characteristics. These fields will be used as the Key fields in the comparison of table data.
  4. Key Figure Fields – selection of table fields to be used as key figures. These fields will be used as the Data fields in comparison of table data. Only the number like fields can be selected here. Number like fields are those with data type equal to:
    1. DEC
    2. CURR
    3. QUAN
    4. FTLP
    5. INT1
    6. INT2
    7. INT4
  5. Select Number of Rows – is an option for the column 'ROWCOUNT' to be added into the output of Table.
  6. Set Filters (button) – used for defining the filter values to be used during DB table read. Maximum of 100 distinct filtering fields can used.


Figure 171 Table filter selection


It is possible to swap between the descriptions of table filtering fields and their technical name by clicking on  'Display Description/Technical Name' button.

  1. After Image Variant – ID of the Table variant that is used for the after image creation. This allows you to compare the output of different Tables or Tables from different systems.

To save the Table variant click the 'Continue' (Enter) button, before saving various checks are done to ensure the correctness of variant definition.
*Important Notes:

  • When no table fields are selected as characteristics and no table fields are selected as key figures then the ROWCOUNT field is automatically added as only output field of table read.
  • In the current version, KATE can hold values with the maximum length of 74 characters. Values that are longer are truncated.

 If a different after image variant is specified for Table variant some restrictions are then applied in terms of comparing results of the before/after image. The used Table variants must have the same number, type and order of table fields selected as characteristics. When so, KATE can compare the before/after image. If some table fields that are selected as Key Figures are missing in one of variants in comparison to another variant, then these columns are not considered during the comparison.

Generate RFC Table Variants

The screen for generation Table Variants is displayed after clicking on 'Generate RFC Table Variants' button (CTRL+F5). 



Figure 172 Generate RFC Table Variants screen 


In this screen, you can define:

  1. Characteristics Fields – selection of the table fields to be used as characteristics. These fields will be used as the Key fields in the comparison of table data.
  2. Key Figure Fields – selection of table fields to be used as key figures. These fields will be used as the Data fields in comparison of table data. Only the number like fields can be selected here.
  3. Filter Fields – The selection of Characteristics Fields on which you want to define the filters (from KATE version 1.4.2 navigational attributes are also supported).
  4. Set Filters (button) – for defining the filter values to be used during DB table read. Maximum of 100 distinct filtering fields can used. 



Figure 173 Filter values for generation of Table Variants
It is possible to swap between the descriptions of table filtering fields and their data element by clicking on  'Display Description/Technical Name' button.

  1. Description suffix – Is what will be added to the description of generated variants. Description of the variants are generated in the form 'Gen. Variant for $TABLE_NAME'. If the description suffix is a specified string, then '- $SUFFIX' is added to the description.
  2. Select Number of Rows – is an option for the column 'ROWCOUNT' to be added into the output of Table.
  3. Tables Selection – In this table, you can specify the pairs of tables for the Before and After Image together with their RFC Destinations. For each pair a new Table Variant is generated that will contain all the settings specified in the header of screen. It is possible to use patterns with asterisk sign (star) in table name and define more table variants at once.

It is possible to execute the generation of RFC Table variants in a background job. The Background job can be executed after you click on  'Generate Variants in Background' button. 
 When the variant generation is executed in the background, you can check the background job state through the SM37 transaction. It is important to note that you should not try to adjust/change the variants in the selection screen while the generating jobs is running. You can exit the selection screen but should not save the variants selection because variants that are generated in the background are automatically saved under the appropriate Test Case / Run. 

Delete Table Variants

To delete the existing Table Variants, select the rows and click on the delete button in the ALV toolbar. 
 Any Table Variants that are still in use in the Backend Testing will be locked; therefore it is necessary to delete the Table Variants from the given runs before they can be deleted from the Table Variant Editor.

Transport Table Variants

You can add Table Variants to a transport so these can be transferred to another system (with KATE installed). To specify the Table Variants you want to transport, select them from the list (Figure 174). There are options for filtering and sorting in the ALV table and this can be used to select specified Table Variants more easily. 



Figure 174 Selecting Table Variants to be transported


After selecting the desired Table Variants and clicking on the  'Transport Table Variants' button, a screen for choosing the transport request is displayed, once selected press confirm. 
It is important to note that Table Variants only carry the information about KATE related items and not the Table structures. These Variants should only be imported to a system where KATE is installed and the same Database Tables with the same structure exist.

Edit Table Variant

To edit existing Table variants, you double click on these in the table, only Variants that are not already used in Test Run can be edited. If a Table Variant is already being used, their details can be only reviews but not changed. 
When variant details are displayed you can check where this variant is used. By pressing the 'Where Used'  button table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 



Figure 175 Where Used List for Variant


By clicking on  'Copy Settings to After Image' button you can copy specified settings of this variant into its After image variant - if specified.

Mass Edit Variants

You can edit more Table variants at once. Mass edit is done by selecting the required variants in the list and clicking on 'Mass Edit Variants'  button, a Dialog for mass edit of variants is then displayed. 



Figure 176 Mass Edit Of Table Variants


Here you can define new values for the before, the after image and the RFC destination. Changes to these values are done after clicking on 'Continue' (Enter) button. By marking the 'Edit' checkbox only the values, which you want to be changed will be replaced in selected variants. Only variants that are not yet used in test runs can be changed by mass edit.

Create After Images as Copies

Select multiple variants and create after image variants for them. To access this functionality, right click on the selected variants and choose 'Create After Images as copies'. A dialog is then displayed where you can define the RFC destination that will be applied to all of the generated after image variants. All other settings are also copied from source variants.



Figure 177 Create After Image Variants as copies

Compare Settings

You can compare the chosen settings for variants and its defined after image variant (if there is one). Select the requested variants and then choosing 'Compare Settings' option from the context menu.

 

Figure 178 Compare settings of before and after image variant


A dialog with possible settings is displayed select what is to be compared between variants. After you confirm the selection check is done and table with compare status messages is displayed.

Copy Settings

You can copy settings of variant to its defined after image variant. After selection of variants is done you can choose 'Copy Settings' in the context menu. Dialog is then displayed where you can define which settings should be copied from source variant to the after image variant (if there is any). 



Figure 179 Copy settings of variant to its after image variant


After you confirm the selection, specified settings are copied and message table is displayed with the information about updated variants.

Copy Table Variants

You can create copies of DrillDown variants by selecting multiple variants in the selection table and then clicking on  'Copy Table Variants' toolbar button. For each selected variant a new variant is created with exactly the same settings as the source variant. If a copied source variant has a different after image variant specified also a copy of that will be created. The copied after image variant is then assigned to the copied source variant as its after image variant. 



Figure 180 Copy Variants

Cleanup Table Variants

You can delete all unused Table variants by clicking on  'Cleanup Table Variants' button. The First screen with preselection filters of variants is displayed and you can restrict which variants should be checked for deletion. After you confirm this screen, a check is done to find the unused variants. A variant is classed as unused if it is not assigned to any Test Case or Test Run. If a variant is used in another variant as an after image variant or the variant is used in any Test Case or Test Run it is evaluated as used and will not presented for deletion. 



Figure 181 Table Variant Cleanup Preselection


All variants evaluated as not used are then displayed in dialog window. When you confirm the selection in this window variants are deleted from the system.

Report Variants Editor Tab

The Report Variant Editor provides an overview of all the Report Variants used in the Backend Testing and these Report Variants can be managed from this screen.



Figure 182 Report Variant Editor


The Report Variant editor provides you with the following functionalities:

  1. Create New Report Variant
  2. Delete Report Variants
  3. Transport Report Variants
  4. Edit Report Variants

Create New Report Variant

The Screen for creating new Report Variant is displayed by clicking on the 'Create New Report Variant' button (Ctrl + F3).



Figure 183 Create new Report Variant screen


In this screen you can define:

  1. RFC Destination – RFC destination that is to be used for Report Variant execution.
  2. Variant Description – The description of the new Report Variant.
  3. Report (required) – Technical name of report to be used for image creation.
  4. Report Variant (ABAP Variant) – Variant of specified report to be used when the report is executed. These variants can be manage ins transaction SE38.

The Report Variant is created after you click on the 'Continue' button (Enter). 
 KATE creates before and after images from report execution spool. Only reports that create such spools when executed in background job should be used.

Delete Report Variants

Deleting the existing Report Variants can be done easily by selecting the desired rows and clicking on the delete button in ALV toolbar.
 Any Report Variants that are still in use in the Backend Testing will be locked; therefore it is first necessary to delete these Report Variants from the given runs (or specific runs) before proceeding in deleting them permanently from the Report Variant Editor (i.e. system).

Transport Report Variants

It is possible to add the specified Report Variants to a transport to be transferred to another system (with KATE installed). To specify which of the Report Variants are to be transported you need to select them from the list as shown on Figure 184. There are options for filtering and sorting in the ALV table that can be used to select the specified Report Variants more easily. 



Figure 184 Selecting Report Variants to be transported


After selecting the desired Report Variants and clicking on the  'Transport Report Variants' button, choose your transport request. You can select the request and confirm the transport for the selected Report Variants. 
It is important to note that the Report Variants only carry information about KATE related items, and not the transformation structures themselves so they should be imported only to system where KATE is installed and the same reports/variants with same structure exist.

Edit Report Variant

You can edit the existing Report variants by double clicking on them in the table view. Only Variants that are not already in use in Test Runs can be edited. If a Report Variant is already used in the Test Runs, then the details can only be reviewed but not changed. 
When variant details are displayed you can check where this variant is used. By pressing the 'Where Used'  button a table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 



Figure 185 Where Used List for Variant

Copy Report Variants

You can create copies of Report variants by selecting multiple variants in selection table and then clicking on  'Copy Report Variants' toolbar button. For each selected variant new variant is created with exactly same settings as source variant. 



Figure 186 Copy Variants

Cleanup Report Variants

You can delete all unused Report variants by clicking on  'Cleanup Report Variants' button. First screen with preselection filters of variants is displayed and you can restrict which variants should be checked for deletion. After you confirm this screen, a check is done to find all unused variants. A variant is unused if it is not assigned to any Test Case or Test Run. 



Figure 187 Report Variant Cleanup Preselection


All variants evaluated as not used are displayed in the dialog window and when you confirm the selection in this window variants are deleted from the system.

Web Template Variant Editor Tab

The Web Template Variant editor provides an overview of all the WT Variants used in the Front end testing and these WT Variants can be managed from this screen.



Figure 188: Web Template Variants Editor Tab


The Web Template Variant editor provides you with the following functionalities:

  1. Create New WT Variant
  2. Generate WT Variants
  3. Delete WT Variants
  4. Edit WT Variants

Create new Web Template Variant

The Screen for Creating new Web Template Variant is displayed by clicking on the 'Create New Web Template Variant' button (F5).



Figure 189: Create new Web Template Variant

 
In this screen you can define following fields:

  1. RFC Destination – RFC destination that is to be used for Report Variant execution.
  2. Bookmark – Bookmark id for report (F4 help available based on RFC)
  3. Variant description
  4. After Image Variant ID – ID of the WT variant that is used for the after image creation. This allows you to compare the output of different Bookmarks or Bookmarks from different systems.


 If After Image Variant is filled, it's necessary to maintain the mapping between those different bookmarks tables. A screen will be automatically opened after creating such a variant. 

Generate Web Template Variants

The Screen for generation of Web Template Variant is displayed by clicking on the 'Generate New Web Template Variant' button (F6). Mass generation of WT variants is the fastest way to create variants with same settings for cross system testing.



Figure 190: Generate new Web Template Variant 


In this screen you can define following fields:

  1. Select option for bookmarks
  2. Variants description
  3. RFC flag – if unchecked local system variants will be created
  4. Source, target rfc system for variants

Delete Web Templates Variants

Deleting the existing WT Variants can be done easily by selecting the desired rows and clicking on the delete button in ALV toolbar.
 Any WT Variants that are still in use in Front End Testing will be locked; therefore, it is first necessary to delete these WT Variants from the given runs (or specific runs) before proceeding in deleting these permanently from the Web Template Variant Editor (i.e. system).

Edit Web Template Variant

To edit variant, double click on desired variant ID in the alv grid, to show variant details a screen where you can click the change button in the bottom right hand corner (CTRL + F1) to switch between edit and display mode.



Figure 191: Variant edit mode