You can only create transaction variants for dialog transactions and reporting transactions.
Only "normal" screens, dialog boxes, and subscreens can be included in the variant.
To create a transaction variant, proceed as follows:
The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto ® Client-specific transaction variants to branch the client-specific transaction variant maintenance transaction.
Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.
The system calls the application transaction that you want to create a variant for.
Adopt field values |
Saves the field values you have inserted on the current screen |
Do not display screen |
Hides screen |
With contents |
Field contents are saved with it |
Output only |
Field is no longer ready for input (display mode only) |
Invisible |
Hides field |
Mandatory |
Required field |
You may or may not be able to select each of these checkboxes for every field depending on the field's type (see
Requirements).Screen variants are created automatically for each screen where values have been saved (copied). Enter screen variant names in the Name of screen variant: field. These names must be unique. If the system is able to find a unique name for a screen variant, it is automatically inserted into this field. (The convention reads as follows: <name_of_transaction_variant>_(<client>)_<screen_number>.)
The following pushbuttons are available from this dialog box:
Cancel |
Displays current application transaction screen again. Here you can make changes to your settings. |
Deactivate menu functions |
Deactivates menu functions in an additional dialog box. |
GuiXT |
Allows user to edit a GuiXT script for the current screen ( GuiXT). |
Exit and Save |
Exits and saves application transaction. |
You can also branch to this list using the Change values function during the function selection process.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Deleting Preassigned Values
You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.
If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.
Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.