ess/mss best practice

[Former Member]

When implementing employee self service and manager self service what are the best practices when creating ids. Do most use active directory. Or employee Ids and or generated numbers.

I would like to know what the best methods some may recommend.

Thanks.

[Former Member]

Hi

I am not sure about these.

But I think these best practices guides can help you

http://help.sap.com/bp_epv260/EP_JA/html/EP/N26_ESS.htm

http://help.sap.com/bp_epv260/EP_JA/html/EP/N27_MSS.htm

[Former Member]

Deepak,

Where in those documents you have linked to do you see a best practice for naming conventions of user IDs in ESS/MSS scenarios?

Cheers,

Julius

[Former Member]

Hi

I am really sorry that I had provided the totally wrong documents for this query. I jsut got it wrong.

-

---

In our case, we had implemented the ESS/MSS scenario using the LDAP configurations. In a nutshell,

the employee is created at the Active Directory, which is connected to the CUA client and we have associated the ESS with the CUA.

[Former Member]

Thanks for clarifying!

Most companies which I have observed use the AD alias, which is also the email address SMTP name and easier to associate to the IT 0105 pernr via the employee first name and last name, and that in the user master address data as well.

First 7 characters are last name, last character is first character of first name, etc => 'BUSSCHEJ'

But then again, if your AD name is a generated number or cryptic value, then why not call yourself S123456789 like here at SDN, or R2D2 for that matter.

Using the pesonnel number is another option, but you should first check where else it is used. Perhaps it is like the US Social Security Number, which is meant to be kept "top secret" like a password...