What is t-code SHD0's 'Variant Groups' used for?

[Former Member]

hi all:

What is t-code SHD0's 'Variant Groups' used for?

It seems can't work,who can help me?

thanksss.

[Former Member]

hi,

SHD0 is used to create transaction variants, by using transaction variant you can supress fields, set default value many more in standard transactions.

by transaction variant you can

􀁺 Predefine fields with values

􀁺 Suppress fields

􀁺 Hide screens

please check

http://husnie.wordpress.com/2007/12/21/changing-the-sap-standard-transaction-variant/

http://www.saptechnical.com/Tutorials/ABAP/TransactionVariant/Create.htm

http://help.sap.com/saphelp_nw70/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/7d/f63a0a015111d396480000e82de14a/content.htm

Yogesh N

[Former Member]

Variant groups

An extension of the standard variants is involved in the variant groups; the standard groups are often insufficient:

Different users (groups) should work with different variants;

Some users should be able to execute a transaction with different variants.

This is possible - in addition to the advantages that the standard variants offer - with variant groups:

Variants from variant groups are automatically applied, but only for users that are assigned to them.

A user can be assigned to several groups and can change the assignment.

The values of the groups are not applied in the batch input mode.

If a transaction is started with another transaction variant, the values are not additionally applied to a variant group.

How are the variant groups maintained?

You can enter the group names on the "Variant Group" tab and maintain variant groups with the "Create" or "Change" functions.

The group name must be in the "correct" namespace.

In addition, there are two Where-Used Lists:

Which users are assigned to the group,

For which transactions the group applies.

Which transaction variants belong to the groups?

The name of a transaction variant that is to belong to a group meets the following naming conventions:

<Name of variant group><name of transaction code>. Example: A transaction variant is to be created for the XYZ transaction that belongs to GROUP1. The name of the transaction variant is then GROUP1XYZ.

Due to this naming convention, the group name must be in the "correct" namespace.

Transaction variants that (randomly) meet this naming convention do not necessarily belong to a group. The group assignment is activated by

1. Creating a group

2. Assigning users to this group

A transaction variant that belongs to a group can also be used this way, like a transaction variant without a group.

How are the transaction variants that belong to a group maintained?

Transaction variants that belong to a group are maintained in the same way as all other transaction variants, they are distinguished using a naming convention (<name of variant group> <name of transaction codes>).

They can be maintained in the "transaction variants" tab or in the "variant groups" tab. If you maintain them in the "variant groups" tab, you must always enter the transaction code so that the name of the transaction variant can be determined.

Under what conditions is a variant from a group applied?

A variant from a group is applied if users are assigned.

(Only for the assigned users, all other users get the original transaction with a variant from a different group.)

It is NOT sufficient to

Create a group

Create a variant that satisfies the naming convention.

How do you assign users to groups?

You can assign users in the "variant groups" tab in the "user assignment".

Enter the user name.

The user is assigned to the group with the "assign" function, but they see original transaction(s) or the transactions with variants from another group as the proposal.

The assignment of users to the group is deleted using the "delete assignment" function.

The user is assigned to the group using the "Set Proposal" function and the relevant transactions are started for this user with the corresponding variants.

The proposal is canceled with the "Cancel Proposal" function, the assignment itself remains.

If you enter the user names generically (*), you receive a selection screen in which you can

Choose whether assignments or proposals are to be changed

Further restrict user names (the group in the "all users from group" option has nothing to do with the variant group, it concerns the "user group for authorization check" from the user master record (logon data)).

By choosing "Execute", you receive a list in which you can further restrict the user selection. The "Save" function saves the assignments for all selected users.

If you want to start the report in the background, you can choose if just the list should be outputted, or if the database changes should also be performed.

If a user is additionally also to be able to execute the original transaction, he must be assigned to the "empty group", the allocation takes place in the same way, in this case, nothing is simply entered in the group name field.

Regards,

Joy.