05-19-2009 3:21 PM
In the Maintain User Profile, we think we would like to allow users to update their own email address. In our system, this field is protected for the users own data, unless you are a security administrator using SU01. Even a security administrator can't update their own email address using SU1 or SU3, they must use SU01 and modify the field that way.
Is there any system option that makes this field available for modification?
05-19-2009 5:11 PM
Hello,
Please ask the system administrator update the email address field by using LSMW (recording through SU01)
This guide may be useful.
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
Regards,
Ravi
05-19-2009 5:15 PM
05-19-2009 5:29 PM
Hi - this is on a native ECC 6.0 system, through the GUI. I just want the users to be able to update their own email addresses on the first tab of the user master.
The field is protected from update on the "address" tab via SU1 or SU3.
05-19-2009 5:53 PM
hmmm...
In that case you need to parametrize SU3 and create your own custom TCode and then add this to the common role for the users.
Regards,
Dipanjan
05-19-2009 5:49 PM
Hi,
SU1, SU3 never give option to change email address. There is no such system configuration has been changed.. don't worry.
Regards,
Dipanjan
05-19-2009 6:03 PM
05-19-2009 6:21 PM
>
> In the Maintain User Profile, we think we would like to allow users to update their own email address. In our system, this field is protected for the users own data, unless you are a security administrator using SU01. Even a security administrator can't update their own email address using SU1 or SU3, they must use SU01 and modify the field that way.
>
> Is there any system option that makes this field available for modification?
We don't allow our users to change their email in their master records due to our business requirements. Most of our workflow are based on email so we don't want them to redirect it to their hotmail email, etc. We get a report of new and email updates and run our SECATT script to change the user master record emails.
You might want to investigate the business impact on the changes you are proposing before it gets implemented.
Good Luck!
05-19-2009 6:32 PM
Yes, we would consider business impact before allowing this, however, it looks like it's not an option anyway!
05-23-2009 8:42 PM
Changing the mail ID is an administrator task, as the mail ID is used for a multiple of scenarios (John already gave one from workflow...) where it is used to identify the person who requests information (an example would be a new password via a self-service).
But if you realy want this, then it is possible if you are willing to take on some risk by granting the administrator access to change the mail ID to the user(s) which update it and isolate it in a custom transaction (via a workflow, which for example checks than a hotmail address is not used, and that the mail ID is unique...).
This can be done programmatically using BAPIs. You can then add your own checks before the BAPI is called (for example that BNAME = SY-UNAME...).
Cheers,
Julius
05-24-2009 2:44 PM
however, it looks like it's not an option anyway!
Yes , that is the Point. We should not allow employees to provide incorrect (as per their own convenience) mail address As it is managed by administrative units of a company; similarly it is done in SAP by the User Administrator and Not by the users themselves. SAP didn't make this open to the users.
Regards,
Dipanjan
05-27-2009 10:19 AM
SU1/SU3 doesn't allow the change of the email because of the business impact as described in some of the other reply. Changing the email using SU01, SU10 or the BAPIs requires an authorization for S_USER_GRP with activity change. Only user administrators have such an authorization.
Kind regards
Frank Buchholz
05-28-2009 5:43 PM
Hi Frank,
Thanks for the update.
I believe SAP is also designed in right way, in case if the user has updated wrong email address or some personal email address and workflows are triggering, then the mails may go outside (in case if the gateway is open).
I still believe that the best way to update the all the user master records using LSMW in a simple way, as stated earlier in this thread.
Please let me know your thoughts.
Regards,
Ravi
05-28-2009 9:23 PM
LSMW (Legacy System Migration Workbench) is a data migration tool, not a maintenance tool.
My preference would be for an LDAP sync or IdM as source. Next best would be a BAPI or transaction MASS.
LSMW ranks a close second last. Last resort is direct updates for mass maintenance of existing data (with all possible side affects to the referential integrity of the database)...
My 2 cents,
Julius