Vf01 screen transaction variant

Hi,
We created Screen transaction variant for VF01 transaction to make
Billing date field of intial screen in display mode through the
transaction code SHD0.
It working fine in Development,Testing servers. But when we transport
it to production it is not working.
But when i go to the test mode it is working fine. When i go directly
to the transaction VF01 it is not displaying the Billing Date field in
display mode.

Please check if all relevant Customizing Request & Workbench Request have been inported to production server. Probably some request is skiped by oversight.
Regards,
Rajesh Banka

Similar Messages

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

Problems with SKIP FIRST Screen when calling a transaction variant

Hi,
I have a transaction variant of VA02 that suppresses the display of the pricing button on the conditions screen. I have created a variant transaction for called ZA02 which calls this variant of VA02.
In my program I have coded the following :-
      SET PARAMETER ID 'AUN' FIELD VBELN.
      SET PARAMETER ID 'VPO' FIELD POSNR.
      CALL TRANSACTION 'ZA02' AND SKIP FIRST SCREEN.
I would have expected the program to display the second screen of VA02 but it displays the first screen and when I hit return key the second screen is then displayed.
I don't think I need VPO setting but when I code
      SET PARAMETER ID 'AUN' FIELD VBELN.
      SET PARAMETER ID 'VPO' FIELD POSNR.
      CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
VA02's second screen is displayed
Any help as to how to Skip this first screen with ZA02 would be greatly appreciated
Thanks
Rous

Yes you are right Reg thanks for that.
But it appears that VA02 doesn't require it setting anyway. I changed the PID to APO and indeed I've even commented the line out, but my program goes to the second screen when calling VA02 but stays on the first screen when calling ZA02 .

Transaction variant for Goods Issue going back to MB1A transaction screen

Hello,
I have created a transaction variant ZMB1A for Goods issue.
When the goods issue transaction completed by using ZMB1A system again going back to the initial screen of MB1A. (Since it is the base of MB1A)
Here the issue is everytime user had to enter the ZMB1A transaction. (for example if the user wants to issue material for different plants).
Please suggest any suitable method to avoid the above multiple t code execution.
Regards
Rifaie M

Hi,
In SHD0, do the complete processing of Transaction MB1A during creation of Transaction Variant "ZMB1A" till posting of the Material document.
To create a new T-Code as ZMB1A, go to Transaction SE93 and here enter Transaction Code as ZMB1A and Click Create button. Now enter Short text of Transaction and select option "Transaction with Variant (Variant transaction)" and press enter.
Here enter following;
Transaction MB1A
Transaction variant ZMB1A
Activate "Cross-client"
Select Professional User Transaction
Activate SAP GUI for HTML
Activate SAP GUI for Java
Activate SAP GUI for Windows
Now Click SAVE button.
Now you can start using Transaction ZMB1A which will call Transaction Variant ZMB1A.

Creating a transaction variant doesn't catch the selection screen

Hi,
I am trying to create a transaction variant for RERAPP transaction, which calls the report RFRERAPP on selection screen 1000.
I have used SHD0, specifying the t. code and a name for a transaction variant, then pressed the "Create" button. the selection screen is displayed, I enter the relevant values for the transaction, and press enter. the system prompts me to create some screen variants, but none of them have fields listed, and none of them is for the screen 1000.
SAP Release 600.
Any hint on the reason behind this behavior?
I found another related, unanswered [topic|Transaction Variant for a standard report without transaction code;

Hi,
I have faced similar problem..
Here is the work around.. Might be useful for you..
1. Create Selection screen variant for report (Modify selection screen 1000 for display/hide in variant maintaince)
2. Then create "parameter Transaction" with report on Transaction START_REPORT
D_SREPOVARI-REPORT = <Your Report Name>
D_SREPOVARI-VARIANT = <Newly created variant>
Nag
Edited by: Naga Mohan Kummara on Dec 31, 2009 10:46 AM
Edited by: Naga Mohan Kummara on Dec 31, 2009 10:49 AM

Problem in Transaction Variant - hide screen

Hi All,
Iam creating a transaction variant for the tcode IE02.
There are 4 tabs in which i need the first tab( say A ) to be hidden completely so that the second tab      ( say B)gets displayed as the first tab. I have hidden the tab A and the fields in that tab.
When I execute the transaction variant,Iam able to see a blank screen under the B tab.
When I go to some other tab and come back again to B tab, Iam able to see the fields in the B tab.
Can anyone tell me why is it showing a blank screen as the first display? I should be able to see the corresponding fields in the B tab in the first hit.
Thanks in advance.
Guru.

Hi Guru,
           I hope in the PAI section of that transaction you need to do the coding for PAI of TAB B is clicked. So that all the fields of that TAB will be activated.
           In your case first it is blank and when you are doing it second time, automatically PAI of TAB B is satisfied and you are able to see the fields of TAB B.
           Hope this is helpful.
Regards
Sravan

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

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.

Transaction variant vs screen variant

Hi.
Created a transaction variant. The variant has two screen variants. (for VA01). one for the main screen, and one for the sales overview screen.
If I click test for the screen variant, it is working fine as expected.
But if I click the test for the transaction variant, only screen 1 is working fine. Screen 2 is not. Instead it is showing the standard sap screen.
Do we activate the screen variants?
Thanks,

HI gemma deriada,
Check if you maintain only initial screen then the remaining standards will only trigger.
Regards,
Madhu.

SHD0-Transaction Variant not correctly hiding screens from tabstrip control

Hello All,
I have created a transaction variant for transaction PPDPIM. It is my intention to hide all tabs on the second screen of the transaction except for one. This is working. However, I find that my results are as follows:
1. The tab I have left as visible is, in fact, visible. All others are invisible. This is good and what I want.
2. For the one visible tab, the subscreen contains the structure/information found on the DEFAULT tab (which is not the same as the chosen visible tab). This is bad.
It would seem that somewhere in the application the default tab is being set and somehow overriding the transaction variant. Has anyone found a solution to this type of problem?
Thank you.

I have used the "Invisible" checkbox on the subscreen screen variant as the only configuration. I marked this check box for 5 of the 6 tabs with outcome as outlined in my first message.
If I include the "default" screen (giving me two visible screens) then both screens display properly. This does not seem consistent.
Has anyone had a similar problem who can give me some constructive suggestions?
Thanks

SHDO-how to create transactional ,screen , standard variants for a t code..

hi experts,,,,,
1)can u explain the use of it.......
how to create diff type of variants.......
2)......how to give batch number assignment alpha numerically.......
here in the system only numbe\rically available, and i have to assign the batch number internal assignment.........for a particular production order.

Hi,
<b>creating Transaction Variants</b>
Step 1:
Execute transaction SHD0 and create a Transaction Variant against the original transaction.
Step 2:
As soon as you press the create button, the original screen of the transaction will appear. After pressing any button/tab on the screen a menu variant screen will appear. Make sure to check any field or tab or any button you want to disappear from the menu functions. Press the exit and save button when you are sure that no further settings are required on sub-screens (if present). After pressing the exit and save button another menu variant screen will appear. Press the save button here and save as a local object or under any development class.
Step 3:
When you are back on the Transaction Variant (SHD0) screen, press shift+F6 or click the goto menu and press the create variant transaction button. Through this transaction SE93 will be executed. Enter the transaction name you want to create and any other required field and now press the save button.
Step 4:
Now execute the transaction you create through create Transaction Variant and enjoy the results.
Case two for creating Transaction Variants
Step 1:
Create a dialogue transaction through SE93 and enter the program name and screen number of the original transaction you want to make a variant on (e.g., PFCG). Press the save button and check whether the replica transaction (PFCG) has been created successfully by executing it on a new session.
Step 2:
Execute transaction SHD0 to create a Transaction Variant. Specify the transaction name (replica of PFCG) which you have just created and create a Transaction Variant against the replica transaction.
Step 3:
As soon as you press the create button, the original screen of the transaction will appear. After pressing any button/tab on the screen a menu variant screen will appear. Make sure to check any field or tab or any button you want to disappear from the menu functions. Press the exit and save button when you are sure that no further settings are required on sub-screens (if present). After pressing the exit and save button another menu variant screen will appear. Press the save button here and save as a local object or under any development class.
Step 4:
When you are back on the main screen of the SHDO (Transaction Variant) click the edit option on the menu tab and activate Standard Variant. Through this a Standard Variant will be assigned to the transaction specified (replica transaction).
Note: Make sure you activate the Standard Variant against a replica transaction and not on the original one.
Regards
Sudheer

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

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

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

Transaction Variant -Skip first screen of sm30

Hi ,
I have created a transaction variant for a ztransaction using shd0.This is for transaction sm30.
I need to skip the first screen and directly switch to table maintenance screen of the table.
While creating a transaction variant for sm30 I came across the maintain button , but I could not set its value to X.
Any idea how I can do this ?? or how i can directly switch to the maintainance screen?
Regards,
Shital

Hi,
You can make use of teh FM involved in SM30.
See the example code below
PARAMETERS: y_p_lgnm TYPE lgnum.
DATA : y_v_string   TYPE string.
CONSTANTS: y_k_u        TYPE char1   VALUE 'U',
          y_k_x        TYPE char1   VALUE 'X',
          y_k_lgnum    TYPE char7   VALUE 'LGNUM',
          y_k_lgtyp    TYPE char5   VALUE 'LGTYP',
          y_k_eq       TYPE char2   VALUE 'EQ',
          y_k_viewname TYPE tabname VALUE 'YLOMANAGTROL'.
DATA: y_i_seltab TYPE STANDARD TABLE OF vimsellist.
DATA: y_wa_seltab TYPE vimsellist.
START-OF-SELECTION.
*authority check for warehouse number
AUTHORITY-CHECK OBJECT 'L_LGNUM'
             ID y_k_lgnum FIELD y_p_lgnm
             ID y_k_lgtyp FIELD '*'.
IF sy-subrc NE 0.
* user not authorised
   CONCATENATE y_p_lgnm text-003 INTO y_v_string SEPARATED BY space.
   MESSAGE s015(ylo1) WITH text-001
                           sy-uname
                           text-002
                           y_v_string.
ELSE.
*Clear Internal Table
   CLEAR y_i_seltab.
   CLEAR y_wa_seltab.
*passing the selection parameters to the function module
*view_maintenance_call.
   y_wa_seltab-viewfield = y_k_lgnum.
   y_wa_seltab-value     = y_p_lgnm.
   y_wa_seltab-operator = y_k_eq.
APPEND y_wa_seltab TO y_i_seltab.
   CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
     EXPORTING
       action               = y_k_u
       view_name            = y_k_viewname
       show_selection_popup = y_k_x
     TABLES
       dba_sellist          = y_i_seltab.
ENDIF.
Here i am having my Y table 'YLOMANAGTROL'
It has primary key field warehouse number
I am creating a report with a parameter where user will give the warehouse number which he wants to change data for.
Then I check the authoity for this warehouse and then directly call the table in change mode using the FM.
I hope it is useful for you.
Regards,
Ankur Parab

Vf01 screen transaction variant

Similar Messages

Maybe you are looking for