Title
Converting a Transaction Variant into a Number of Screen Variants

Prerequisites
Report RSHD_TV_SCRV is only for use by those customers that usetransaction variants or that have applications for which transactionvariants have been delivered. The transaction variant concept and itsfunctionality have been reworked for Release 4.6A.
New Functionality in Release 4.6A:
- In addition to transaction variants, that will continue to exist,there are so-called screen variants that allow the user to set valuesand attributes for fields in exactly one screen.
- Cross-client transaction variants and scrren variants now have theirown customer namespace and are automatically attached to the WorkbenchOrganizer.
The new functions available make a technical change necessary in howdata is stored. Report RSHD_TV_SCRV_XPRA automatically converts alltransaction variants found in the system to the new technical structurewhen upgrading from Release 3.0x, 3.1x, 4.0x, or 4.5x to Release 4.6x.

Features
This report reads all table entries for the transaction entriesselected on the selection screen. The names of existing transactionvariants are changed: The system inserts the name of the transaction infront of the variant name. For example, the transaction variant 'TEST'for transaction 'SE38' is renamed 'SE38_TEST'. Screen variants arecreated for each screen present in the transaction variant. Their namesare constructed as follows: (client)__. Screen variants with the same name are notoverwritten. The tables of the new structures are filled with theseentries.
Transaction variants that cannot be converted are noted and highlightedat the end of the list.
Transaction variant names are adjusted for variant transactions aswell, just as described above. Variant transactions that hat cannot beconverted are noted and highlighted at the end of the list as well.

What do I do if...

...not all transaction variants were converted?
This can happen form one or more of the following reasons:

• A transaction variant with the same name already exists in the system

either because the transaction variant has already been converted, or
because a transaction variant with the new name already exists in thesystem (for example, one delivered by SAP that has already beenconverted).

• The system was unable to choose a name, since its suggestion would have
contained more than 30 characters (this can only happen withtransactions whose names contain more than 15 characters).
If necessary, use report RSHD_TV_SCRV_SG to convert the transactionvariants manually. You may select new transaction variant names freelyaccording to your own criteria in this report.
Old (that is, not converted) and new (converted) transaction variantscan be compared using Report RS_HD_SCRV_COMP.

...not all variant transactions were converted?
This can happen form one or more of the following reasons:


• The (old) variant transaction is invalid,

because the transaction called does not exist, or
because the (old) variant transaction does not exist

• The new variant transaction already exists,

because it has already been converted, or
because the corresponding (new) variant already exists

• The new variant transaction does not exist,

because the (old) variant transaction could not be converted
Convert any of the variant transactions you need manually (transactioncode maintenance):
Replace the old transaction variant with a new one, but do not changeany of the other settings.
Old (that is, not converted) and new (converted) transaction variants
can be compared using Report RS_HD_SCRV_COMP.

Parameters

Transaction
Name of the transaction(s) whose variants you want to convert

Variant
Name of the variant(s) that you want to convert

Client
Client where the variants should be converted (if you select "Variantsfrom all clients", the system ignores any entries in this field).

Variants from all clients
If this field is selected, all client-specific variants from allclients are converted (any entry found in field "Client" is ignored inthis case).

Cross-client variants
If this field is selected, all cross-client variants are converted.

Change database
If this field is selected, all variants are converted in the databaseas well.
If this field is not selected, no changes are made to the database anda list of those variants converted is output instead.

Variant transactions too
If this field is selected, variant transactions are converted as well.

Display unconverted ones only
If this field is selected, only those variants (and varianttransactions) that could not be converted appear in the list that isoutput.