How to assign screen variant to transaction variant

Hi ALL
I HAVE CREATED A SCREEN VARIANT HOW TO I ASSIGN IT TO TRANSACTION VARIANT , PLS GUIDE ME ON THIS ITS IMPORTANT

Sunaina,
Transaction Variant:
Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Crux:- you just make fields as display, or 'supress', knowing your requirements
Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
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 as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
o Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
Hope this Clarifies your Doubt and Please Reward If Really Helpful
Regds
MM

Similar Messages

How to skip screens in a transaction

I m using transaction CU01, from the program i have to go to the third screen by skiping the first two,, is there any syntax for tht.
I know how to go directly for second screen
the syntax for tht is
call transaction 'CU01' and skip first screen.
Now my requirement is to go to 3rd screen.
Can anyone tell me how to proceed.
Thanks in advance.
Kalpanashri Rajendran

Hi Kalpanashri,
you can create a variant transaction.In variant transactions you can define screen number which should be called first.
to do this create a new transaction through se93 for the program.
then goto SHD0 transation to specify the variant for this transaction, here you can specify screen number.
then use normal call screen.
Hope this helps.
Award forum points to helpful answers

How to assign Authorisation to a transaction code

Hi ,
I have created a report and i have assigned a transaction code to it.
But i want only 3 users to access the transaction code when others try to access the Transaction code there should be a message saying that they are not authorised to view that.
Can someone help me out in this regard

Hi Arvind,
Go to TCode SE93 enter your Tcode and Change it. There enter Authorization object as S_TCODE.
Cheerz
Ram

How to assigned SHD0 Variants to user?

Dear All,
    I want to use SHD0 to hide the u2018DO not Display Valuesu2019 in MB52 .Now I used SHD0 to do it.
My step is:
1.     Created Transaction Variants:ZMB52_T and Screen Variants ZMB52_S
2.     Created Tcode: ZMB52, Created Variant Groups Group Name: ZMB52.
3.     Assign the user ,Set Proposal the user
Now I run ZMB52 that found all users have worked it .not the special user.
How can do it
Thanks

Hi sun ,
Transaction variants can only be used with dialog transactions.
so in this case its not possible to create a transaction variant for mb52 .
Regards ,
Rajesh

How to assign variant to user

Hi All,
I have created one variant. i want to assign this variant to one user.
Could you guide any one.
Thanks
Krishna

hi kumar,
Screens variants are generally used in simplifying the screens.
When you run a transaction you can provide values to fields in advance.
Or, you can hide and change the ready-for-input status of fields
A screen variant can hold field values and properties for a single screen. You can assign screen variants to transaction variants. For this you use SHD0 transaction.
For example, you want to permit certain users to view blocked invoices, but you do not want them to release. There is a transaction MRBR that shows all the blocked invoices, but this transasction also shows gives options and icons to permit release.
In order to remove such option of release together with that icon, you can create screen variant and assign to this transaction MRBR. In this screen variant you hide the option of release. The screen variant can be assigned to those users.
Field Status variants (FSV)are associated, generally with the GL accounts where control which field to be displayed, available for change etc when that GL is called.
FSVs are not available for any screen. Screen variant are available for all screens and transaction.
assign me the points....
Ranjit

Transaction Variant for Selection Screen

Hi, experts!
A question regarding transaction variants: Is it possible to create screen variants and transaction variants via SHD0 for selection screens? I' ve created a customer report with one selection screen including parameters and select options and would like to provide the users with a variant transaction for this.
Utilizing the "Save as variant" option from the selection screen itself works out perfectly, but this variant cannot be transported. And trying to create a transaction variant via SHD0 fails because values entered in the selection screen parameters and select options help screens are not saved and presented.
Any hints are more than welcome!
Regards,
Thomas

You wrote
Utilizing the "Save as variant" option from the selection screen itself works out perfectly, but this variant cannot be transported.
But, give the variant a name beginning with "CUS&" and this variant will be transported. Variant beginning with "CUS&" or "SAP&" are so-called "system variant" and are transported automatically. You can then copy the transaction code and use this new variant in the new transaction.
Regards,
Raymond

Transaction Variant and Screen Variant

Hi
I have created a transaction variant ZTX for transaction TX.
The First screen of transaction ZTX IS Screen 0100 for example.
The Screen variant is ZSVAR and only for the first screen of the transaction variant ZTX, which is created when creating the transaction variant.
Then, I activated the transaction variant to be a Standard Variant.
Now in my program, if I say,
1. Leave to screen 0100.
Then, it takes me to the initial screen of transaction ZTX but the effect of the transaction variant is not there.
But if i code it as
2. Leave to transaction TX.
I can see the effect of the transaction variant.
Why is this ?
More-over, I cannot code a " Leave to transaction" as I will lose a lot of history.
What could be the remedy ?
I am new to Transaction Variants and Screen Variants concepts.
Thanks in advance for your valuable inputs.
Kind Regards
Prasad

Hello Prasad,
Leave to transaction will be considered as a new dialog process, hence all memory will be cleared. Try look at the standard transaction TX whether it uses parameter ids on it screen fields. In your program, set these parameter ids with the last values you are working on, before you call "Leave to transaction".

Transaction variant misunderstood. I will reward points !!!!!

Hello Gurus, i am trying, for some time now, to create a transaction variant. The goal is to set a field read-only in the "ea13" transaction.
When is use "se93" to create a transaction variant i have to fill in the transaction variant name, but when i do that it says that the transaction variat does not exist, confusing because i want to create a new transaction variant.
When i use "shd0" and fill in the name of my new transaction variant and click create i don`t have any fields, everything is empty. Can anyone give me an exact example or something. I found on the forum a link to a step by step how to, but it didn`t work.
Im working on R/3 Release 4.6C.
Please help, i will reward lots of points !!!

Hi,
Starting Transaction Variants
A transaction can be started with a variant:
Using the Test function from the maintenance transaction
By a program that includes a call to function module RS_HDSYS_CALL_TC_VARIANT
Function module RS_HDSYS_GET_TC_VARIANT checks to see if a transaction variant is active and returns its name and (if possible) its current values (screen variants, inactive functions).
Using its own transaction code as a variant transaction.
When a transaction with variant is called using the Test function, for technical reasons it is started in call mode. Some transactions behave differently in call mode than when called directly.
A variant transaction is started either in call mode or LEAVE TO TRANSACTION, depending to how it is called.
If you call a transaction with variant from a program using the function module RS_HDSYS_CALL_TC_VARIANT, you can use the function module to determine which mode is called (call mode or LEAVE TO TRANSACTION).
Variant Transactions
A transaction with a variant can have its own transaction code, which you can then use to execute the transaction with the appropriate variant.
To create a variant transaction, proceed as follows:
Choose Goto ® Create vari. trans. from the initial transaction variant maintenance screen.
Enter a transaction name and corresponding short text. Transaction type Variant transaction is already set. The following screen already contains default values for the name of the calling transaction, the variant name, and the client-specific or cross-client variant checkbox.
Save your entries.
Example:
Variant ABC has been defined for transaction Z000. We now want to create the variant transaction ZVAR.
Name of the new transaction: ZVAR
Name of the calling transaction: Z000
Name of the variant: ABC
Transaction ZVAR starts transaction Z000 with variant ABC.
If the variant specified for a variant transaction does not exist (in the current client), then the calling transaction will be started without variant.
The Standard Transaction Variant
Standard transaction variants have a special purpose. You can use any transaction variant as a standard variant. Use the Activate and Deactivate functions to use a specific transaction variant as a standard variant or to deactivate it.
If a standard variant is active for a transaction, the system searches for the variant automatically whenever the transaction is started and adopts its values.
If a transaction with an active standard variant is started with another variant, the values of the standard variant are not imported.
If a transaction with an active standard variant is started in batch input mode, the values of the standard variant are not imported either.
Variant Transactions and Parameter Transactions
Variant transactions can be client-specific (this means that their corresponding variants can also be client-specific).
In a variant transaction, several screens can be given pre-assigned values or suppressed. In a parameter transaction this can only be done for the initial screen.
You can suppress as many screens as you like in variant transactions; in parameter transactions you can only suppress the initial screen. If a screen is suppressed in a variant transaction, it is never displayed. An initial screen that has been suppressed in a parameter transaction is only not displayed when the transaction is initially called.
You can use the function Change transaction type during transaction code maintenance to convert a parameter transaction to a variant transaction. The system creates a transaction variant and a screen variant for its initial screen containing the values of the parameter transaction. The system suggests the name CV_P_ for these variants. The default name may be changed. The variant is created for the called transaction. It can be changed in Transaction Variant Maintenance and Screen Variant Maintenance. The transaction variant can be created in the current client or as a cross-client variant.

Syst variable for transaction variant?

Hi,
How to identify current transaction code with variant. We can't use sy-tcode as it shows orginal transaction code. Sy-slset is also empty allways?
Thanks
Shekar

hi Reddy ,
check the Documentation of SHD0.Its nothing but modifications of Screen fields.
Regards
Prabhu
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
Regards
Prabhu
PS : Customer is First Points next

Problem in SHD0 about creation of Transaction Variant for VA02

Hi All,
My goal is to create a Transaction Variant for VA02 Variant that doesn't display the "Object Status" button under the page "Status" in the Header of Sales Orders.
To do so, I created a Transaction Variant in SHD0 (named ZTEST_VA02), the creation process creates the Screen Variants too, and i named them ZTEST_VA02_<dynpro_number>.
The Dynpro where I can found the button to hide is the SAPMV45A / 4305, so the Screen Variant Name is ZTEST_VA02_4305.
My problem is that If I test the single Screen Variant (ZTEST_VA02_4305) using the button in SHD0, I can see the whole transaction with my modify (the "Object Status" button is hidden), but testing the entire Transaction Variant ZTEST_VA02 I cannot see the modify and the Button is pretty visible.
I even tried to create a Transaction with Variant, in SE93, that launches the transaction VA02 with the variant ZTEST_VA02, and I tried to assign the Transaction Variant I created as a Standard Variant, in both cases the problem is that the modify doesn't appear to be applied.
For me this is a real mistery because If the Screen Variant is right (It works) I would expect to see that even the Transaction Variant is correct.
Does Anyone have (or have ever had) this problem?
Thank You very much for your attention.
Regards,
Claudio
PS: I forgot to mention that I'm working on SAP ECC 6.0
Edited by: Claudio Distrutti on Apr 4, 2008 11:47 AM

I too facing the similar problem when assigning the screen variant to transaction variant.
screen number where the 'Obj.Status' button is ' 4456
if executing the screen variant alone , it works perfectly,
once i assing to the transaction variant and test, the 'Obj.Status' button is visible.
does anyone got the solution?
Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

Issue in Transaction Variant creation

Hi,
We are trying to create a Transaction Variant for VA01 t-code so that we want to greyout the 'Payment terms' field in the sales order.
when I test the screen variant it is working fine where as the same is not working when assigned it to the transaction variant ?
any inputs ? idea ?
Thanks in advance,
Vasanth

The solution is here :
Screen variant for Create Sales order

What is a Transaction Variant?

hello abap gurus,
can u tell me what is a transaction variant and how does it works? i have a requirement that is to run an existing customized report program in the background. that means no user interface. i'm pretty new with abap programming. please help...
thanks,
sid

Use SE75 to create your own custom text ID for SAVE_TEXT object
Finding a user exit when you only have the function module name: Use table MODSAP with member=function module. This will give you the enhancement name that you can enter in SMOD.
To execute on OS command in SAP: Use program RSBDCOS0
Transaction Variants
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
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 as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
tables: tbtco.
data: jobcnt(1) type n,
      t_sdluname like tbtco-sdluname,
      t_strtdate like tbtco-strtdate,
      t_strttime like tbtco-strttime.
ZXXX is the job name to check for
select * from tbtco where jobname = 'ZXXX'
                      and strtdate = sy-datum
                      and status   = 'R'.
   add 1 to jobcnt = jobcnt.
    if jobcnt = 1.
       t_sdluname = tbtco-sdluname.
       t_strtdate = tbtco-strtdate.
       t_strttime = tbtco-strttime.
    else.
       exit.
    endif.
endselect.
if sy-subrc = 0.
   if jobcnt >= 1.
       message i999(b1) with t_sdluname ' has released job on '
                         t_strtdate t_strttime.
   endif.
endif.
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
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 as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
Using Transaction variants
Change SAP standard screens by hiding fields, screens, tabstrips, changing field properties, ... read on
Show all users per Application server
Transaction AL08
To log a user off via an ABAP
CALL 'SYST_LOGOFF'.
Advanced SM04 program
The following program displays the Ip address , workstation name , Nt user name etc. Plus you can send instant messages to users just by clicking on the user name. It will show a red band for users who exceeds session limit. ( That you can adjust ). Created this for R/3 4.6C and above. (Submitted by Joy Ramachandran) - Click here to download zuser.txt
Changing the SAP Logo on the top right of the SAPGui
Change file sapalogo.bmp in directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\default (SAP 4.6C)
Changing the Logo on the Right Hand Side ( Courtesy of: http://sapr3.tripod.com/ )
Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif       EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name                     Value to be set
START_IMAGE      ZXXXX.GIF
RESIZE_IMAGE     NO
Logoff and Login again
Automated transports
regards
vinod

On saving Transaction Variant for MM02 you cannot exit out

I created a transaction variant for MM02. The first problem that occured was an authorization message when I click saved. It saved the changes but then reported that I was not authorized to access MM02. Which I was not because I had authorization to run the new transaction variant. SAP solved that problem with note 529116. Now I can save and get a correct message: 'Your changes have been saved'.
But now the problem is I cannot exit out of the program because the Back and Exit buttons do not work. Has anyone else encountered this problem after implementing note 529116.

I too facing the similar problem when assigning the screen variant to transaction variant.
screen number where the 'Obj.Status' button is ' 4456
if executing the screen variant alone , it works perfectly,
once i assing to the transaction variant and test, the 'Obj.Status' button is visible.
does anyone got the solution?
Edited by: Thomas Paul jr on Oct 21, 2010 1:59 PM

SHD0 transaction variant for SM30: some FCODEs don't react

Hi,
I have a customizing table which contains data of kind "current settings", so it can be maintained on productiv systems without transport dialog.
At the moment it can only be reached within the customizing (SPRO).
it is maintained via SM30-dialog.
Now I need to maintain it with a normal transaction cause the admin people for the table have no authority to do customizing on productiv system.
I made a transaction variant in SHD0 for SM30. It works except on little thing:
the functioncodes BACK, CANC, don't work.
Any idea, how I could make them work.
At the moment the users has to kill the mode to leave the transaction variant.
Thanx in advance
Hans

Hi Atish,
the maintainance screen ist a transaction variant of SM30. (see subject)
I didn't develop anything on it.
In transaction variants you can only exclude function codes, but I didn't do this.
Thanx for your reply.
Hans

About Transaction Variants

Hi friends..
At Application level, i've to customize the screen ( eg. adding/editing the field option in application).
As we know that there r options such as BADIs, Screen-exits.
But i came to know about another options as "Transaction Variant"
Can anyone suggest me regarding this.
Thanks
Suren

Hi,
we can create Transaction Variants Using SHD0 Transaction.
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
Please check the links.
http://help.sap.com/saphelp_nw04/helpdata/en/7d/f639fb015111d396480000e82de14a/content.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/67/232037ebf1cc09e10000009b38f889/frameset.htm
Reward if useful.

How to assign screen variant to transaction variant

Similar Messages

Maybe you are looking for