topic Re: HR Master Data Object in Application Development and Automation Discussions

HR Master Data Object

Former Member — Thu, 19 Jun 2008 14:57:52 GMT

Hello All, I'm trying to restrict HR users to change their own salary by using PA30 and PA40. I limited E under P_PERNER and it works if the user login as regular user. But it doesn't work if the user login as HR user. Does it relate to any of these objects below? What field value should be restrict? Many thanks

INFTY, SUBTY, AUTHC, PERSA, PERSG, PERSK, VDSK1

Re: HR Master Data Object

Former Member — Thu, 19 Jun 2008 18:16:41 GMT

I think what you are trying to do is not allow HR Admin chnage his data.

This can be implemented by using Double Verification Principle for Personnel Adminstration.

This process controls access to infotypes by stipulating that two users are always required to create or change infotype data.

http://help.sap.com/erp2005_ehp_03/helpdata/EN/ab/4bba3b3bf00152e10000000a114084/frameset.htm

hope this will help .

Re: HR Master Data Object

former_member74904 — Fri, 20 Jun 2008 07:35:59 GMT

hi rachel,

what exactly have you entered in the fields in P_PERNR?

furthermore, is the same person using two different user ID's? because when using P_PERNR, the user ID should have a connection to a personnel number (in IT0105) and only one user ID can be used per PERNR..

good luck!

Re: HR Master Data Object

Former Member — Fri, 20 Jun 2008 14:05:57 GMT

Hi there, thanks for your info. I did read the article about how to restrict HR Admins to change their own data. Should I just restrict to "read" for all infotype related to salary and "E" for P_PERNER?

Re: HR Master Data Object

Former Member — Fri, 20 Jun 2008 14:08:05 GMT

Hi there, thanks for your reply. I put "E" under P_PERNR, and the HR user with user ID HXXXX still can change their salary.

What is IT0105? Thanks

Re: HR Master Data Object

Former Member — Fri, 20 Jun 2008 16:27:39 GMT

Hi Rachel,

IT0105 is basically a communication type infotype which is used to link the personnel number with a user ID.

Thanks,

Neeraj

Re: HR Master Data Object

former_member74904 — Sun, 22 Jun 2008 18:02:26 GMT

I'm not sure what values you entered in the P_PERNR object, but you say you used 'E' (exclude). in that case you have to exclude write access to IT0008.

using P_PERNR will only be useful when there's a connection between a user ID (HXXXX) and a personnel number. this is done in IT0105 (subtype 0001). you can only enter one user ID per PERNR.

I hope I was able to clarify things a little for you.

Re: HR Master Data Object

Former Member — Mon, 23 Jun 2008 13:32:53 GMT

I'm not sure what is one user ID per PERNR. Below is the auth. object under P_PERNR, please let me know if something wrong in it. fyi, there are 2 PERNR

1ST:

AUTHORIZATION LEVEL M, R

INFO TYPE 0000, 0001, 0002, 0006, 0007, 0009, 0021, 0022, 0023, 0041, 0105, 0185, 0395

INTERPRETATION OF ASSIGNED PERSONAL NUMBER E

SUBTYPE 0001

2ND:

AUTHORIZATION LEVEL M, R

INFO TYPE 0008, 0014

INTERPRETATION OF ASSIGNED PERSONAL NUMBER E

SUBTYPE 0001

Re: HR Master Data Object

former_member74904 — Tue, 24 Jun 2008 08:26:34 GMT

rachel,

in you two P_PERNR objects above, you have excluded read access for the following infotypes:

INFOTYPE 0000, 0001, 0002, 0006, 0007, 0009, 0021, 0022, 0023, 0041, 0105, 0185, 0395
INFO TYPE 0008, 0014

and for all of the above infotypes, you have excluded read access for subtypes 0001. this is not what you aim to achieve.

you want to exclude write access (W, D, E, S) for infotypes 0008 and 0014 and so P_PERNR should look something like this:

P_PERNR nr. 1:

AUTHORIZATION LEVEL W, D, E, S
INFO TYPE 0008, 0014
INTERPRETATION OF ASSIGNED PERSONAL NUMBER E
SUBTYPE *

if you want to include read access for the infotypes in you mentioned in your example, it should look similar to this:

P_PERNR nr. 2:

AUTHORIZATION LEVEL M, R
INFO TYPE 0000, 0001, 0002, 0006, 0007, 0009, 0021, 0022, 0023, 0041, 0105, 0185, 0395
INTERPRETATION OF ASSIGNED PERSONAL NUMBER I
SUBTYPE *

the above will only work if the personnel number has a valid infotype 0105 subtype 0001 (System user name (SY-UNAME)) record. please look that up in PA30 and create that record with HXXXX if it is missing.