Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from SAPAUSSEC on Apr 13 at 7:48 AM One consideration is data retention. Allow me to explain.
If you use last name say for J Smith user ID SMITHJ or JSMITH. What
happens if there are 2 employed? JSMITH1 and JSMITH2. That does not
look good to me.
What happens if J Smith leaves and another one joins. You go back through
history and how does one separate J Smith the first from a later J Smith.
Very important for any investigation for anything from fraud to user
trends (they are unlikely to have the same responsibilities and access).
I therefore suggest something unique - one possibility is employee
number. If you are going to use one of the Single Sign On mechanisms
then something unique and consistent is required across the entire IT
landscape.
| | | ---------------Original Message---------------
From: peter248
Sent: Thursday, April 13, 2017 4:58 AM
Subject: Best practices to set up users regarding naming convention i.e.
Okay, thanks, we have to create 118 of 500 users with very long names, and many users with the same number. As our HR number (in a separate solution called Workday) is the only unique identifier we have, we think about moving to this number.
But not all SAP competence center member are happy with that. But it makes sense to move that way because of IDM and SSO in the future. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
