Shd0 - variant transaction

Hi !
I have to create a variant transaction for Tcode ME23N.
I need to hide part of the tabs of the tabstrip.
At Shd0 screen i check the "Do not Display screen" checkbox and saved and exit the screen i want to hide, however it doesn't"t work and despite the checkbox check the tabs i want to hide are shown.
Please tell me how do i have to do the task of hiding the tabs ? please answer in details.
thanks
moshe

Hi SOLMAN*,
search in this FORUM ,u will get it .
Otherwise See the Documentation in that Tcode SHD0
Regards
Prabhu

Similar Messages

SHD0 Maintain Screen Variant in Variant Transaction

Hi all,
I would like to know how tom maintain screen variant in variant transaction ?
I created a variant of MM01 using SHD0, the recording gived me as much screen variant as screen maintained during record session, this works perfectly.
The problem is when I want to maintain an already created screen variant : I try to hide Basic Data View fields that was not initally hidden. I do change the field "invisible" for the basic date fileds I would like to hide. I save the screen variant changes.
It seems to work but when I try to test the transaction variant, hidden fields remain visibles ...
do you have an idea of that problem ?
regards
Morgan

Hi,
thanks for answer but unfortunately, it won't help.
I already found how to record a transaction, create a transaction variant and associated screen variants and it works. The thing that doesn't works is, after all these steps, when I try to maintain the screen variant because I have to do change something.
IN my case, I created the screen variant with some visible fields on basic Views of material master but now, I want to change it because some fields has to be invisible.
So I go to SHD0 and maintain screen variant. Check the value "unvisible" for required fileds and save.
Next, I launch transaction variants where the screen variants was used but the fields remain visible ...

Shd0 - creating a variant transaction

Hi !
I am new in creating a variant transaction.
i need to change the default of transaction PKBC from the radio button - Auto to radio button- Empty.
please tell me how to this ?
Also i will be glade to get material about this subject.
thanks
Moshe

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).
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)
Variant Transaction
http://help.sap.com/saphelp_nw04/helpdata/en/7d/f63a0a015111d396480000e82de14a/content.htm

SHD0 transaction-how to restrict the variant transaction to specified users

I have created a variant transaction for MM02 wherein am disabling a field .I want this field to be disabled only for certain users.The variant transaction which I created affects all users.So,for everyone the field is grayed out.How to restrict this for specified users???

Hello,
Try to look an exit for that transaction, either user exit or badi, then try to disable the field doing a LOOP AT SCREEN, but first you should have the restricted users in a Z table, or by cheking the profiles for each user..
Another way to do it is trying to do it the profiles customization, maybe you can do it that way.
Cheers!!
Dont forget to reward.
Gabriel P.

Shd0 for transaction ea20

I am trying to make a transaction variant for transaction ea20.
EA20 is an ISU-CCS transaction which reverses bills.
Normally when I create a transaction variant - I go to SHD0 - enter the transaction, give a name of the transaction variant - and click create.
It goes to the transaction. I hit enter - and it goes to another screen which allows me to hide - or default certain fields. Then I save - and go on.
On transaction EA20 - I go to SHD0 - enter EA20, a transaction variant name - and click create. When I click enter - nothing happens. It stays on the same screen. If I click back, cancel or save - it shows me the wrong screen to modify. Instead of the EA20 screen - it shows me the screens to create variants.
I have read the help on SHD0 where some transactions cannot be used in transaction variants - but I don't see where this transaction falls into those categories.
Has anyone else had a problem with creating a transaction variant for a certain transaction? And if so - how did you get around it? Or what did you do to fix the problem?
Thanks for your help.
Scott Overmeyer

Scott,
Follow this process and let me know if you face any problem.
Case one for 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.

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

Variant transaction

Dear all,
I have created several variant transactions (shd0). No problem with that. After that I assign some transaction codes to the created variants. No problems either.
I have created a variant transaction for CO11 and one for MB1B (transfer material to material).
During testing all is working very well, except for...
When the transfer with the variant of MB1B is posted, he returns to the initial MB1B screen! (not the variant screen, where I've hided some fields).
However, after a confirmation with the variant transaction of CO11, SAP returns to the initial variant screen of CO11 (with hided fields).
I would like to obtain the same result for the variant transaction ofMB1B.
Does anyone has a clue?

Hi,
withint standard this is correct the SAP note 46625 question 1 for details.
If you need to change this you need to modifiy the system.
Regards,
Sabine

Can anyone tell the use of variant transaction in real time?

i have done programs using variants .. i would like to know the use of variants in real time..also about
variant transaction parameter transaction..

Whenever u r execution the program, save it. It will ask u to save it as variant. so that u can use this variant for multiple times to execute the program

Problems with variant transaction zme51n

Hi,
I have created a variant transaction zme51n.
But I can only start the transaction when I add the original transaction 'me51n'
in T_Code in profile generator.
Any ideas why?
Thanx for your help in advance.
Thomas

Hallo Rob,
thanx for your help. I think we're on the right track...
Greetings.
Thomas

Assign variant transaction to SD01 tcode

Good morning experts,
I want to create a variant transaction to the std. SAP tcode SD01.
Is it possible to do this?
if Yes then how?
Moderator message: please do some research before asking.
Edited by: Thomas Zloch on Feb 24, 2011 2:14 PM

In case of SD01 , I think most thinks your require should be possible with the favorites and other options in the Area Menu.
Or is your requirement more complex.?
Suzie

Using SHD0 for transaction variants with 4.6C

Hello,
I need to slightly alter the program behind transaction CU60. Initially, I intended to simply copy the original program, edit it slightly, and attach it to a new custom transaction code but this would require copying multiple entire function groups. As we are upgrading to ECC 6.0 shortly, this approach is not wise as it involves some potentially big headaches in the near future when we upgrade.
My question is: Is there a way to assign some users a modified version of CU60 that has no "maintain" ability in the toolbar/menubar?
*Note: I can accomplish this using variant groups in shd0 in ECC 6.0 only but in the 4.6C version it appears to be "all or nothing". i.e. create a standard system-wide variant that applies to everyone, or none at all. I need this to apply to only some users.
Please help if you can.
Thanks,
Matt

Rather than taking copies of SAP code, I feel that there is a time-and-place for considering "repairs" to meet specific requirements - and enhancing the logic this way means that any subsequent support pack changes to standard SAP are still applied to the program, whereas a copy will soon start to lag behind... of course you should always comment the mod well for the next ABAPer who comes along, and maybe think about keeping a register of these too with associated doco as it can be very hard for a programmer in 3 years time to understand the original intent of changes and what other objects were affected too.
Post upgrade you can look to using the new enhancement framework to apply the same logic / validation (if a suitable standard exit doesn't exist in ECC6).
Jonathan

How to assigned SHD0 Variants to user?

Dear All,
    I want to use SHD0 to hide the u2018DO not Display Valuesu2019 in MB52 .Now I used SHD0 to do it.
My step is:
1.     Created Transaction Variants:ZMB52_T and Screen Variants ZMB52_S
2.     Created Tcode: ZMB52, Created Variant Groups Group Name: ZMB52.
3.     Assign the user ,Set Proposal the user
Now I run ZMB52 that found all users have worked it .not the special user.
How can do it
Thanks

Hi sun ,
Transaction variants can only be used with dialog transactions.
so in this case its not possible to create a transaction variant for mb52 .
Regards ,
Rajesh

MB1B: Variant transaction is not showing the message of document creation

Dear MM EXPERTS n GURUS,
When we create any document using T-Code MB1B, on successful posting it gives a message: Message no. M7060, Document 4900556951 has been saved and is stored in the database.
Now, we have created an variant of this Transaction (ZMB1B) and assigned this Z-Transaction to the user. Original Transaction (MB1B), has been blocked for that user, because - user should use only ZMB1B.
Problem is that after saving the document in Z-Transaction, user come out to main screen (SAP EASY ACCESS Screen) with a message You are not authorized to use transaction MB1B Message no. S#077
While document has been saved in database.
Why it is not showing the message - Message no. M7060, Document 4900556951 has been saved and is stored in the database.
Thanks in advance.
DSC

Dear GURUS n EXPERTS,
As I have mentioned in my previous thread - After creation of Variant if I block or not assigned the original T-Code i.e. MB1B, system gives message Message no. S#077 You are not authorized to use T-Code MB1B.
If I don't block the or assigned the Original T-code, there is chance to user will use original T-Code instead of variant.
How can we solve this problem.
Please advice.
With thanks,
DSC

Variant transaction ZMM42 for one view: Logistics: Distribution Center

Hi All!
I have to create for tCode MM42 a variant (ZMM42) and authorize some users only for ZMM42 (in order to modify only Storage data).
I read about the solution of Ralf Nellesen in thread How create a custom profile on SU02, with only one view? .
But I can't create an entry for my transaction in OMT3E in order that the new screen sequence will be called for transaction ZMM42. I can't create this entry because I don't know how to create a new Transaction screen reference (table T130M). If I use tCode SM30 for table VCM_T130M I can only modify the entries and I can't add a new entry for:
ZMM42 Change Material & 04
(04 is a new transaction screen reference)
Can anybody help me? I'm getting stuck...
Regards.
Florina

Hi,
To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
Regards,
Ram

Authorization message problem with variant transaction

Hello everybody, I have created a transaction variant ZMM01 from transaction MM01. In the role I specified this new transación (ZMM01) in S-TCODE.
I can create the material but at the end, instead of the message "material zzz created" I received the message "you are not authorised to MM01".
Does anybody know how to solve this problem?
Thanks in advance.
Maria

Thanks for your quick answer but if I run SU53 the result is the following:
Object class AAAB Cross-application Authorization Objects
Authorization Obj. S_TCODE Transaction Code Check at Transactio Start
Authorization Field TCD Codi de transacció MM01.
If I include this I allow the user to access transction MM01, but I don´t want to.

Shd0 - variant transaction

Similar Messages

Maybe you are looking for