<?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: How to avoid create many roles in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557082#M1268250</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;As a SAP default field, Doc. Type should not be changed to Org. level. And if you are not hiring 300 people to maintain each document type separately (which is itself a foolish idea) please put more concentration to segregate user access by "&lt;STRONG&gt;Purchasing Group&lt;/STRONG&gt;", "&lt;STRONG&gt;Purchasing Organization&lt;/STRONG&gt;".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. create roles for different "&lt;STRONG&gt;Purchasing Group&lt;/STRONG&gt;", "&lt;STRONG&gt;Purchasing Organization&lt;/STRONG&gt;" first. (say 10 roles)&lt;/P&gt;&lt;P&gt;2. for each set of those 10 roles, you just clone them for different doc types (as far as required).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 role for each doc. type: this level is granularity is not so important from risk point of view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dipanjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 May 2009 21:15:46 GMT</pubDate>
    <dc:creator>sdipanjan</dc:creator>
    <dc:date>2009-05-08T21:15:46Z</dc:date>
    <item>
      <title>How to avoid create many roles</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557078#M1268246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an issue on how to create roles.&lt;/P&gt;&lt;P&gt;I have 300 shops and each user will be authorised (by document type in Purchase Requisition) &lt;/P&gt;&lt;P&gt;to make requisitions only for his shop.&lt;/P&gt;&lt;P&gt;Can i somehow use the authorization object for PR and not create 300 roles( one per shop?)&lt;/P&gt;&lt;P&gt;Is there a way to add an auth object value to user profile?&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2009 11:37:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557078#M1268246</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-08T11:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid create many roles</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557079#M1268247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As per the given information, it seems there will be 300 employees for this work!!!!! &lt;/P&gt;&lt;P&gt;Please let me know if Yes, else let me know how many employees are going to work their.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dipanjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2009 12:56:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557079#M1268247</guid>
      <dc:creator>sdipanjan</dc:creator>
      <dc:date>2009-05-08T12:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid create many roles</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557080#M1268248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you can build one role for the task in the shop and are sure that the roles will be identical accross all the shops, then &lt;STRONG&gt;Derived Roles&lt;/STRONG&gt; is an option if you can find an object which is consistently used by the transaction(s) and differentiates for an organizational field which relates to your 300 shops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2009 13:21:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557080#M1268248</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-08T13:21:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid create many roles</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557081#M1268249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;bowing to julius.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try to determine whether you could use purchasing groups as an organizational distinction for the different shops. i strongly recommend that. then proceed as julius adviced and create derived roles, where the only diffrerence might be the purchasing group.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2009 20:19:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557081#M1268249</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-08T20:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid create many roles</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557082#M1268250</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;As a SAP default field, Doc. Type should not be changed to Org. level. And if you are not hiring 300 people to maintain each document type separately (which is itself a foolish idea) please put more concentration to segregate user access by "&lt;STRONG&gt;Purchasing Group&lt;/STRONG&gt;", "&lt;STRONG&gt;Purchasing Organization&lt;/STRONG&gt;".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. create roles for different "&lt;STRONG&gt;Purchasing Group&lt;/STRONG&gt;", "&lt;STRONG&gt;Purchasing Organization&lt;/STRONG&gt;" first. (say 10 roles)&lt;/P&gt;&lt;P&gt;2. for each set of those 10 roles, you just clone them for different doc types (as far as required).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 role for each doc. type: this level is granularity is not so important from risk point of view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dipanjan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2009 21:15:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557082#M1268250</guid>
      <dc:creator>sdipanjan</dc:creator>
      <dc:date>2009-05-08T21:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid create many roles</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557083#M1268251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 May 2009 07:29:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-avoid-create-many-roles/m-p/5557083#M1268251</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-22T07:29:18Z</dc:date>
    </item>
  </channel>
</rss>

