Change existing screen variants of certain z t-code.

Hi,
I have a zT-code which has some existing screen variants , one of them is say z_2904.
Now It is required to change one field in this screen variant z_2904 to display only.
I can see the screen variant in SHD0 but the check boxes are in disabled mode.
Please tell me how to change these fields to output mode in the variant.
Thanks,
Sucharita.

hi....
THIS IS TESTED PROCEDURE
execute the program which is having varient...
click on varient and get its value for scrren assignment....
now edit the values accordingly with new values...
now go to push button SCREEN ASSIGNMENT..
now you will get an option to overwrite the varient..overwrite it.
IN SHDO..you can add the varient after you have created it
regards

Similar Messages

Procedure to define screen variant

Hi all,
Please explain the complete procedure to define screen variant for fast data entry.

Hi,
You can use T. code O7E6 to define screen variant for fast data entry for G/L accounts, here you can copy from existing screen variant and make the desired changes for fields, their length and their length like wise can use T. code O7E5 to define screen variant for fast data entry for invoices/memos and also can use T. code O7E4 to define screen variant for fast data entry for Park documents and remember after defining the screen variant you need to activate them also we can use them for fast data entry accordingly.
Regards,
Shailesh Verma

Screen Variants SHD0 ?

Hi ,
We have upgraded the system . We have done some changes the to the screen before upgrade.
Now i have the Screen variants. After the upgrade they are reseted to original. So i now to change the screen variants.
Where i can the screen variants ..and where can i see the methods of screen variants...
Method GET_SCREENVARIANT_SC
· Worklist for Sourcing: Screen variant BBP_SOCO_WL
Method GET_SCREENVARIANT_SOCO
· Work area in Sourcing: Screen variant BBP_SOCO_GA
Method GET_SCREENVARIANT_SOCO.
Please help ...

i got the methods

How to change existing variants

Hi All
I have made changes in the selection screen of a report. Now if I use any of the existing variant I get the error 'Variant <> of program <> is not the current version'.
How to adjust the existing variants.
Amol

Hi
For one particluar variant I am getting the Dump.
I have following error analysis given in Dump.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
was neither
caught nor passed along using a RAISING clause, in the procedure
"%_IMPORT_VARI_CLNT" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When importing the object "S_RPMAX", the component no. 3 in the
dataset has a different type from the corresponding component
of the target object in the program "ZARS".
The data type is "N" in the dataset, but "C" in the program.
Now if I am correct this means value in Variant is 'N' and in Program is C. Thats why dump is occurring . Then how do I change values in variant. because If I try to change it using SE38 . it gives the same Dump.

Changing the column position & width using Screen Variant..

Hi Experts,
    Iam trying to change the column position and width for the standard transaction (eg. FB60 or VA02) using the transaction code SHD0 (Transaction and Screen Variant).
    Iam able to create and save the transaction and screen variant and i could see the check box options for table control like
    a. Auto Column Position
    b. Auto Column Width
     I tried checking and unchecking both the check boxes but iam unable to modify / maintain the column position and width.
     Please guide me in changing the column position and width.
   Thanks in Advance.

Hi Mudit,
Kindly go through this link below:
http://help.sap.com/saphelp_nw04/Helpdata/EN/9f/dbac0b35c111d1829f0000e829fbfe/content.htm
Hope it helps you
Regrds
Mansi

Change column sequence for screen variant FB50

Hi Experts,
I am able to hide unwanted fields in screen variant for items for tcode fb50 by creating screen variant and i also selected adopt column sequence check box.when i go tcode shd0 and clicked screen variant that i already created and click with processing button i can get FB50 tcode screen there i can change column sequence by drag and drop .is it correct way to change the column sequence? but i am unaware how to save the changes i made.
Please let me know how to proceed to change the column sequence and save it.
Thanks&Regards,
narasimha.

Hi Faheem,
After changing the column sequence i clicked configuration button and click save button and again clicked Configuration and selected Administrative button there i can see the column sequence change and clicked activate button .now if i close and reopen the transaction my column sequence is same with out changes that i made .
you asked me to save the changes where i can do exactly ? Could you please tell in briefway from scratch so that i can trace where i done mistake.
Thanking you in advance.
Regards,
narasimha.

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
This BADI as you can see by name is for Screen Variants.
BBP_SCREENVARIANT in this case.
Please read the following documentation to get the clear difference
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

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 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 when assigned to transaction variant in SHd0

Dear All,
User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
Thanks in advance
Komal

Hi,
Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
Once done and saved, you can see all the screens variants in the transaction variant.
Use the Change WITH PROCESSING OPTION.
Hope this solves your problem
Regards
Shiva

I have the same case with you an iPad Air in dead pixel or speckle silver dust on screen. It is been 3 months I bought in Avant Abenson in Greenbelt Makati Philippines. Today I decided to change my screen protector film but the speckle dust on the screen

Speckles dust on the screen and it cannot be removed today when I decided to change the screen protector film and noticed is not my fault it is a factory defect on screen it is either dead pixel or speckle dust on screen they are so many said and experience I have read. So I need the replacement a new one for that dismayed screen on my iPad Air. I bought this 3 months ago in Avant Abenson at Greenbelt Makati Philippines. I need the replacement for tomorrow I will go to the store I bought. I love apple products but they need to replace and make go round to improve some defects and cannot be more escalate with this issue of the many of patronizing your products. It is sometimes irritating to the eyes and seen dirt on the screen. Thank you apple customer service to bringing up my complaints and a replacement for tomorrow's to inform the store I bought and advise them here in the Philippines to facilitate in regards to this matter.

I wanted to buy an ipad air to replace my ipad 2 but the one I wanted was (luckily) sold out.
Yesterday I tested the air from a collegue and I noticed the screen was SUBSTANTIALLY less sensitive than the screen of my ipad 2 when using my stylus.
I use Stylus R US especially for I annotate and with the air this did not work well at all... Half of the time there was no contact registered so underying certain parts of the text was a disaster...
Just working with the finger all whent OK... Just fear that another app I use a lot (notes +) will have same problem.
On the Ipad 4 also retina all goes *** smooth as on my ipad 2...
Is this a fault of a specific ipad air series? Or is this normal?? If it is I think this is truelly a huge flaw and I cannot see how not manny people using the ipad for notetaking etc did not notice this...

Custom Data Entry Profie screen variant needed

hi All,
Our client was asking for making modification to the Order the columns currently being displayed for CAT2 trx.
Ex:
For profile 1, the client wants the column display in the following order:
Receiver WBS Element - Network - Actvity type - CO Area - Rec. CCtr
For Data entry profile 2, the client wants the column display in the following order, and doesn't want WBS Element to be displayed:
CO Area - Rec. CCtr - Network - Actvity type
I have searched if there are any screen variant options available, but not of much help. This is bit urgent, so awaiting your replies.
-thnx

Sreekanth,
Thank you for responding. I am in 'Data Entry view' (CAT2 trx), and, I do see a small icon with 3bars on top right hand corner. When I click on it & on 'Administrator' button, I see the 'Position' column vaues grayed out. I have tried using SHD0 for CAT2, and it wont work either. However, it is working just fine for MIRO trx.
Q-1: Can you please guide which 'Authorization' under SU21 -> HR I shall check in order to be able to change the layout?.
Q-2: I also see in Pg. 58 in http://help.sap.com/printdocu/core/print46c/en/data/pdf/CATS/CATS.pdf, the other option listed as -> worklist [Extern]. Do you have any idea on how I can track through this option?.
-thanks

Selection Screen Variant (optionally default) -I dont think it's possible!?

I have spent a lot of time looking at this issue - researching forums/sap help/on the system - so any help appreciated...
On the selection screen (for tx me59n) is it actually possible for users to set a variant as default on the selection screen? It's actually that I want "Test Run" to be defaulted.
This is the ideal scenario:
- The selection criteria variant is created centrally (or even individually by the user)
- The user can then optionally set this variant as their default selection criteria for the transaction
- Next time the user runs the transaction, the defualt variant is used
What I do not want is:
- User having to select the variant each time they run the transaction
- The variant always being default (it should only be default when user decides they want it as such)
Any ideas? I can't see that it's possible....?
thanks in advance,
Matt

I've been trying SHD0 alot, but doesnt seem to work - again, i've spent time reading and trying it out but with no luck.
This is how I'm doing it to try to default "Test Run" checkbox for ME59n
- Run transaction SHD0
- Input "ZDefault" into Transaction Variant field
- Click create
- ME59n loads
- I tick "Test Run" (which is what I want defaulting for the transaction)
- Click save
- It prompts me to create screen variant
- I input ZTEST_VARIANT and click save
- I get a pop-up box which I enter ZTEST_VARIANT to name field but dont make any other changes
- Get message saying ZTEST_VARIANT saved
- Click back to Transaction Variant screen
- Save it as a local object
- Get message saying "Trans Variant and Screen Variant Saved"
- Click back to initial SHD0 screen
- Click TEST to try it out.
- ME59n loads, but "Test Run" is not checked - the variant appears not to have been loaded at all.
I run ME59n independently and still nothing seems to get loaded when I run the transaction. Although the new screen variant is availbale in the variant list, which if I select it it works perfectly. But I want make it default??? How do I do it?
Any ideas what i'm missing?
Usually I can figure these things out pretty quickly, but this one has me stumped!
thanks
Matt

Time series inconsistency due to change in Fiscal variant/Storage bucket

Hi All,
We got into the situation where running time series consistency check on a DP planning area fails with the message pointing to, 'changes to Fiscal variant'. We are unable to track any changes to the fiscal variant though there is a possibility that storage bucket horizon could have been changed. Is there a way to correct/synch this by running a report?
We are trying to avoid re-initialization here, though this is an option, for the obvious reasons to backup the data in production. Is there an alternative solution to fix this inconsistency?
Cheers!

Dear Ashok,
You should never change a FYV when this FYV is used in a storage
bucket profile which is used in a planning area and if time series
objects are already created. It is no problem to maintain the FYV for
an additional time range, but changes and deletion of periods should
never be made if the FYV is actively used. You should not
change existing periods. If you want to make any changes to buckets
in your FYV or delete buckets, you should always make a COMPLETE
backup of ALL your data from the planning area into an InfoCube,
then delete the time series objects for the planning area (and with
this all the data in liveCache) and then change the FYV. After that,
you can create time series objects again and reload the data from the
Backup-InfoCube into the planning area. If you do these steps, you
will not risk to loose any data. The data in the InfoCube will be
the backup you can reload.
As some processes check the FYV some time before and after it is used,
it is very recommendable to maintain the FYV at least 2 - 3 years in
the past and in the future. E.g. if you create time series objects up
from 2001 you should maintain your FYV at least back to 1999 and if you
create time series objects until 2006, you should maintain your FYV
at least until 2008. It might be that you never experience problems if
you do not maintain the FYV in this time range, but some processes do
additional checks and then it can come to problems
Regards,
Rakesh

Change existing screen variants of certain z t-code.

Similar Messages

Maybe you are looking for