Skip to Content

Introduction:

Whenever you use a transaction in the SAP system to process specific business transactions, it often makes sense to adjust processing flow to mirror these business activities. This can be done by hiding all information not pertinent to the business. More important information should be placed in a better position creating a transaction variant alters the layout of the screen. Transaction variants are actually made up of a series of screen variants. The field values and settings for each screen in the transaction variant are stored in a screen variant.

Transaction variants used for the below purpose:

  1. Changing fields to read only(Display)
  2. Making master data / transaction fields to required/Invisible
  3. Inserting default values for the fields etc..

Here we will discuss with 2 simple examples:

  1. Making Cost centre responsible user required while creating/changing master data
  2. Making FV60/FBV2 (parked invoice) payment method field display only

Configuration:


  1. Making Cost centre responsible user required: There will be always requirement for the Master data field control. In this example in order to make cost centre user responsible required we are using the transaction variant.

Transaction:

SHD0

shd01.JPG

In the screen you have 3 tabs:

  • Standard Variants – used to assign Transaction Variants to standard transaction; create and assign

Variant Groups to specifics users; this tab will be used for activating transaction variants.

  • Transaction Variants – create Transaction Variants and assign Screen Variants; while process if creating transaction variants screen variants will assign automatically.
  • Screen Variants – create Screen Variants. Screen variants will be created at the time of recording transaction.


Transaction Code

KS01

Transaction Variant

ZKS01

shd02.JPG

Press on Create button.

Provide controlling area and other details including screen variant short text as well.

shd03.JPG

Click on enter and provide cost centre and valid from details

shd04.JPG

Press on Enter and provide screen variant text and press on enter

260704a.JPG

Provide some test data and press on enter again. You may get one more screen for screen variant short text here, Please enter short text and press on enter.

Here you will get the screen variant for user responsible. Please select ‘User Responsible’ field required.

shd05.JPG

Press on Enter till you get main screen and save.

Provide short text and save the variant in Package along with transport which you have created.

shd06.JPG

Save and press on back arrow.

Here you can see the screen variants created for the transaction variants.

shd07.JPG

We need to activate above transaction variant by going to ‘Standard variants’ tab from the same transaction.

shd08.JPG

Press on activate button and ignore warning message. Please note that this step should be performed in each client.

Do the same configuration for the transaction KS02 (Change cost centre) when anyone try to remove user responsible system say that cost centre user responsible is mandatory.

Now go to KS01 and check for new master data creation whether ‘Cost Centre user responsible field is required or not.

shd09.JPG


2.  Making FV60/FBV2 (parked invoice) payment method field display only: Sometimes business may require option that user should not modify some fields from the particular transaction. Posted document field changes can be controlled through standard configuration (document change rules) but parked document is not possible. This can be achieved through transaction variant.

Transaction:

SHD0

Create screen variants for the transaction variant same as example1.

Transaction Code

FV60

Transaction Variant

ZFV60

Record all screen variants till you get for payment method screen and make ‘payment method’ field display (Output Only).

shd011.JPG

Save screen variant in your package (transport) as mentioned in example1.

shd012.JPG

Activate created Transaction variant

shd013.JPG

Do the same config as above for the transaction FBV2 (Change parked document) and activate transaction variant.

Now you go and check for the transactions FV60 and FBV2 for the field ‘payment method’. The field should be in display only.

shd014.JPG

Note: Transaction variants should be configured in development or Golden client with the package. As a functional consultant if you have any issue in creating package please contact abaper. Transaction variants should  be activated manually in each client.

Thanks & Regards,

Prasad


To report this post you need to login first.

53 Comments

You must be Logged on to comment or reply to a post.

    1. Kamal Kumar

      I’m unable to create a Z transaction variant via SHD0 in the testing client as the authorization is display only. It can be created in the development client but the recording does not pass as the data needed to move to the next screen on the standard transaction do not exist in this client?

      Do I need appropriate authorization from the BASIS to be able to create Z transaction variant via SHD0 in the testing client of the development system? Thanks

      (0) 
    1. Prasad Tatikonda Post author

      Hi Ravi,

      Thank you. You people are the inspiration to write these kind of documents and blogs for the newly joining consultants in SCN.

      Regards,

      prasad

      (0) 
  1. VasuDev Prabhu

    hi, Good article.

    I have a query on SHD0. I am trying this on FF_5. so user need not select variant everytime and We can default values directly.

    But i am not able to create. Is there any restriction for FF_5?

    (0) 
    1. Prasad Tatikonda Post author

      Hi Vasu Dev,

      There is no restriction to transaction FF_5. Please check whether you have activated transaction variant correctly and saved in package.

      In my opinion variant is the best option where you can select variant attributes for reports.

      Thanks & Regards,

      Prasad

      (0) 
        1. Prasad Tatikonda Post author

          Hi Vasu Dev,

          Please ask you abaper to create one package with transport for you. You can even save in local object and check.

          Thanks & Regards,

          Prasad

          (0) 
      1. rakesh kumar kumar

        Hi Prasad,

        really good ,but this would help for end user,we working in cockpit we want to create layout where we can see payment terms ,payment released of vendors ,we use to go for FB03 t code to see the payment released or not,we want to save the time ,instead of going to FB03 t code we want to see in the Cockpit it self ,please advice how we can create layout like our requirement please provide with screen shot.

        (0) 
      1. nikki saju

        Thanks for the document.

        When I tried to save in a package, system is saying I cannot use the selected package.

        What is the package and which one I should use to save the screen variant ?

        (0) 
  2. Sagar Mahesuni

    Hi Prasad,

    In your article have such a kind information is available and keep it up this is could be helpful to me and new comers in SAP FICO.

    Thanks a lot…, 🙂

    Best Regards,

    Sagar

    (0) 
  3. Mao Ye

    Hi Prasad,

    it is very nice of you if you can tell us how the settings will affect the users. my question is once it is done including the transaction variant and the standard variant, will every user has the same setting when run a particular transaction with transaction variant?

    how it is applied to user?

    Regards,

    Alex

    (0) 

Leave a Reply