Using SHD0 for transaction variants with 4.6C

Question

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

Answer 1

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