Go Back   Wiki NewForum | Latest Entertainment News > Career Forum & Tips > Tech Forum & Tutorial > SAP Forum > SAP HR Forum

Talent Management - Central Person (CP) instead of Person (P) object...

Views: 4788  
Thread Tools Rate Thread
Payroll Time OM & PA Portal Payroll Fixes Career Tips SuccessFactors
Old 07-12-2010, 10:53 AM
bholas bholas is offline
Award Winner
Join Date: Apr 2010
Posts: 4,983
Default Talent Management - Central Person (CP) instead of Person (P) object...


Please help me to understand, why Talent Management uses CP object instead of P i.e. why it has been designed for CP object?


If I may take a stab at this one, here is my opinion on this much discussed subject (at least, I find the subject comes up a lot!)

The big issue here is where Talent Management came from. It used to be just Succession Planning and was a subset of E-Recruiting, prior to EhP4. E-Recruiting can be/is deployed on a separate non-ECC system. Non-ECC systems don't have the object P. E-Recruiting is no different than CRM/SRM/etc in that they rely upon Central Person and Business Partner to act as the equivalent to object P.

Obviously this is just conjecture but my guess is that when the decision was made to really expand Talent Management and bring it into ECC, it was determined that so much ground work had been done already with the Talent Management data against the Central Person, that there was just too much work to be "undone and redone" if SAP wanted to detach Talent Management from the CP and connect it to the P.

From a front end perspective, it's more or less invisible to the end user, so I'm guessing they felt as though the risks were low in not making Talent information based upon object P.

That's my opinion. I certainly welcome any other input you may receive. Let me know if this is causing you any problems though and we can try to help you work around them.

Reply With Quote

Latest News in SAP HR Forum

Thread Tools
Rate This Thread
Rate This Thread:

Powered by vBulletin® Version 3.8.10
Copyright ©2000 - 2022, vBulletin Solutions, Inc.