Question:
hi All,
Our current landscape is 4 systems, 3 clients on each system (e.g DEV = clients 200, 230 and 240) and we are using CUA for assigning roles to users.
We received a request from business to change the current userid's, e.g bennl(surname+initial), which is also the domain userid to position id's (e.g P00010).
Please give your views on the above but alsoe bear in mind of the following:
We have mutiple HR Org structures (3)
Userid or Position id's will not be linked to the org structure, but ORG structure will be used to trace the person behind the position.
thanks,
Lynne
Answer:
Hi Lynne,
I really cant understand what do you mean by PositionID - I hope it is clear to me, it is not the 8digits ID from org.structure. Are these ID's in any relatioship? Or is your PositionID only some characterstring which should be unique in the system? What is then the question? Do you ask if PositionID is better for user identification as the string made from surname and some letters from the first name? Could you clarify your question?
Patla
Answer:
Hi Patla,
Yes it is EXACTLY that... the 8digits ID from the org structure, only difference however is that it will NOT be linked to the org structure in any way.
What are the pro's and con's???
Answer:
If I've understood correctly, then I believe you're on a rocky road.
Userid smithj is a lot easier to understand and to trace if there's a problem with e.g. a document.
Also smithj will remain throughout the user's life (marriage excepted) with the company wherever they work in the company. With position based userids what happens when the user moves position will they have to have a new 'id' ? - a bit of built in overhead here. And what happens when all positions change - e.g. in a reorganisation - another bit of overhead - well actually morelike a headache.
Perhaps I've misunderstood - but if not resist it.
PS: What's the reason given by the business ?
_________________
Best Regards
Bazza
Answer:
Bazza, plain and simple... the business knows more of SAP than what we do.. (or so they think).. they are hoping it to be less admin intense.. that might be the case for them, getting the person linked to HR, CO and the workflow sorted but all the disadvantages attached to such a move is not good... Please understand that we are against it as well and i guess they're not thinking of the licensing issues (we currently have multi-client logon's).. fraud being the order of the day... our internal auditor is against such a move and is more than happy to intervene should the business decide to go that route.
Thanks kindly for your reply, much appreciated
Ciao,
Lynne