Page Comparison

...

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 Datavard Validate 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 from Datavard Validate 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.

...

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 KATEDatavard Validate. 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 KATEDatavard Validate. 

For ADSO InfoProviders the filter is created on top of 0REQTSN field while using same logic. For composite providers filters are created on both 0REQUID and 0REQTSN fields.

...

• 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 from Datavard Validate 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, MultiProviders, certain types of ADSOs and Composite Providers. For other InfoProviders this setting is ignored, as it is not possible to use the filtering on 0REQUID/0REQTSN field in the ListCube. For InfoCubes this setting influences only the read data from the Fact table. For ADSOs read of data from Inbound table. Please note that in MultiProvider Cubes, this setting will affect the InfoCubes below but not the DSOs as their data have 0REQUID set to value ‘0’. 
• t to value '0'.

...

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 from Datavard Validate 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 from Datavard Validate 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  Datavard Validate does not support more than a 100 different characteristics for filtering.
   
   

...

1. Characteristics in Output – The selection of characteristics for the InfoObjects that are to be selected in the ListCube Variants (from KATE from Datavard Validate 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 from Datavard Validate 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  Datavard Validate does support using more than 100 different characteristics for the filtering.

...

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 From Datavard Validate 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. 

...

By clicking on 'Generate OutBoard Variants' button you can generate ListCube variants based on NLS secondary indexes. This option is available only when DataVard OutBoard ^TM is installed on the same system as KATEDatavard Validate.

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

...

1. Characteristics in Output – The selection of characteristics for the InfoObjects that are to be selected in the ListCube Variants (from KATE from Datavard Validate 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 from Datavard Validate 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  Datavard Validate does support using more than 100 different characteristics for the filtering.

...

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 From Datavard Validate 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. 

...

You can add ListCube Variants to a transport so these can be transferred to another system (with KATE with Datavard Validate 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. 

...

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 about Datavard Validate 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.

...