<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: HR Security in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078373#M1179601</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THANKS FOR UR REPLY. WAHT IS THE PURPOSE OF CREATING TWO ROLES IF WE ARE GIVING VIEW ONLY ACCESS.?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Jan 2009 01:00:25 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-01-28T01:00:25Z</dc:date>
    <item>
      <title>HR Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078371#M1179599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi frds,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have 2 structural Authorizations and role assigned to an employee. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One structural Authorization is his personnel area org structure  and the other is a common org structure.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For his personnel area he is able to view and maintain his employees...........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the other Org structure he is able to view the structure but not the employees in it. Now my requirement how can the Authorization objects be defined, so that he can view only Infotype 0002 for the the common org structure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2009 15:57:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078371#M1179599</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-27T15:57:18Z</dc:date>
    </item>
    <item>
      <title>Re: HR Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078372#M1179600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look into using context authorisations in your design concept.  This is achieved by using P_ORGINCON (field PROFL) in your design - you maintain the PROFL field with the name of the structural profile used for the common org structure   - by creating this link between the role and the structural profile you can prevent an overlap of activities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your solution you will need 2 individual roles for your user. Each role should be maintained with P_ORGINCON as described above. &lt;EM&gt;(This is just an example)&lt;/EM&gt; One role should contained infotype 0002 for view/maintain  access and another role should contain also contain infotype 0002 for view access only. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also check that the swtiches are activated for context authorisations else it won't work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's loads of information and documentation about this so it worth using google and searching this forum.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Charmaine&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2009 21:06:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078372#M1179600</guid>
      <dc:creator>charmaine_greene</dc:creator>
      <dc:date>2009-01-27T21:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: HR Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078373#M1179601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THANKS FOR UR REPLY. WAHT IS THE PURPOSE OF CREATING TWO ROLES IF WE ARE GIVING VIEW ONLY ACCESS.?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jan 2009 01:00:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078373#M1179601</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-01-28T01:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: HR Security</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078374#M1179602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It depends on the business requirement - if &lt;U&gt;all&lt;/U&gt; the transactions in the existing role apply to both structures then use the existing role, if not - then create a new one,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jan 2009 23:39:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hr-security/m-p/5078374#M1179602</guid>
      <dc:creator>charmaine_greene</dc:creator>
      <dc:date>2009-01-28T23:39:46Z</dc:date>
    </item>
  </channel>
</rss>

