07-01-2015 9:52 AM
Hi,
We have provided access to the end users to the tcode SU0 instead of SU3 to restrict the suers not to be able to change the profile data , but to change the data in Default tab (for e.g.: Assigning default printer, changing decimal notations etc). The tcode was working fine and the users were able to change the data in "Default" tab. But recently the same tab has become read-only or in other terms the user is not able to change the information.
So what might have caused the tcode to behave in this manner. Is there any auth. object which must be assigned to the role to which the tcode belongs? or is there any alternate tcode (not SU3) to achieve the requirement.
Please help!!
Regards,
Azhar
07-01-2015 10:08 AM
SU0 maintain defaults only
SU1 maintain adress only
SU2 maintain parameters only
SU3 maintain address, defaults and parameters
If you want to further restrict these transactions you have to create transaction variants (= addidional transactions) or transaction standard variants (=modification of the original transactions) using transaction SHD0.
Using SHD0 you can turn input fields into display fields, hide fields or set default values for input fields fon any transaction.
Thanks & Regards,
Ankit
07-01-2015 10:58 AM
Thanks for the reply,
We want the user to maintain default values themselves which is not possible right now in SU0, but was possible earlier.
What have caused the problem?
Regards,
Azhar
07-01-2015 11:20 AM
Hi
Didn't you implemented CUA?
During setup, user account fields can be blocked for local changes.
Regards
Przemek
07-01-2015 1:06 PM
We had recently implemented CUA and it is possible that during the setup, the user account fields are blocked for local changes.
The best thing would be to unblock the user account fields so that the end user can maintain the data or when the new user is created, the the administrator must maintain the minimum required info in the user profile.
Please suggest.
Regards,
Azhar
07-01-2015 1:15 PM
Hi Azhar,
It depends on the business how they want to do. If the end users have to maintain the data or the administrator has to maintain the data.
If you want to allow the end users to maintain their user account details, then you need to change the settings in SCUM transaction. If you want to allow the administrator to maintain the data, then he can maintain the same for the users from the CUA system.
Regards,
Laxman
07-01-2015 1:17 PM
In CUA use transaction SCUM you can change field attributes to:
- PROPOSAL - changes in child system will be made only during user creation
- REDIST - all changes will go to or from child system