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 configuration should be in place). CP is mainly 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).  

SCENARIO:  

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

/wp-content/uploads/2013/11/0001_331620.png

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

/wp-content/uploads/2013/11/0002_331621.png

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.

/wp-content/uploads/2013/11/0003_331637.png

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.  

Relationship CP B 209 P cannot be maintained using basic transaction  

/wp-content/uploads/2013/11/0004_331638.png

This can not be maintained through the basic transaction PP01.  

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

Go to SM30 and the table is T777E

/wp-content/uploads/2013/11/00013_331665.png

Select the relationship 209 and GOTO Allowed Relationship in left  

/wp-content/uploads/2013/11/005_331639.png

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.

/wp-content/uploads/2013/11/0006_331647.png

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.

/wp-content/uploads/2013/11/007_331648.png

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

/wp-content/uploads/2013/11/008_331650.png

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

/wp-content/uploads/2013/11/009_331651.png

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.

/wp-content/uploads/2013/11/0010_331658.png

/wp-content/uploads/2013/11/0011_331660.png

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.

/wp-content/uploads/2013/11/00012_331664.png

Cheers

Ratan

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply