P_per no issue

[Former Member]

Scenario:

We have two Roles one for ESS (EXISTING ROLE)and other one for Performance Appraisal. (NEW ROLE)

Both Roles has P origincon & P_perno.

NEW ROLE that will be added to user has following values:

for P_PERNO.

Manually HR: Master Data - Personnel Number Check

Authorization level R

Infotype *

Interpretation of assigned per *

Subtype *

Manually HR: Master Data - Personnel Number Check

Authorization level *

Infotype *

Interpretation of assigned per E

Subtype ' '

HR: Master Data - Personnel Number Check

Authorization level *

Infotype *

Interpretation of assigned per E

Subtype *

Old Existing Role has following P_PERNO values.

Authorization level D, E, M, R, S, W

Infotype 0002, 0006, 0009, 0021, 0077, 0105, 0106, 0167, 0168, 0169

Interpretation of assigned per I

Subtype *

HR: Master Data - Personnel Number Check Z:HRPRTESS09

Authorization level M, R

Infotype 0000, 0001, 0003, 0007, 0008, 0171, 0378

Interpretation of assigned per I

Subtype *

Question is ->

Would P_perno Value from NEW Role overwrite

P_perno values in EXISTING Role? Please advise.

Thanks,

From,

Pranav

[former_member74904]

However, since PSIGN = * and * can be substituted for any value, PSIGN and E can also be interpreted as I. This can also lead to an undefined situation. In earlier releases, the authorization was denied on the basis of the rule E is stronger than I. This meant that superusers with assigned personnel numbers were not able to access their own personnel number. The programs have since been changed and now * is interpreted as I and is stronger than E. In other words, * is stronger than E and E is stronger than I, whereby * is interpreted as I.

this means that any P_PERNR object with PSIGN value * will overrule any other P_PERNR object with PSIGN = E.

with this in mind, the new role would overrule all values from the old role.