<?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: Master role set up in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396996#M1924856</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;OL&gt;&lt;LI&gt;What abishek wrote! Never include organisation levels in a master, if you aren't sure that this will stay identical over the whole life cycle of the business process. Hint: it won't. The less you doctor with the master, the more grateful you will be in 10 years time. Just sayin'.&lt;/LI&gt;&lt;LI&gt;Never put the name of company codes (or any other Level) into the name of your roles - again, it isn't likely that the relation of company codes to plants to other-org-Levels will be the same for every plant, let alone every company code. Your business might grow "organically" and the more &lt;SPAN style="text-decoration: line-through;"&gt;chaotic&lt;/SPAN&gt; organic the less you serve transparency by including one organisation Level to the name. Think of another nomenclature instead.&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Nov 2015 14:06:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-11-17T14:06:15Z</dc:date>
    <item>
      <title>Master role set up</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396993#M1924853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are trying to set up master roles as well as derived roles off the master ones to give access only to certain company codes.&lt;/P&gt;&lt;P&gt;Currently we are using a range of companies in the master role (i.e. AB01 - AB99) and we are only using 10 companies of the possible 99.&lt;/P&gt;&lt;P&gt;Would there any issues if we set up the company as " * " (asterisk) in the master role rather than AB01 - AB99 ? Does anyone foresee any risks associated to using asterisk instead of a wider range ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 23:43:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396993#M1924853</guid>
      <dc:creator>Tiberius</dc:creator>
      <dc:date>2015-11-16T23:43:07Z</dc:date>
    </item>
    <item>
      <title>Re: Master role set up</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396994#M1924854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tiberius,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can keep this field as BLANK in master&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peeyush&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Nov 2015 09:50:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396994#M1924854</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-17T09:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: Master role set up</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396995#M1924855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Always Keep Org Data blank in Master role, you can fill * in derived role but challenge will be that all Company Code will be included and you have to reomoved other 89 afterwards, which are not required for that user ids.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would advice to include on required Company Codes in Org level of derived role&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Nov 2015 10:21:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396995#M1924855</guid>
      <dc:creator>abhishek_sehgal</dc:creator>
      <dc:date>2015-11-17T10:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: Master role set up</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396996#M1924856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;OL&gt;&lt;LI&gt;What abishek wrote! Never include organisation levels in a master, if you aren't sure that this will stay identical over the whole life cycle of the business process. Hint: it won't. The less you doctor with the master, the more grateful you will be in 10 years time. Just sayin'.&lt;/LI&gt;&lt;LI&gt;Never put the name of company codes (or any other Level) into the name of your roles - again, it isn't likely that the relation of company codes to plants to other-org-Levels will be the same for every plant, let alone every company code. Your business might grow "organically" and the more &lt;SPAN style="text-decoration: line-through;"&gt;chaotic&lt;/SPAN&gt; organic the less you serve transparency by including one organisation Level to the name. Think of another nomenclature instead.&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Nov 2015 14:06:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/master-role-set-up/m-p/11396996#M1924856</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-11-17T14:06:15Z</dc:date>
    </item>
  </channel>
</rss>

