Transaction Variants

Transaction variants simplify 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 are actually made up 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, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.

Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.

A specific namespace has been designated for cross-client transaction variants and screen variants and they are both 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. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.

Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).

The following sections contain additional information on how to create and maintain transaction variants:

Maintenance

Additional Functions

Transport