Scribd
Upload
158 views

Transaction Variants

Transaction variants allow customizing SAP screens by hiding fields, menus, tabs, and changing field properties. This document provides steps to create a transaction variant that 1) prevents creating new business partners and 2) hides the payment tab when viewing business partners. It involves recording a transaction variant using code SHD0, deactivating menus and marking tabs invisible, then testing the customized screens. The variant can be assigned as the standard variant or a new transaction code can be created.

Uploaded by

asimalamp
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
158 views

Transaction Variants

Transaction variants allow customizing SAP screens by hiding fields, menus, tabs, and changing field properties. This document provides steps to create a transaction variant that 1) prevents creating new business partners and 2) hides the payment tab when viewing business partners. It involves recording a transaction variant using code SHD0, deactivating menus and marking tabs invisible, then testing the customized screens. The variant can be assigned as the standard variant or a new transaction code can be created.

Uploaded by

asimalamp
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Transaction Variants

Step By Step Guide - Creating Transaction Variants


Purpose: The Purpose of transaction variants is to hide fields, menu functions, screens, to supply individual fields with default values or to change the ready for input status of one or more fields. Using transaction variant, you can tailor screens to meet your required business process, and it can be used to accomplish security task, not directly supported by SAPs security concepts. A Transaction variant consist of a number of screen variants, customized to meet your requirements, Transaction variant only alters the layout of the screen. The Business processes delivered by SAP retain their integrity.

Scenario In this example the scenario is: In transaction BP Business Partner, the user should not be able to create a new person. In transaction BP Business Partner, the user should not have access to the Payment tab.

Recording a Transaction Variant Transactions variant are recorded through transaction SHD0

1. Enter the transaction code you want to record here BP, and press enter 2. Enter a name for your transaction variant here Z_BP_NO_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y. 3. Push Create

You have now called transaction BP in recording mode.


1. When you push the exit button you will get the following popup

2. Enter a name for the screen variant e.g. Z_BP_NO_PERSON, 3. Press the deactivate menu function, and you get the following popup.

In this Popup you can deactivate menu functions.


1. Open the Menu Bar Business Partner Create

Position the cursor on SCREEN_1000_CRE_PERS Person


2. And push the deactivate button

3. Push enter

4. And Exit and Save

5. Save the Transaction Variant.

Test You can now test your transaction variant by pushing the test button

As you see the Person button is grayed out, and if you go to the menu Business partner Create, you can see that youre not allowed to create a person for the menu either. Removing the tab Payment Transactions In order to modify your transaction variant, you go to transaction SHD0

Press change with processing to enter the screen

2. Press exit,

You will now get a popup for each sub screen.

3. Enter a name for these all of these sub screens e.g. the screen name with a Z as prefix

When you reach Sub screen 1100_MAIN_ARE


4. flag the Payment transaction as invisible and push Exit and Save

5. Now save the transaction variant with Exit and Save. Notice that youll get a popup with a
transport request for each screen.

6. Now save the variant and go back to transaction SHD0 again.

When you now test the transaction variant, you can see that the tab strip Payment transactions has been removed.

Assigning the transaction Variant You can assign your newly created transaction variant to a transaction code by:

1. Assigning it as a standard variant for the transaction (here BP).


2. Create a new transaction code for the transaction variant.

Assign it as a standard variant for the transaction BP

If you want the transaction BP to start with the transaction variant, you can set this variant as the standard variant. This is done in SHD0 under the Tab Standard Variants

Here you enter your transaction variant, and activate it. If you now call transaction BP you will see that its started with your transaction Variant.

Please Notice that this activation isnt transported. You need to activate the transaction Variant on all receiving system.

Create a new transaction code for the transaction variant.

You also have the opportunity to create a new transaction for your transaction variant. By doing this you will end up with two transactions, one BP for the original version of transaction BP and one for your screen variant.

In order to create a new transaction code, choose from the menu Goto Create Variant Transaction. You will now get the following popup:

Enter a new Transaction code e.g. Z_BP_NO_PERSON, and a short text for this new transaction code, and press enter.

In the next screen flag Inherit GUI Attributes

Save and test your new transaction code.

You might also like