Hi,
I hope below documentation will help you :
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.
The values of which variants are applied?
There are the following orders:
1. Variant transaction
2. Variant group
3. Standard variant
When calling an application, the system first determines if it was called with a transaction variant (as a variant transaction), if this is not the case, the system then checks if there is a variant from a variant group for him for the application, if this is not the case, the system finally checks if there is an active standard variant for the application.
If an application sets variants internally, the application itself determines if these variants have priority. If necessary, this can also only be the case for individual screens (--> screen variants)
Which authorizations do the users need?
Users who work with variant groups need the authorization for the original transaction (as is also the case with standard variants).
However, it is guaranteed that you only see the characteristics that belong to "your" groups:
In every transaction start, the transaction variants that belong to the group are set.
Users can only change between the variant groups that are assigned to them.
How can users change between variant groups?
The SHD_SWITCH transaction is used for changing between the variant groups:
If you choose the SHD_SWITCH transaction, you receive an initial screen with a field in which the group that is currently active is displayed.
By choosing "possible entries" (F4), a list of all groups that you can choose is displayed. The "empty group" (no entry in the group name column) can also be selected.
If you select a group, the selected group is now displayed in the initial screen.
Save the new settings.
See the note in the initial screen and start all the applications again.
Client-Dependence
The variant groups and the relevant transaction variants are fundamentally client-independent.
As users are client-dependent, the assignments are also client-dependent.
Restrictions
Only one group can be active, it is NOT possible to work in different sessions with different variant groups. After the group is changed, the applications must be re-started.
Due to the naming convention, it is not possible to use the same variant for different transaction variants.
Otherwise, the same restrictions apply as is also the case with other transaction variants (see "Restrictions" unit, "Special Features", note 331360).
Hrishi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.