...
- 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.
- Variant Description – description Description of the new ListCube Variant.
- InfoProvider (required) – technical Technical name of the InfoProvider to be read. F4 help is available for this field.
- 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.
- Data Access Type:
- Read Online Data – option to read only online data via the ListCube.
- 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).
- 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.
- 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.
- 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 Validate additional aggregation is used.
- Display number of Hits – option for the column 'ROWCOUNT' to be added to the output of ListCube.
- 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.
Use Conversion: If enabled, on writing into the cluster step the info objects conversion exit will be applied to the data. Important Note: In the current version of Validate the Automated Root Cause Analysis doesn't support this.
- Characteristics in Output – selection of the defined characteristics to be selected from the InfoProvider (from Validate version 1.4.2 also navigational attributes are supported). All the key figures are always selected together with the unit characteristics*.
- 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.
...
| Warning | ||
|---|---|---|
| ||
| 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. |
...