Transaction variant shdo

hi,
i trying to create a variant in SHDO TCODE for sales order -to hide reason for rejection & ordering party tabs
but after assigning variant to sales doc type if i goto sales order ************ ************ are coming
in few fields.
Pl suggest how we can avoid this

hi,
pl suggest how to actvate
but i've assigned trans variant to sales doc type.
in va01 reason for rejection tab is hidden as required but in some fields astrix *************** is coming
pl suggest

Similar Messages

Need help in defining the Transaction Variant using MM02

Hi Experts,
I had a requirement that I need to disable the <b>Purchase order Text</b> tab in MM02 T-code,I tried using Transaction Variant(SHDO) ,but I unable to disable the PO text Custom Control.Iff you have any info Please share it with me on [email protected]
Apriciated your contributions by Assinging the points.
Thanks,
Sridhar.

Hi Nani,
The transaction used to create transaction variant is SHD0.
Using this you can change the screens, for example is you want certain fields to get a default value in XD03 / MM03 etc you can do so with the help of transaction variants.
Also you can go thru this links for more help .... please go thru and I believe that you problem will be solved....
Check the following threads:
Re: How to create a transaction variant
Transaction variant
Regards,
Jayant
Please award if helpful
Message was edited by:
JAYANT KUMAR

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 for Transaction FV60 (Parked AP Invoice)

Hi All:
I have been successful in creating a transaction variant for transaction code FV60 (Park AP Invoice). My objective was to get rid of the post and save as completed buttons on the FV60 screen. But when I simulate the document, the post and save as completed buttons appear again and I have been unsuccessful in getting rid of these and deactivating/hiding them.
Can anyone please help me or has anyone done this before?
you help is very appreciated
thanks
Brian

Hi you can hide the button as follows;
While doing SHDO Variant Creation , in the confirm screen entries dialog press Menu Functions button and in the dialog expand Function setting tree and select BU (POST) and press Deactivate button (or F2 key) then select PBBP(Save as completed) and press F2 again.
Now save the variant and activate it.
Now check the tcode, those two buttons will be hidden.
This will solve your problem.
Regards
Karthik D

Transaction variant - can all fields be gryed out?

Hi,
I want to build a wraparound for VT02n, I want all the fields to be greyed out except for one field and the save button. Can I do this using trasnaction varinats?
Thanks,
Krishna

We had this requirement in one of my previous project and we were able to create a transaction variant using SHD0 to populate decimal format, logon language and default printer name like LOCL or FRONTEND. Only in case of dates where we needed MM/DD/YYYY we had to change the parameter zcsa/moddatfm (Parameter for Default date format when creating users with transactions SU01).
Creating a transaction variant is pretty easy and you can google it or search in SDN. Basically it is something like this ..
1. executing t-code SHD0,
2. entering SU01 in Transaction code field,
3. entering some transaction variant name say Z_SU01 etc.
4. clicking on create
5. actually creating a test id with the default values you need like putting the user id name and last name and password
6. also hitting enter /continue till you are able to reach/click Default tab
7. here you put values for ex lang - as EN, decimal notation as 1,2345.67, output device as LOCL etc and then when u see screen entries - check mark on W.content for logon language, decimal notation and output device.
8. Save it and then go back ..then again save it
9. Do not forget to activate your transaction variant. To do so click on Standard variant tab -> Standard variant -> you will see activate button.
Next time you create a user id - you will see these default values. Only for dates you need to set the paramter mentioned above from value 1 to 2.
If you still have issue take help from some abapers/developers who are aware of SHDO functionality.

TRANSACTION VARIANT

Dear All,
I am facing a problem while doing the transaction variant. It is as follows -
With the T.Code SHD0, i started creating a transaction variant and named as ZMM01 for the transaction MM01.
After clicking the create(F5), it went to the MM01 transaction for recording. Here i wanted to give some default inputs in the fields Industry sector and Material type, i gave my default values and pressed enter, then "Confirm screen entries" screen popped up. Here i selected(marked) required check boxes and clicked "Exit and Save". It went to another screen where i gave "Screen variant short description" and when i clicked on save, "Create Object Directory Entry" screen popped up.
What exactly should i do now?
When i tried to save by clicking on save button, system is giving me a message "Specify the package or flag it as a local object"
"Message no is TR742".
BUT.....
When i clicked the "Local Object" tab which is next to "Save" button, system is asking me to Assign a package" and in the package field the system is giving the value "$TMP" by default and when i tried to save it OR click "Local object" again, system is giving me an error message "Test objects cannot be created in foreign namespaces", Message no. TO131.
Pl guide me what exactly i have to do at this stage( How/Procedure to save).
Thanks & Regards,

Hi ,
Ensure that all the variants you have created start with Z like screen variant , transaction variant .
The system throws this message when you use other name space which is not allowed .
Regards,
Hari.

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

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

Transaction variant not working

Hey,
I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
The reconstruction steps are as follows:
SHD0 -
Creation of transaction variant - with processing.
Activating it.
Appreciate a quick response. Thanks in advance.
Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
[email protected]
Regards,
Z

hi,
just check out the following pre-requisites if you have followed them or not:
You can assign various transaction variants to individual sales document types.
With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
Preassigning fields with values
Fading out and changing input availability for fields
Fading out entire screens
In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
Activities
You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
regards,
Siddharth.

Authorization issue on SHD0 transaction variant in R/3

Hi,
Can anyone help me on the below issue?
Created a transaction variant ZME31K using SHD0 on R/3 system with the base transaction ME31K.
And created a transaction ZME31K for the above transaction variant.
Created one ID which has access only to transaction ZME31K.
But when tried to create contract using ZME31K, it allows to create the contract, but ended up with message "You are not authorized to use ME31K".
Anyone faced similar issue before? how this can be resolved? As per the busniess requirement, they can provide access only to the transaction variant for the user and they will not be assigned to ME31K.
-Thanks,

> We are doing an Upgrade assessment wherein at R/3 side, the system is being upgraded from 4.6 to ECC 6.0.
> I wanted to know the impact the Change in Transactions at R/3 side.. namely transactions..
> AS02, CT02, F-02, F-41, F-49, FB01 would have on BW.
What do you mean? I don't get your question. What impact should those transaction have on BI?
Markus

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

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

Edit drop down list in SHD0(transaction variant)

Hello all,
How can we control the values displayed in drop doen list using transaction variant? i am using SHD0 to create a transaction variant and want only few values to be dispayed in drop down list instead of all the values in orignal transaction.
Thanks
Arjun

As far as I konw, you can not.
You can edit the properties (Visible/Invisible, etc ) but not restrict the values originally displayed.
Regards

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.

Transaction variant shdo

Similar Messages

Maybe you are looking for