Transport a display variant ( screen variant )

Hi,
I have copied a standard display variant (screen variant to choose the fields on output) to Z variant with some more fields added into it.
I need to tranport this Zvariant to the production system
Can any one help to how do i insert this variant into the tranport.
thanks
Sandhya

the program RSTRANSP is to be run for transportin variants.
plz chk this link:
Re: Transporting Screen variants

Similar Messages

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

Sales document - std variant - screen variant -sales order ?

Dear SD experts,
We have assigned a variant in sales document type through VOV8, which is doing the job of WBS element mandatory field at account assignment level while creating sales order thru VA01.
Now I have requirement that the item level WBS element also mandatory field while creating sales order thru VA01 in addition to above head level.
For this I have modified the the Variant thru SHD0 and made the Item level mandatory, but this modification is being affected to all the line items, which are not being filled with data, so if I have to use one line item, the rest of line items have WBS element as mandatory and it is not allowing the order to save.
Kindly suggest solution how to ensure that the line item which is being filled is only applicable the said WBS element mandatory.
Please help.
Thanx in advance
Regards
Srihari

hi
yes, this is one we are using as of now. but still we want if anything else thru SHDO transaction.
suggested solution, can save the sales order if user not gone to the edit incompletion log or ignored. this needs lot of user discipline unlike the mandatory field.
thanx once again,
regards
srihari

Screen Variant

Dear friends,
what is transaction Variant/ Screen Variant/Gui XT pls explain step by step
Thanking you
Regards
Reddy
[email protected]

Hi Reddy,
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,
Thanks and Regards,
Sateesh.Kandula

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

Screen Variant Not working

Hi,
I have created one screen variant for screen for SAPLBBP_SC_UI_ITS screen 230.
It's getting called while i checked by debugging .
But its not working in ITS Template & in transaction also .
In SAPgui it's not working .
Is there any more setting for Screen variant apart from just save it & called in screen variant BADI .
Thanks,
SS

Hi
<u>This BADI as you can see by name is for Screen Variants.
BBP_SCREENVARIANT in this case.</u>
<b>Please read the following documentation to get the clear difference</b>
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).
Screen variants
Screen variants allow you to simplify screen editing by:
Inserting default values in fields
Hiding and changing the ready for input status of fields
Hiding and changing the attributes of table control columns
A screen variant contains field values and attributes for exactly one screen. A screen variant can, howevever, be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.
For more information, see: Calling Screen Variants
A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Screen Variant for BBP_POC

Hi,
in transaction BBP_POC,
is it possible to create a screen variant via SHD0 so that field ITEMTYPE (BBP_PDH_PO_SCREEN_ITEMS-POS_TYPE) has a fixed content?
e.g. itemtype = 'M'.
I´ve tried via "Modify with processing" button but i´m not able to.
Best regards.
Edited by: Pablo Casamayor on May 25, 2009 10:54 AM

Hi Pablo,
Have you tried using the following Screen Variant:
Screen variant       BBP_PO
Program               SAPLBBP_POC
Screen                 4000
Thanks,
Pradeep

To display the selection screen variant name in WAD report output.

Hello experts,
I have a requirement which is to display the selection screen variant description in the output of the WAD report.
I managed halfway, by using the object "Information field", which displays all the values which are selected by the variant.
Example:I have created a cost center report created using WAD, since I need some graphical displays..
In the selection screen, I have the characteristic "cost center" as input field. I have created a variant " GM - IT" which will include few cost centers managed by GM. In the output, I want the dispaly to be "Cost center - GM IT". Currently it displays "Cost Center - a,b,c,d" as the values a,b,c,d are the values from the variant name "GM-IT"
Please let me know if this required any java script. I am not familiar with java / html codes and any help would be much appreciated (and rewarded)
Thanks in advance
KS

Hi,
Try this.
If you want to include your variables in your WAD means you have to choose "Force Variable Screen" option to be in enabled condition.
TO enable this,in WAD select your Template(New Template1) click the WEBITEM , it'll shows all generic properties , here you can enable this "Force variable screen"
Save and execute your WAD now you can get your variable screen.
Thanks,
JituK

How to transport a transaction variant and her related screen variant?

Hello to every SDN member,
I am looking to transport a transaction variant and the related screen variants.
I read the help and I am concerned by the paragraph about the Client-specific transaction variants because when I created the transaction variant, no dialog box appeared.
In the paragraph about the Client-specific transaction variants, it is told to transport the variants with the Transport function but the problem is that I cannot find it. How can I use this function? It is not in the toolbar and not in the differents menus.
Can you please give me the solution to transport the transaction variant and the screen variant?
Thank you very much in advance.
Best regards,
Matthieu Chérier

Hi,
You can transport a variant by :
1. Running the program RSTRANSP. Mention your program and variant name there.
2.Create a variant with prefix 'CUS&'. This type of variants will be automatically transported to target system through transport request.
3.Go to Se38 --> Input report name --> Select Variants
On the screen --> Go to Utilities -> Select transport request
--> Provide the program name and Variant --> Assign Transport request to variant. Then release the transport.
Regards.

How to transport a Screen variant from one system to other

Hi All,
I created a screen variant in Dev. It was included in a transport request. But when I transported the request to Quality, The transaction is not behaving according to the screen variant. i.e. Screen variant has not got transported there.
Please help me out what can be done in this regard.
Thanks a lot.
Himanshu

Check the status of the request which u have transported, whether it includes the screen variant also.

SCREEN VARIANTS" and "MAINTANANCE AND TRANSPORT OBJECTS"

Hello Guru's,
am in upgradation now in the stage of working with "SPAU"
I want to do compare "SCREEN VARIANTS" and "MAINTANANCE AND TRANSPORT OBJECTS"
with old to new versions
can we do that with SPAU or any other will required?
help me on the above
points will be rewarded>>>(**)
Thanks in advance.......

Hello Guru's,
am in upgradation now in the stage of working with "SPAU"
I want to do compare "SCREEN VARIANTS" and "MAINTANANCE AND TRANSPORT OBJECTS"
with old to new versions
can we do that with SPAU or any other will required?
help me on the above
points will be rewarded>>>(**)
Thanks in advance.......

Transporting Screen variants

This is for an upgrade project of a system from 4.6c to ecc 6.0. There are nearly 400 screen and transaction variants that donot have any transport request numbers. how can i transport these objects???
Please help.
Thanx & regards
Sujai

Hi,
From SE03, manually insert the screen variants in to the request using the following,
Program id : R3TR
Object: SCVI
Object name : Screen variant name
This is again tedious as you need to include all the screen variants that are created in the system,
Alternatively, you can create a small utility in ABAP to include the screen variants to the transport request thro' the selection screen,
Hope this helps,
Rgds,

FB50 Screen variant transport

Hi,
I have created screen variant for FB50 using SHD0. Now, how can we transport this variant to other client. I have read other threads for variant trasport but none of them is working for me. I tried SE38 but was totally confused.
Thank you,
Joseph

Hello,
You can use SE38, you use the name of the program SAPMF05A and select Variants.
In the menu goto->Variants (or CTRL + F1).
Enter the name of the variant (you can create it here by pressing the button CREATE.)
Next in the menu UTILITIES -> transport request, enter the name of the programm and the variant you have created. Then execute.

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

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

Transport a display variant ( screen variant )

Similar Messages

Maybe you are looking for