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 SAP’s 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 Page 1 of 16 How to - Transaction Variants 5/18/2012 http://www.mhn-consulting.com/Security/transactionvariants.htm
Transcript
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 SAP’s 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
As you see the Person button is grayed out, and if you go to the menu Business partner � Create, you can see that you’re 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
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 it’s started with your transaction Variant. Please Notice that this activation isn’t transported. You need to activate the transaction Variant on all receiving system.
Create a new transaction code for the transaction v ariant. 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”
