Knowledge Management

Question:
Hi,
I notice that whenever a person (Object Type 'P') is created in SAP HR, system automatically creates a relationship B 209 with Object Type 'CP' (Central Person'). I am pretty sure this was not happening last time I was on a SAP HR project.
Can any SAP guru enlighten me on whether this is a bug or a feature. What is the use of this Object Type in OM or PD? Any replies would be greatly appreciated. Alternatively please point me to a link in SAP help or elsewhere where I can read it up for myself.
ENdurista, are you there?
Thanks in advance
Answer:
Wouldn't this have something to do with the new concept of 'Global Employee' ?
Answer:
Wouldn't this have something to do with the new concept of 'Global Employee' ?
Hi ,
Thanks for the reply.
I must confess that events seem to have moved a bit too fast for me. I guess I am still stuck in the world where SAP 4.6b rules. WHat exactly is this new concept of Global EMployee?
Answer:
Sorry, can't give you much details either. I just heard about it because we are preparing an upgrade to 4.7.
This is what I understood from it:
if your company is divided into sub-companies (this would be the entity Company in SAP) employees who are transferred to another company of the group will receive a new pernr. This usually leads to problems with regard to reporting an the employee's full career within the group, problems coming from:
1) the pernr-change as such
2) authorization problems when structural authorizations are used for limiting access to a user's own company.
The Global Employee concept should solve this problem but I don't know how it works.
My guess is that it links all pernrs that an employee may receive to 1 central reference number. This could be the CP you mentioned.
I have no idea on how SAP handles tha authorization issues.
Sorry that's all I know about it.
Answer:
Hello,
A CP is aimed at linking an employee numbers (when he has several ones) all together. Basically, the CP object and the first relationship with pernr are created when hiring an employee.
If the employee gets a new pernr (when moving to an other company for example), filling out the "Reference pers. no" field in IT 0000 creates a new relationship between the new pernr and the corresponding CP, as creating an IT 0031 do.
The CP was supposed to solve the global companies issues regarding global mobility within SAP (cause you can't move to another country without getting a new pernr and loosing history).
In theory, this is the way things were supposed to work. But they still don't work in R/3 Entreprise. When you run the "Country reassignment" action (n°05), you still get nothing : no infotypes are copied, no reference pernr is created.
In conclusion, CP is unusefull. So don't worry about that.
Answer:
Thanks for all the replies, Frenchie and K.. They were quite lucid, and I have now got a satisfactory explanation for my doubt.
I however request anyone to continue to add further thoughts to this thread, if there are any. Any ideas on how this object can be used in other ways than intended by SAP, for example.