Вы находитесь на странице: 1из 4

Transaction Variant - A Step by Step Guide for Creation

Attachments:14 Added by Ashim Chowdhury, last edited by Leonardo Schmidt on Aug 18, 2011 (view change)

Author: Ashim Chowdhury Submitted: April 30, 2008 Related Links:


http://help.sap.com/saphelp_nw04/helpdata/en/67/232037ebf1cc09e10000009b38f889/f rameset.htm http://www.sap-basis-abap.com/sapbs010.htm http://www.erpgenie.com/abap/tvar.htm

Summary Transaction variant is a very efficient method to create some tailored version of standard SAP transaction without any actual modification. This article explains in a stepwise manner how to do that. The transaction chosen is CO01 - Create Production order.

Introduction
Transaction variants are created to personalize any standard SAP transaction. A transaction variant simplifies the usage of a transaction by tailoring some of the features as per the business need. It can be used 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. This document describes the step by step process to create a transaction variant for standard SAP transaction CO01 - create production order. The transaction variant should have the following restriction:

Order type is not visible in the initial screen. Menu path Order -> Create from Planned Order is deactivated

There are two steps, first create the transaction variant and then attach the transaction variant to a transaction.

Creation of Transaction Variant


Transaction variant can be created by through transaction code SHD0. The steps to create a transaction variant as follows: 1. Go to transaction SHD0. In the initial screen enter the transaction code (in this case CO01) for which we are going to create the transaction variant. Enter the name of the transaction

variant (say YCO01) in the "Transaction Variant" field and then click the "Create" button.

2. In the next screen transaction CO01 will be opened in recording mode. As we are going to hide the field "Order type", enter some default value (say PP01) in that field. For others we may or may not enter values. Click "Enter". A pop-up screen will appear.

3. In the "Confirm Screen Entries" pop-up screen we can customize the fields. Enter the screen variant name (say YCO01_0100) and short text (Test screen variant) here. Also for the field "Order type" check the Invisible checkbox to hide this field from the screen.

4. To deactivate some of the menu function click the button "Menu functions". A pop-up screen will appear. In the pop-up select the menu item "Order-> Create from planned order" and click the deactivate button.

5. The menu item will be deactivated (it will be highlighted in yellow). Click "Enter" to come back to the original screen entries pop-up.

6. Click "Exit and Save" button to save the Transaction variant. System will pop-up for a transport request. We can save it as a local transport or save it in some transport request.

7. We can test the transaction variant by clicking the "Test" button in the initial screen.

Assigning Transaction Variant to Transaction Code


After creating the transaction variant we need to assign it to a transaction. The transaction can be used by the user to get the required tailored version of the original transaction. The steps are as follows: 1. Go to transaction SE93. Enter the name of the transaction code (say YCO01_TCODE ) to be created and click the button "Create".

2. In the next pop-up screen enter the short text, select the radio button variant transaction and click enter.

3. In the next screen enter the transaction (CO01) and transaction variant (YCO01) created in the previous step. Click the "save" button to save the variant transaction.

The variant transaction (YCO01_TCODE) is now ready and it can be used to get the tailored version of the original production order creation (CO01) transaction code.

Result:
Initial Screen: Field "Order type" is not visible

Menu: Menu item "Create from planned order" is disabled

Related Content
http://help.sap.com/saphelp_nw04/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset .htm http://www.sap-basis-abap.com/sapbs010.htm http://www.erpgenie.com/abap/tvar.htm

Child Pages (1)


Hide Child Pages | View in Hierarchy transaction variant

Comments (5)

Show Comments

Used Transaction Variants to make your fields Mandatory, Hidden or Display You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available on 4.6x. 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).

Вам также может понравиться