...
- 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.
- Variant Description – The description of the new DTP Variant.
- 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 Validate .
- 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.
...
It is possible to add the specified DTP Variants to a transport to be transferred to another system (with KATE Validate 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.
...
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 Validate related items, and not the transformation structures themselves so they should be imported only to system where KATE Validate is installed and the same transformations with same structure exist.
...