Skip to Content
Author's profile photo Eslam Hosny

Transaction Variant

Transaction Variant

Prepared By: Eslam Hosny

In This Document we will learn the concept & how to create Transaction and Screen Variants to change screen layouts.

And how to assign those transactions and screens variants to:

  • A Standard Transaction
  • A group of users
  • A new transaction


Transaction Variants can simplify transaction runs as they allow you to:

  • Pre assign values to fields
  • Hide and change the ‘ready for input’ status of fields
  • Hide menu functions
  • Hide entire screens

A Transaction Variant is made up of a series of screen variants.

Screen variant contains field values and attributes for exactly one screen.

Transaction Code -> SHD0


The above Three Tabs in the T Code SHD0:

  • Transaction Variants – > Create Transaction Variants and assign Screen Variants
  • Screen Variants – > Create Screen Variants.
  • Standard Variants -> Used to assign Transaction Variants to standard transaction

                                               Create and assign Variant Groups to specifics users


Creating Transaction Variant from a Transaction (Transaction Variant TAB)

  • You can create the Screen Variant first  (Screen Variant TAB)and then create Transaction Variant (Transaction Variant TAB)
  • Or create both at the same time (Transaction Variant TAB) -> Preferred

Our Below Example will be on T Code IW31 (Create Maintenance Order)


  • Once You Pressed Create, The System Will Call The T Code IW31
  • Fill all the required fields  & Any Field you Want Then Press Enter


Once You Pressed Enter, The System Will Call A Configuration Screen That Represents The T Code IW31 In Forms Of Screens with its own Fields


  • W.Content: set the value you entered as default
  • Output Only: Dimmed
  • Invisible
  • Required: Mandatory

In Our Example



  • Press Enter If you want to change the another available screen In The T Code IW31
  • Press Exit & Save If You Finished

Result -> Transaction Variant Created With Its Screen Variants



Then You Can Test Your Transaction Variant




Using the Transaction Variant You Have Created

  • Assign it to The Standard Transaction
  • Assign it to a group of users
  • Assign it to a new transaction (Variant Transaction)

1- Assign The Transaction Variant To The Standard Transaction (Standard Variants TAB)

If you assign the Transaction Variant to transaction IW31 the changes will affect all the users that use the transaction.



2- Assign The Transaction Variant To A Group Of Users (Standard Variants TAB)

Here We Create a Group (Variant Group)


  • A Transaction Variant Generated Automatic Once You Create The Variant Group
  • Then Assign Users To The Variant Group
  • Set Proposal : To Active The Variant To The user


Then Go To Transaction Variants TAB & Put The Transaction Variant Generated in the previous step With The group & Create it as normal transaction variant or Assign the Screen Variants to it



3- Assign The Variant To A New Transaction (Variant Transaction)

You Have Two Options:

A- In T Code SHD0,  Then From Go To Menu -> Create Variant Transaction

B- From T Code SE93

We Will Work From T Code SE93




Then Save

You Can Now Use Your T Code



  • You cannot activate more than one transaction variant to a standard transaction, only one

For example:

If you created two transaction variant from T Code MM01, and you need to assign the two variant to the standard T Code (MM01) -> You cannot, only one can be assigned

  • If you created two transaction variants for example from T code MM01, and you assigned one to the T Code MM01 & the other to a user(s)

So all the users will work with first (assigned to the T Code MM01) & The User(s) will work with the variant that is assigned to

  • You can assign to a group (User(s)) more than one variant -> but the these variants must be from different T Codes


20/06/2016 by Jogeswara Rao Kavala

One more useful link on this subject:

Transaction Variant and Screen Variants  by Kleyson Rios


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo K Jogeswara Rao
      K Jogeswara Rao

      Very good Document

      Author's profile photo Eslam Hosny
      Eslam Hosny
      Blog Post Author

      Thanks Mr. Jogeswara Rao K

      Author's profile photo Former Member
      Former Member

      A Very Clean explanation. Great work, Thank you Eslam.  😎

      Author's profile photo Eslam Hosny
      Eslam Hosny
      Blog Post Author

      Thank you Karim

      Author's profile photo Phi Duy Dang
      Phi Duy Dang

      Thanks Eslam. Good job.

      Author's profile photo Former Member
      Former Member

      Excellent document . Thanks for sharing.

      Best regards,


      Author's profile photo Kali Charan
      Kali Charan

      Thank u This is useful.

      Author's profile photo Hemes Cool
      Hemes Cool

      Good document.



      Author's profile photo Former Member
      Former Member

      Very good document & anyone can easily understand.



      Author's profile photo Simone Rinaldo
      Simone Rinaldo

      Very good work