Showing results for 
Search instead for 
Did you mean: 

P_PERNR problem

Former Member
0 Kudos


I have some problem in object P_PERNR. Hope someone can help me with the following scenario.

One of my client needs ESS/MSS. My problem is that in the portal, there is an option for employee to be delegated the position of manager when his/her manager is not around. We need to restrict that the employee will not be able to approve his/her own request when he/she is in the position of manager.

To make it clear, here is the detailed description. Employee A would like to request for Leave (IT2001). Once the request is made, the request will be sent to employee A's manager for approval. If the manager is not around, Employee A can be delegated the task of manager. However, we would like to restrict that Employee A would not be able to approve the leave application which he/she make earlier.

I understand that this can be done through object P_PERNR. However, I have tried a lot of combination but I still end up with the same. Can anyone help?


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos
Active Contributor
0 Kudos

Hi Sean,

Welcome to SDN.

Check this might help -

Although the structural authorization example will work, there's a simpler way. For the ESS users, you must assign the authorization object P_PERNR for the infotypes (and subtypes) and that you want them to see only their own data for, and make sure you do not assign them P_ORGIN for those infotypes.

Before P_PERNR is effective, though, you must activate the authorization check for this object. You do this with transaction OOAC, changing the value for AUTSW PERNR to 1.

P_PERNR comes into play when a user tries to access infotype data against their own personnel number. For other personnel numbers, P_ORGIN is used.

Also, to post any question please use the appropriate forum for maximum visibility.

For HR related queries use this following -