topic P_PERNR in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/p-pernr/m-p/2804733#M655305 <HTML><HEAD></HEAD><BODY><P>Hi, </P><P></P><P>I have a situation where a program called by our ESS system requires write access to infotype 2006 to succesfuly project leave for an employee. So, I assigned the role with P_ORGIN W and 2006. This is a standard program (used by PT50).</P><P></P><P>My issue is that those users with PA30 access can now update their own and others infotype 2006. </P><P></P><P>So... To ensure that the user could only write to their own infotype 2006 record and not others, I thought I would use P_PERNR (with W, I and ST *).</P><P></P><P>This has not restricted write access to the persons own 2006 infotype and they can continue to write to other employees 2006 infotype.</P><P></P><P>If I change P_ORGIN from write access to read, then the restriction works, but the program (outlined earlier) stops working.</P><P></P><P>P_PERNR is active in the system.</P><P></P><P>Any Ideas?</P></BODY></HTML> Mon, 03 Sep 2007 02:28:32 GMT Former Member 2007-09-03T02:28:32Z P_PERNR https://community.sap.com/t5/application-development-and-automation-discussions/p-pernr/m-p/2804733#M655305 <HTML><HEAD></HEAD><BODY><P>Hi, </P><P></P><P>I have a situation where a program called by our ESS system requires write access to infotype 2006 to succesfuly project leave for an employee. So, I assigned the role with P_ORGIN W and 2006. This is a standard program (used by PT50).</P><P></P><P>My issue is that those users with PA30 access can now update their own and others infotype 2006. </P><P></P><P>So... To ensure that the user could only write to their own infotype 2006 record and not others, I thought I would use P_PERNR (with W, I and ST *).</P><P></P><P>This has not restricted write access to the persons own 2006 infotype and they can continue to write to other employees 2006 infotype.</P><P></P><P>If I change P_ORGIN from write access to read, then the restriction works, but the program (outlined earlier) stops working.</P><P></P><P>P_PERNR is active in the system.</P><P></P><P>Any Ideas?</P></BODY></HTML> Mon, 03 Sep 2007 02:28:32 GMT https://community.sap.com/t5/application-development-and-automation-discussions/p-pernr/m-p/2804733#M655305 Former Member 2007-09-03T02:28:32Z Re: P_PERNR https://community.sap.com/t5/application-development-and-automation-discussions/p-pernr/m-p/2804734#M655306 <HTML><HEAD></HEAD><BODY><P>Closed due to no response.</P></BODY></HTML> Mon, 10 Sep 2007 00:45:02 GMT https://community.sap.com/t5/application-development-and-automation-discussions/p-pernr/m-p/2804734#M655306 Former Member 2007-09-10T00:45:02Z