Which screen variant is active?

Hi everyone,
i have one really basic question - for the transaction MIRO there are several custom screen variants created.
How do I know which one is active?
Shouldn't a new screen variant be assigned to a transaction variant? And how do I see currently active transaction variant?
Thanks in advance!
MaryM

hi
goto SHD0
here select t code MIRo
niw in std varient seacrch for the varient of MIRO,now if the activate button is on then the varient is active and check accordingly
regards
KI

Similar Messages

Create transaction and screen variants

Hello
I want to create transaction variant for VA01 and MM01 in order to simplify the data entry. I know SAP has SHD0 as a tool and Synactive has GuiXT to make all these changes. But I wonder what are the differences between these 2 tools.
Please let me know,
Thanks,
George

Dear Mr.George,
Transaction Variant
You can only create transaction variants for dialog transactions and reporting
transactions.Only "normal" screens, dialog boxes, and subscreens can be
included in the variant.
Screen Variants are automatically created anytime you create a
transaction variant.
Initial Screen
Enter the name of the transaction and the transaction variant on the initial screen. The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto -> Client-specific transaction variants tp branch to the client-specific transaction variant maintenance transaction.
Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.
Creating the Transaction Variant
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
Here you can determine:
if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
if field contents are saved (the "With contents" checkbox)
if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
if specific fields should be hidden (the "Invisible" checkbox)
if specific fields should be mandatory the "Mandatory" checkbox)
You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
Choose the function Continue to proceed. The following pushbuttons are available:
The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
Enter a short text for your transaction variant here.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
You can also branch to this list using the Change values function during the function selection process.
Deleting Preassigned Values
You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.
If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.
Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.
If useful reward points.
Regards
Mangal

Transaction variant/Screen variant (SHDO)

Hello guys,
 Actually as far as i know, if we want to put default values for certain field in any transaction, than we can do it by SHDO.Am i right?
 Actually for production order header, i want to maintain certain default values for couple of fields.Through enhancement (PPCO0006) we can do it.But one of my friend told me that its even possible by SHDO.
So could u guys plz help me in doing this?I dont know the procedure.
In CO01 Screen, i want to maintain default values for following fields,
Plant- 1009
Order type- ZPP01.
 Thanking you guys for all the help you provided.

You can use transaction SHD0 to create transaction variant. The transaction variant can be assigned to user.
Please look into the below process.
Creating the Transaction Variant
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
Here you can determine:
if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
if field contents are saved (the "With contents" checkbox)
if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
if specific fields should be hidden (the "Invisible" checkbox)
if specific fields should be mandatory the "Mandatory" checkbox)
You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
Choose the function Continue to proceed. The following pushbuttons are available:
The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
Enter a short text for your transaction variant here.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
You can also branch to this list using the Change values function during the function selection process.
Apart from this there is alternative to use role/parameter-id's and assign to the user. In this case, whenever the user logins in all the cases same values would be populated on to the CO01 screen. This is easily done by the basis consultant.
Thanks,
Srinivas Karri

Screen Variant for PO Qty

All,
Can someone tell me which screen variant controls the PO Qty field in the Item Header when creating a PO?
Thanks,
Sean

Hi,
Go to IMG>Material Management>Purchasing>Purchase Order>Define Screen Layout at Document Level, there you can find the screen variant you want!
Good luck
Tao

Screen Variant / Transaction Variant

Hi
I am trying to create a Screen Variant for T-Code VA02. Want to change the Req. delivery date as display only (grey coloured), once it is filled in VA01, so that no one can change the same in VA02.
When I created the Screen Variant for SAPMV45A and Screen 4440, and tested the same it is fine. However when I created its transaction variant for the same screen Variant and activated it is not working, means the desired field is not greyed in VA02 transaction.
I am saving it in Local Object ($TMP). Can any one guide me what I am missing.
Thanks
Amitesh

Hi Raja
Thanks for your continuos support, however as I told you I have already gone through these documents and only then I am trying this. I have already implemented one screen variant for J1IIN.
But in this case as I mentioned above I am trying to make the field RV45A-KPRGBZ (Date Type for Required Delivery Date) and RV45A-KETDAT ( req. delivery Date) Grey in VA02, so once the field filled in VA01 no one can change it.
When I created the Screen variant and tested it its working OK. However when I created the transaction variant for this screen variant and activated it for the standard transaction and then tested it, it is not working. I have checked it in display mode and both the fields are ticked for "output only" and so the field "req.del. date" is also ticked for Output Only. still when I run the transaction VA02 it is not working.
Can you check at your end if you are on system. Or any other suggestion?
Regards
Amitesh

How to find out default screen variant name

Hi All,
For particular sales order creation I want to find out which screen variant has been used.
I have tried using SHD0, with entering Transaction code as VA01 but in that for Transaction variant field there are 5 different transaction variant names are mentioned.
Please guide me how to find out the transaction variant name used in va01 for particular sales order.
Thanks and regards,

Hi,
Goto VOV8 T.Code.
Select your order type.Details.
Check what is the transaction variant assigned to your order type.
It is used while creating the order.
This field is present in transaction flow tab.
Regards,
Krishna.

PS: Activity Allocation Screen Variant Display Issue

I'm having a problem in SAP v5.0 when I create a screen variant for Trans KB21N (Activity Allocation). The variant is available in the drop down list and works fine during the data entry session, however, when I press the 'Enter' key the system restores the screen variant back to the default variant. This is very disconcerting, am I missing something simple in the config?
Thanks,
Dave Flick
972-821-4211

I'm answering this post myself because SAP support gave me OSS note 913227 and this corrected the problem.
Thanks,
Dave Flick

Activating screen variant created in 4.7 Version

Dear All,
Want to know is there any way to activate the screen variant created in 4.7 version.
Thank you.
Regards,
Venkat

Dear All,
Come to know how to do that.
Thank you.
Regards,
Venkat.

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".

Screen Variant for VA02

Hi,
I have a requirement according to which I need to make few fields of transaction VA02 as output only.
While we create a sales order using VA01, all fields should be writable but when we open the sales order in change mode(using VA02) fields Ship-to-party, Net-Value should not be editable whereas all others should be. I have created a transaction variant for VA02 and also activated it. But the changes are not getting reflected when I open a sales order using VA02.
Can any body help please. Thanks in advance.
Regards,
Dhiraj

HI
After Creation of Screen for reflecting changes you have to active screen variant
Screen Activation procedure:-
STEP1: T-code:SHD0 --> Enter transaction code: VA02
STEP2: Click on "Stanrad Variant" tab --> Again choose "Standard variants tab"
STEP3: Enter your variant name --> click on Active(Button)[it is in right side of inputfield name]
Appreciate points if it is useful.
Thanks & Regards
Sudheer Madisetty

Regarding Screen Variant for tcode va11

hi all,
i am trying to create a screen variant for tcode va11. the fileds in the item level has to changed.. we have a requirement to show only those fields that are usefull as per our clients requirement.. there are fields which will never be used .. so we have top remove it .. i have created a screen variant and made all the fiedls not needed invisible .
then i link this csreen variant to a transaction varaiant .. howver when i execute
this i don't find any difference in screen .. guess my screen variant not working..
Is there anything we have to take care for table control.
the Program name is SAPMV45A
Screen number is 4900
please if any body has done this before ,,kindly suggest.
thanks and regards
Sriniavs

this variant is in Active state ?
what is system status ?
check which PF/GUI it is using .
system-->status>Program here u have to get ur Zvariant name.
Regards
Prabhu

Screen Variants disabled for FB50,FB60,FB70

Hello All,
The screen variants for FB50 FB60 FB70 disabled. These vairants can be selected as Edit --> Screen variant --> Select screen variant.
When any user executes transaction he gets some field missing (table control setting set as basic settings) and when he try from the above option for the desired screen then also screen remains same. It doesn't change
Previously it was not the case. previously when user executes these trasnaction screen was coming correctly.
Many users facing this issue.
If anyboday faced similer kind of issue then request you to please share your inputs.
Thanks & regards,
Prashant

Hi Prashant,
Please refer to notes 546889 and 186961.
if user is calling transaction FB*0 the first time no screen variant
for items is selected. So in order to assign a user to a screen variant,
the user has to switch the tree on (SHIFT+F1).
In the folder 'Screen variants for items' the user has to choose your
'default' variant by a double click. After clicking on the button
'Refresh Tree' this screen variant is saved in the table TFBUF, which
contains the personalizations for ENJOY transaction. This table is
always read by starting transaction FB*0. Because of the user
personalization with table TFBUF the SET/GET-Parameters SCRVAR & STV are
not used in the FI-Enjoy transactions. It's the enjoy and personlization
system design that always the last selected screen variant of the user
is used by starting transaction FB*0 and not a default one.
But I can suggest you a modification, for setting your default screen
variant in FB*0 with the value of parameter SCRVAR until the user will
chosse another screen variant in the tree. Furthermore this default
variant is set if user is executing 'Reset screen variant' under
EDIT -> Screen variant. You can find the program changes of this
modification below:
Because it is only possible to set standard for transaction variants and
not for screen variants and due to user personalization goal of the
enjoy transaction It cannot change this system behaviour during
maintenance.
Here is the program code for this modification:
1.
FORM posting_transaction_init.
If variant transaction is active, get screen variant     "Note 421236
      CALL FUNCTION 'RS_HDSYS_GET_SC_VARIANT'              "Note 331997
           EXPORTING                                       "Note 331997
                progname         = 'SAPLFSKB'              "Note 331997
                dynpro           = '0100'                  "Note 331997
           IMPORTING                                       "Note 331997
                scvariant        = g_scvariant             "Note 331997
           TABLES                                          "Note 331997
                values_scvariant = tab_values_scvariant    "Note 331997
                guixt_scripts    = tab_guixt_scripts.      "Note 331997
    ENDIF.                                                 "Note 421236
*Modification Begin of insert
    IF acc_kontext-scvariant IS INITIAL and g_scvariant is initial.
      GET PARAMETER ID 'SCRVAR' FIELD G_SCVARIANT.
    endif.
*Modification End of insert
    IF NOT g_scvariant IS INITIAL                           "Note430830
2.
FORM create_tree_treev_style_enj.
data entry variants
Only if screen variant not provided by transaction variant
*Modification begin of deletion
IF p_scvariant IS INITIAL.                               "Note 331997
*Modification end of deletion
    PERFORM create_tree_ev TABLES p_node_table.    " Erfassungsvarianten
    PERFORM create_item_ev TABLES p_item_table.
*Modification begin of deletion
ENDIF.                                                   "Note 331997
*Modification end of deletion
assignment models
PERFORM create_tree_km TABLES p_node_table.      "Kontierungsmuster
3.
MODULE tree OUTPUT.
read screen variants
Only if no screen variant provided by transaction var.   "Note 331997
*Modification Begin of deletion
IF g_scvariant IS INITIAL.                               "Note 331997
*Modification end of deletion
    PERFORM get_screen_variants.
*Modification Begin of deletion
ENDIF.                                                   "Note 331997
*Modification end of deletion
read parked documents if required.
I recommend you to check with your local consultants if this modification is suitable to your requirements.
Kind Regards,
Fernando Evangelista

Text Field is not displaying in MIRO , Screen Variant SHD0

Hi,
All Experts.
In my client TEXT field is not there in MIRO T.code. I heard Screen Variant can be a good option for adding field in MIRO.
Or is there any work around to bring TEXT ( SGTXT ) field in MIRO ?
I gone through the already posted threads regarding this, unfortunately no any perfect solution found.
Experts help will be great on this.
Regards,
Sharvari Joshi.

Hi,
Go to SHD0 and enter transaction code as MIRO
Then in first tab "Standard variant", sub tab "Standard Variants", do F4 on the field "Name"
You will get the list of the standard Variants for MIRO.
Then select one of them and press enter. It the "Activate Match Stick" is enables, that means that standard variant is not activated yet. Similarily check for other standard variants of MIRO.
If all the standard variant have "Activate Match Stick" enabled, then SAP MIRO should be showing SGTXT as a part of standard SAP.
Regards,
SDNer

Screen Variant is not reflecting same value in different transactions.

Hi Guys,
I need a help, it is urgency.
I done the screen variant for one filed is mandatory and another field in display mode (gray color) for transaction (FPR1 in ISU). After I done the screen variant the standard transaction code (FPR1) showing same result, what I am expecting.
But the problem is, I want to maintain or enter the values from CIC front office screen.
Once I confirm the BP and select the contract account to create install plan (FPR1), here it is open with standard view, which is not displayed with screen variant changes.
What should i check in that case. I already checked with
T.code : EWFC, EWBC.
Thanks in advance. Your guidance is appreciated
Regards,
Venkat.

Hi,
Even if you group valuation/view currency is the same as controlling area currency, the system will still show the message above. SAP need you to acknowledge that you're now costing for different valuation than your operation (legal valuation).
Note: Normally we execute sales order costing for group valuation in the background. You can read note 1819102 on how to remove that warning message when costing via background.
Thanks,
Ong Yang

Variable screen/variant screen authorization issue

HI All,
We have implemented standard Cost Center Overview Report(0SR_C02_Q0002) in BI 7.
We have three selection fields:
1.Company Code which is mandatory
2.My controlling Area which is also mandatory
3.Costcenter which is not mandatory
The requirement we are facing over here is that in the Variable screen/variant screen when I enter a company code, then I need to display dynamically only those "My Controlling Area" values which are assigned to that particular company code and not all. In the same way after selecting the appropriate "My controlling area" value, I need to display only those cost centers in the cost center selection field which are assigned to the selected company code and My controlling area combination and not all.
can anyone guide me on how to go about on this authorization issue at the variable screen itself.
Please treat this issue/requirement on high priority.
Appreciated in advance.
Regards,
raps.

Hi,
I think that an alternative to solve your concern could be using Web Application Designer (WAD). In this respect, there are several design options, with different levels of complexity.
As the simplest alternative, you could create a WAD including your query and three Dropdown Boxes: one for Company, a second for Controlling area and another for Cost center. The four mentioned elements should be linked to the same dataprovider so, when you select a company, the options in the other two Dropdown boxes and the information in the query are updated.
In order to enforce mandatory filter selection at Company and Controlling area level, you should set NO_REMOVE_FILTER='X' in both two Dropdown boxes, so that "All values" option -which would mean no filtering- is not offered.
I hope this helps you.
Regards,
Maximiliano

Which screen variant is active?

Similar Messages

Maybe you are looking for