Transaction Variants
Transaction variants simplify the transaction flow by:
● Inserting default values in fields
● Hiding and changing the ready-for-input status of fields
● Hiding and changing the attributes of table control columns
● Hiding individual menu functions
● Hiding entire screens.
Transaction variants consist of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may contain values for screens in multiple transactions, if the transaction flow makes this necessary.
There are both client-specific and cross-client transaction variants. Screen variants are always cross-client, they may be assigned to a client-specific transaction.
A specific namespace has been designated for cross-client transaction variants and screen variants and they are automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.
Transaction and screen variants may be created for all dialog and reporting transactions. There are certain restrictions, depending on how their corresponding transactions are utilized internally.
Transaction variants may not be created for transactions already containing predefined parameters (parameter transactions and variant transactions).
See also: