Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Transaction variant?

Former Member
0 Likes
533

Hi

What is a transaction variant?

Why do we need this variant,I mean what is the exact usage of creating a transaction variant?

Thanks

4 REPLIES 4
Read only

Former Member
0 Likes
501

hi,

use the transaction SHD0 , this used in cases where you need to make your own variants to the standard TCODES, like hiding some input fields, hiding some screens, make input disable , etc.

using Transaction varaints you can do all of them.

Regards

vijay

Read only

Former Member
Read only

Former Member
0 Likes
501

Read only

Former Member
0 Likes
501

hi

good

In the SAP Reference IMG, you can create transaction variants. Choose Basis Components ® Application Personalization ® Tailoring of Application Transactions ® Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.

To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).

Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).

To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.

Steps :-

Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.

Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.

Create and change the Zxxx area menu with the new transaction variant. In this way, the user does have to remembers any extra transaction codes.

In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate asstandard variant)

An example for using transaction variant (restricting the field displayfor CO11N - Goods movement) :-

If you want to restrict changes to the fields in Goods movement forone group of users.

1. Create a transaction variant for CO11N

2. Create a new transction code for the transaction variant and assign an authorization object to it

3. Divide the users into this two transaction code. Those who can change the field using CO11N. For those that have limited

field change, give them the authorizationfor ZCO11 (this is a new transaction code you have to create).

thanks

mrutyun