Create transaction and screen variants

[Former Member]

Hello

I want to create transaction variant for VA01 and MM01 in order to simplify the data entry. I know SAP has SHD0 as a tool and Synactive has GuiXT to make all these changes. But I wonder what are the differences between these 2 tools.

Please let me know,

Thanks,

George

[former_member184655 · Accepted solution]

Dear Mr.George,

<u><b>Transaction Variant</b></u>

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.

<u><b>Screen Variants</b></u> are automatically created anytime you create a

transaction variant.

<u><b>Initial Screen</b></u>

Enter the name of the transaction and the transaction variant on the initial screen. The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto -> Client-specific transaction variants tp branch to 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.

Creating the Transaction Variant

Choose Create to create a variant.

The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).

Here you can determine:

if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)

if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")

if field contents are saved (the "With contents" checkbox)

if the ready for input status of specific fields should be revoked (the "Output only" checkbox)

if specific fields should be hidden (the "Invisible" checkbox)

if specific fields should be mandatory the "Mandatory" checkbox)

You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).

Screen variants are created automatically for each screen where values have been saved (adopted). 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 like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).

Choose the function Continue to proceed. The following pushbuttons are available:

The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.

The Menu functions function displays an additional dialog box wher you can deactivate menu functions.

The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).

The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).

Enter a short text for your transaction variant here.

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.

Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.

You can also branch to this list using the Change values function during the function selection process.

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.

<b>If useful reward points.</b>

Regards

Mangal