Hiding tab in zmsc2n

[former_member525572]

Hi guys,

My requirement is to copy the msc2n transaction to zmsc2n and need to hide few subscreens in it. I'm new to module pool. Can you please help me how to acheive this requirement.

[Sandra_Rossi]

This can be achieved by creating transaction and screen variants, throught the transaction code SHD0.

1. Create a transaction variant and a screen variant for the screen you want, hide the tab (checkbox invisible)
2. Create the transaction code ZMSC2N (via transaction code SE93) as a "variant transaction", and assign the "transaction variant" created previously.
3. Run ZMSC2N -> the tab should be hidden

[former_member525572]

Thanks for your reply Rossi..

I will try and get back to you

[former_member525572]

Hi Rossi,

I tried that everything is working fine but i don't see any option to grey out fields in the classification tab of MSC2N but i'm able to greyout fields in Basic data 1 subscreen.

[Sandra_Rossi]

Not hiding a tab but greying out fields, is another question. I guess the fields in the classification tab are the ones in an ALV Grid control. Screen variants may only act on dynpro elements, not on GUI controls.

[former_member525572]

Oh ok Rossi..

Thanks for your wonderful help

[former_member525572]

Hey Rossi..

I had an other problem. Save button is disabled in my screen whereas in MSC2N it is enabled. Is there any way to enable it.

Thanks in advance.

[Sandra_Rossi]

If you didn't disable the save button via the screen variant, then the cause is maybe the standard which works differently based on the transaction code. For instance, there could be several transaction codes calling the same program, one for displaying, one for creating, etc., and the standard checks the transaction code to enable different buttons.

In that case, it's best to ask a new question (+ add a link to this thread for reference).

[former_member525572]

Thanks for your help Rossi

[matt]

Please note, your requirement is to find a way to have the functionality of MSC2N but with a few subscreens hidden. Your requirement is not "to copy the msc2n transaction...". That is merely your proposed solution to the requirement. You need to be aware that copying SAP standard programs for your own purposes is very bad practice. There's always another way that's less risky - even changing the original SAP program is better than copying it.

Also - be new to a technology won't give you any special treatment here. There's really no point in mentioning it.

[former_member525572]

Hi Matthew

Yes, of course, copying is bad practice. But business didn't want to change the transaction for all users. We need to acheive the above requirement to only certain users. Is there any other solution for this.