Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Applies to:
SAP release ECC 4.7 onwards. For more information, visit the Enterprise Resource Planning homepage.

Summary
This article explains the concept of Central Person and to follow in Case if all the Personnel Assignments for a Personnel Number are not shown in PA30 Author: Vijay Sundaresan

Company: Tata Consultancy Services Created on: 20 July 2009

Author Bio
Vijay S is working in Tata Consultancy Services since 2 years and has a wide experience in SAP HCM modules like Personnel Management, Organizational Management and Payroll.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Table of Contents
Introduction ......................................................................................................................................................... 3 Discussion on a Specific Scenario for a Better Understanding .......................................................................... 3 Relationship CP B 209 P Cannot be Maintained Using Basic Transaction .................................................... 5 Disclaimer and Liability Notice .......................................................................................................................... 10

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Introduction
CP (Central Person) is an object type which is linked via a relationship to object type P (Person). CP object is created in background while hiring a person (necessary config should be in place). CP is majorly required when there are multiple countries implemented in a system and an Employee needs to be re-assigned to a country other than Home country. In that case a new PERNR is generated for this employee for the new Country and this PERNR is again linked to the same CP object. Thus all the various PERNRs of Employee are liked to the same CP which uniquely identifies the Employee. CP->PERNR1 (Object type P) CP->PERNR2 (Object type P) CP->PERNR3 (Object type P) CP->PERNR4 (Object type P)

This helps in tracking the Employee with different PERNRs in different countries with the a unique Central Person ID (CP).

Discussion on a Specific Scenario for a Better Understanding

In PA30, Below is the screen where the Pers Assignment at the top has only one assignment in Yellow.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

The related Personnel number 3364 is shown below with Pers Assgn as Blank.

Ideally the above two personnel numbers refers to one and the same Person due to the different Personnel Assignments. (like expatriate). But the Personnel Assignments in the system shows just one instead of two.

This is because that the Central Person ID 00000227 is linked only to Personnel Number 00003369 and not to the related Personnel number 00003364 as it is below.

Now the above two Personnel Number 3364 and 3369 has to be linked to the same Central Person ID so that there can be two different Personnel Assignments. When you try to create a link between the Central Person and the Personnel Number directly in PP01, you will get the below error.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Relationship CP B 209 P Cannot be Maintained Using Basic Transaction

This can not be maintained through the basic transaction PP01.

To maintain this through Basic Transaction, following settings has to be done.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Go to SM30 and the table is T777E

Select the relationship 209 and GOTO Allowed Relationship in left

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

In the below screen, if both the Top Down and Bottom Up relationships are checked (enabled) for NOT MAINTAINED field, then it will not allow to maintain in the basic transaction PP01.

So in order to maintain in the basic transaction, Uncheck (Disable) those entries as shown below and save it in a transport request (Customizing) and move it to the required environments.

Once the changes are done, goto the Basic transaction PP01 and create the relationship as below.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 7

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

After saving the same, below is the overview of PP01 where the Central Person ID 00000227 is assigned to Personnel Numbers 00003364 and 00003369.

Now the relationship is maintained and goto PA30 for both the Personnel Numbers 00003364 and 00003369 where you will find two Personnel Assignments which is as per the requirement.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 8

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Now you can revert back the settings in table T777E as below by checking the field so that the changes through Basic transaction is locked and transport to the required environment.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 9

Concepts of Central Person and its Significance in Different Personnel Assignments SAP HCM

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 10