Problem in creating transaction variant

Hi all,
I am trying to create transaction variant for F- 41 transaction . it's giving an error message .
Variants are possible only for dialog transactions.
Message no. MS417
Diagnosis
You cannot create variants for variant or parameter transactions.
Procedure
Variant transaction: Adjust the variant
Parameter transaction: Adjust the parameter(s)
i need to disable the filed 'document type' .
Guide me.
Regards,
Ravi

Hi,
You can copied into SAP standard program to Zprogram and then use the Loop at screen....Endloop to disable the Documnet type.
FYI...If you go for F.14 transaction there you find Sytesm----> status .. there you will find SAP standard program. Make a copy to Zprogarm and try to disable it.
Regards
Thiru

Similar Messages

Problem while creating transaction variant for transaction KCH1.

Hi All,
I am trying to create transaction variant for KCH1 transaction code.
I am able to deactivate standard navigation options Change, Copy, Delete for the menu called "Group" in the main screen.
But I am unable to disable the standard navigation options for the menu u201CGroupu201D in the second screen where we enter possible profit center values in hierarchal structure. I want to deactivate u201COther Groupu201D , u201CChangeu201D and u201CCopyu201D In the hierarchy screen.
Please advice.
Thanks & Regards,
Padmasri

Hi,
As I have already mentioned in my previous message, I am able to deactivate standard menu options by using Menu functions for Main screen where we provide Profit center group value which needs to be created. For this screen I have passed GUID START_CO and was able to deactivate required options. But for the Hirarchial screen, I am unable to deactivate some of the menu options. In menu functions I have passed LIST_01(GUID for the screen) and deactivated the options but was not reflecting which testing the transaction variant.
Anyone please let me know if transaction variant work for my scenario. If no please suggest a solution.
Thanks & Regards,
Pratima

No fields displayed while creating transaction variant

Hi,
I am trying to create a transaction variant via SHD0 for the tcode 'VF31'. I enter the ZVF31as transaction variant in the transaction variants tab and click on the create button. It takes me to the VF31 screen. From there when I click on Back or Exit button, it takes me to the change transaction variant screen. Although I did get the fileds listed the first time, I am unable to get the same subsequently. Is this a GUI problem? Quick response would be much appreciated.
Thanks,
Preethi

Selection variant is possible to VF31. If selection screen is 1000 ( Executable programs) then we cannot create Transaction variant,

How to create t-code for a table and how to create transaction variant???

Hi,
I have created a custom table zsark.
Now my requirement is : I have to create a transaction variant zsark_var for sm30 and table zsark. I have to disable the output of the first screen. I have to assign the transaction variant to the transaction code of table zsark.
Now,
1.     how to create transaction code to a table. Can any one give me the
                staps??
2.     how to create transaction variant for the above requirement???
Thanks & Regards,
Sarkar

Hi
1 Goto SE93 transaction
2 Choose 5th option Transaction with parameters
3 Give transaction : SM30, Check Skip Initial Screen Press Enter
4 Goto Bottom left corner, click F4 select viewname, on right hand side give table name
5 Press one more time F4, choose update , mark it X on right side.
6 save the transaction.
Thanks
sandeep
reward if helpful

Error while trying to create Transaction variant for FV60 layout change

Hi Gurus,
I am trying to change the "order/sequence" of FV60 layout (rearranging columns). For which I tried to create Transaction Variant (in sandbox). I keyed in the t-code (FV60) and gave a variant name in the field for Transaction variant. But it gives me a wierd error - "Enter transaction code". Has anybody come across this before? This is enhancement pack 7 so the config button is not available.

Thanks Ravi. I went through the note and did exactly the same. But the two check boxes displayed in the note for "Adopt column sequence" and "Adopt column width" is not displayed in my screen!!! Screen shot attached.

Create transaction variant of mm01 - can't fix material type

Hi,
I am trying to create two transaction variants for MM01 called ZM0R and ZM0F for raw and finished materials respectively.
I have created them and all the fields I want as Required are working.
However, I want the material type to default in as raw for ZMOR and as finished goods for ZMOF. I have ticked "with content" and "required" but it is not working. Whatever material type was last used in MM01 still comes in.
I have also tried creating a copy of MM01 using Se93 to see if I can get it to work this way but when I test it, I get a message Sap Transaction control and can't seem to get past that.
Any ideas?
Thanks

Hi Jurgen,
worked a treat, thanks!. I have another related problem...my backflush field in MRP2 is not appearing. I have checked the field groups and it is there, group 74, for the material type and marked as Optional. Is there somewhere else this can be hidden?

How to create Transaction Variant

Hi all,
I have a requirement like this
I need to create a transaction variant for the table CEPCT, for the transaction SE16 and want to disable or invisible CREATE and CHANGE options in that
Can any one help me out in this requirement
Regards
Srinivas

Hi,
Recording a Transaction Variant
Transactions variant are recorded through transaction SHD0.
   1. Enter the transaction code you want to record u2013 here BP, and press enter
   2. Enter a name for your transaction variant u2013 here Z_BP_NO_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y.
   3. Push Create
You have now called transaction BP in recording mode.
   1. When you push the exit button you will get the following popup
   2. Enter a name for the screen variant u2013 e.g. Z_BP_NO_PERSON,
   3. Press the deactivate menu function, and you get the following popup.
In this Popup you can deactivate menu functions.
   1. Open the Menu Bar à Business Partner à Create
Position the cursor on u201CSCREEN_1000_CRE_PERS Personu201D
   2. And push the deactivate button.
   3. Push enter
   4. And u201CExit and Saveu201D
   5..Save the Transaction Variant.
Thanks,
NNR.

How to create Transaction Variant for T code F-30

Hi
I want to create a Transaction variant for T code F-30, so that user can't change the currency field and put any value in rate. Currency should be always in USD.
Any input will be heighly appriciated.
Regards
Shiv

Hi,
In that case you can use transaction SHD0 to create a transaction variant for F-30 with its screen variant for screen# 122. And you also want to creat a so called Variant Transaction Z-something for F-30 using the mentioned transaction variant. You restrict users to use that Z-something. For other unrestricted process, the system will still cal F-30. Here is the documentation:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/67/232037ebf1cc09e10000009b38f889/content.htm
Regards

Problem with Trasnporting Transaction Variant

Hi,
I created a transaction variant in development system. Now I need to transport the transaction variant to Quality. I have done that. But in quality system, the variant is not picking up when i run the transaction.
I made it as standard variant. I tried with both Cross client and Client specific transaction variants. But it didn't work at all in Quality system.
Can anybody guide me please where I am missing the flow...?
Thanks,
Sankar.

Guys,
Any clues please...
Thanks,
Sankar.

Problem with transaction variant

Hi Gurus,
I want to create transaction variant for XD01 transaction and make district field mandatory.
I have done it using transaction SHD0 and its showing effects when i test it from SHD0.
But I cant see its effect in actual transaction XD01.
Please guide.
Thanks in advance,
Supriya.

Hi,
The transaction variant created by SHD0 when activated will change the display of tcode SM37, irrespective of whether it is called directly or from a Z program. If you are calling SM37 from Z program, try
SUBMIT SAPLBTCH VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar_tab AND RETURN.

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

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,
creating Transaction Variants
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

Creating a variant transaction

Hi,
Im trying to create the above in SE93. Im calling it Z_SWWL and its calling transaction SWWL, which contains variants. But its not finding any 'transaction variant' to choose from!?
Any ideas?
Thanks,
Dave

Hi
goto SHD0 tcode and create a Transaction variant with screen variants for a dialog Transaction
then assign that Transaction variant in SE93 by creating a variant transaction code
see the doc
we can create Transaction Variants Using SHD0 Transaction.
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
see the links
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1213076,00.html
Re: shd0 transaction
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1213076,00.html
Re: shd0 transaction
Regards
Anji

Default the transaction variant created in SHD0 for MIRO

Hi,
We have a requirement where the subsequent Dr/Cr field in MIRO must be invisible.
Used SHD0 and created transaction variant and activated the same in standard variant.
1. The variant is showing up in MIRO but it is not defaulting.
2. How can we transport the same to different clients as transport request is not populated on saving.(Saved as local object).
Appreciate if you can please guide me.
Thank you

Hi:
In SHD0 , have you activated the z screen variant to the transaction variant you created for MIRO....
Regards

Transaction variant durign creation of sales order.

I have a scenario Sale area is R001/10/10 and is applicable for all the customer in all india.
Now the requirement is to incase of sell order creation to only the customers at UP it will be made mandatory to put cheque number in the sales order otherwise the order will not solved.
The same will be applicable only for up customer not to other customers.
Now the problem is if i want to added some field in incompletion procedure and assign to the order type it will not solve my problem.
Becasue OR is assign to R001/10/10 and sell happens from hyderabad, bangalore as well as up also. and this control only require in case of sell to up customers only. If i will assign the incomplition procedure to order type it will be applicable to all.
So it was suggested by anybody to creat transaction variant during sales order creation. Can anybody tell me the way to creat or any other suggestions.
The right answar will be rewarded.
Thanks.
Laxmikanta Das.
09958119889

Hi
If you donot find any other alternative, you can finally go for using the Userexit. When the sales order is created and before saving the document, the system checks for the field -State/Region etc., and if the value is UP then it checks for the Check Number in that corresponding field. You have to mention the systems reaction(warning or error) if there is no value in that field.
Thanks,
Ravi

Problem in creating transaction variant

Similar Messages

Maybe you are looking for