Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from peter248 on Apr 20 at 11:05 AM I agree to your issue about data retention. A unique number would be the optimal solution.
Though we're going to start with a naming convention consisting on last name and first name. Recognizable accounts still are favored.
Regarding the data retention issue, we plan not to delete users. So for tracing back still users are available even if they have left the company. Of course, these users have been deactivated by:
- setting an end data in the past,
- locking them,
- removing all roles and profiles from them,
- assigning them to a specific user group.
I seem to remember this is also preferred by SAP.
| | | ---------------Original Message---------------
From: peter248
Sent: Wednesday, March 08, 2017 10:35 AM
Subject: Best practices to set up users regarding naming convention i.e.
What are arguments, pro and cons in setting up users in SAP? Specifically the user id that is used to logon to the system. Some companies use:
A. Lastname with one character of the first name, like John Doe would be: DOEJ
B. Initials, like: JD
C. Personal number, origin HR, like: 102355
D. Other possibilities?
The user name is limited to 12 positions. So lastnames longer than 12 positions would become an issue. Also multiple employees with the same (long) last name will become an issue.
Some questions that arise:
1. What arguments are there for chosing one or the other options?
2. What is your company using?
3. And of course, are there privacy reasons to not use a name? (Singling out?)
4. Are there laws regarding this privacy?
5. Is lastname allowed following the GDPR? Or is it nog advised? Why?
6. Best practices?
Hope you can shine some light on this matter. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
