Versions Compared

Old Version 1

changes.mady.by.user Anonymous

Saved on

compared with

New Version Current

changes.mady.by.user Marian Vidra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is a collection of Table Variants, after . After you click on the 'Variants' button, a screen for Table Variants selection is displayed.

...

  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. Table Name - name of a tested table (supported table categories are transparent table, view, cluster table and pooled table)
  4. Characteristics Fields – selection of the table fields to be used as characteristics. These fields will be used as the Key key fields in the comparison of table data.
    1. It is possible to specify characteristics selection as pattern. Pattern is always expanded to several single selections upon save.
  5. 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. 
    1. Number like fields are those with data type equal to:
      1. DEC
      2. CURR
      3. QUAN
      4. FTLP
      5. INT1
      6. INT2
      7. INT4
    2. It is possible to specify the key figure fields selection as pattern. Pattern is always expanded to several single selections upon save. If pattern is applied for both characteristic and key figure selections, all overlapping table fields are assigned to characteristics selection. 
  6. Select Number of Rows – is an option for the column 'ROWCOUNT' to be added into the output of Table.
  7. Set Filters (button) – used for defining the filter values to be used during DB table read. Maximum of 100 distinct filtering fields can used.

    It is possible to swap between the descriptions of table filtering fields and their technical name by clicking on  'Display Description/Technical Name' button
  8. 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.
  9. Set Tags - Set Tags – set tags to enable variant execution enhancements. See (DV-2002) Tags for more information about available tags. 
  10. Field Mapping ID - Set ID – set mapping to variant. Mapping renames columns and converts data elements of created images. To create new mapping, fill the field with mapping name and double click it. If mapping with such name does not exist yet, you will be navigated into the field mapping definition screen. See section (DV-2002) Field Mapping for more information how to define mapping. 

...

To save the Table variant click the 'Continue' (Enter) button. Before saving, 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, Validate can hold values with the maximum length of 74 characters. Values that are longer are truncated.

...

Note

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 Used Table variants must have the same number, type and order of table fields selected as characteristics. When so, Validate can compare the before/after image. If some table fields that are selected as Key Figures are missing in one of variants a variant in comparison to another variant, then these columns are not considered during the comparison.

...

Storage Management Table variant is a special type of Table Variant. It enables to compare of table data from various storages through the DVD Storage Management. This functionality is hidden in a standard release. If you want to turn it on, please contact us for support as this belongs to the expert settings.

Add Existing Table Variant Image Modified

The 'Add Existing Table Variant' button displays list of all existing Table variants in a the system and you can select one or more variants that are to be added into the current test case.

...

The 'Add Table Variants of Run' button displays list of all existing Table runs in the system and you can select a run that where variants to will be added into the current test case.

...

The 'Copy Table Variants of Run' button displays a list of all existing Table runs in the system and you can select a run that the where variants will be added into the current test case as copies.

...

The 'Add Variants of Test Case' button displays a list of all existing Table Test Case in the system and you can select a Test Case that the where variants are to will be added into the current test case.

...

The 'Copy Variants of Test Case' button displays list of all existing Table Test Case in the system and you can select Test Case that where variants to will be added into the current test case as copies.

Generate RFC Table Variants Image Modified

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 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 Validate 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. It is possible to swap between the descriptions of table filtering fields and their data element by clicking on  'Display Description/Technical Name' button. Fields for filter values are returned based on selected characteristic field in 'Filter Fields' input field and Tables selection (including patterns).                            
      
  5. Description suffix – Is 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.
  6. Select Number of Rows – is an option for the column 'ROWCOUNT' to be added into the output of Table.
  7. Tables Selection – In 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 the screen. It is possible to use patterns with asterisk sign (*) in the 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 background job can be executed after you click on  'Generate Variants in Background' button. 

Note

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. 

...

To edit existing Table variants, you double click on these in the table. Only the Table Variant that is not already used in Test Run can be edited from the Test Case definition screen. If the Table Variant is already used in one Test Run, it can be edited only in 'Select Table Variants' step of Test Run execution. If the Table Variant is already being used in more than one Test Run, its 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 table is displayed that contains all Test Plan/Test Case/Run ID information where this variant is used. 

...


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

...


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 checking 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 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 choose 'Compare Settings' option from the context menu.

...


A dialog with possible settings is displayed select . After you confirm the selection what is to be compared between variants. After you confirm the selection , a check is done and a 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' in the context menu. Dialog is then displayed where you can define which settings should be copied from the source variant to the after image variant (if there is any). 

...


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

Copy Variants

You can create copies of Table 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. 

...

Note

Any Table Variants that are still in use in the Backend Testing will be locked; therefore . Therefore it is necessary to delete the Table Variants from the given runs before they can be deleted from the Table Variant Editor.

...



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 . Once selected press confirm. 
It is important to note that Table Variants only carry the information about Validate related items and not the Table structures. These Variants should only be imported to a system where Validate is installed and the same Database Tables with the same structure exist.

...

You can delete all unused Table variants by clicking on  'Cleanup Table Variants' button. The First screen with preselection pre-selection 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. 



Table Variant Cleanup PreselectionPre-selection


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.

...