<?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: Shell Role Concept in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465763#M1416304</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sushant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It sounds like you are talking about cross-system composite roles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;What is use&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;If you are using CUA you can define roles in your CUA master that contain roles for the target systems too.  That way if you have HR as your CUA master (possibly using org assignments too?), you can provision for all relevant systems based on the role definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Advantages&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Can speed up provisioning into multiple system&lt;/P&gt;&lt;P&gt;Helps support accurate job definitions for all system access&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Disadvantages&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;CUA needs to be setup and maintained properly (not sure if that is a disadvantage but is a factor for consideration)&lt;/P&gt;&lt;P&gt;If enough thought does not go into design then you end up with composites/shells that cover lots of eventualities&lt;/P&gt;&lt;P&gt;If you have a granular single-role concept then your shell role could get very cluttered by the number of assignments required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Maintain&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Use PFCG in the CUA master&lt;/P&gt;&lt;P&gt;Like any other composite role - use text comparisons etc to pull in the roles from the target systems&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Jan 2010 08:55:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-01-18T08:55:45Z</dc:date>
    <item>
      <title>Shell Role Concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465760#M1416301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any one can explain me concept of shell role, what is use, advantages, disadvantages how to maintain shell roles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sushant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jan 2010 07:16:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465760#M1416301</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-18T07:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: Shell Role Concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465761#M1416302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sushant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please elaborate on what you mean by "Shell roles".  As often happens with non-SAP terminology, it can mean a few things.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jan 2010 07:35:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465761#M1416302</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-18T07:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: Shell Role Concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465762#M1416303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a bit info which i had was, for example if u create a role in the HR but the user can get access for BI  system, and we can maintained  this role in the HR system only,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sushant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jan 2010 08:30:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465762#M1416303</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-18T08:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: Shell Role Concept</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465763#M1416304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sushant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It sounds like you are talking about cross-system composite roles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;What is use&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;If you are using CUA you can define roles in your CUA master that contain roles for the target systems too.  That way if you have HR as your CUA master (possibly using org assignments too?), you can provision for all relevant systems based on the role definition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Advantages&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Can speed up provisioning into multiple system&lt;/P&gt;&lt;P&gt;Helps support accurate job definitions for all system access&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Disadvantages&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;CUA needs to be setup and maintained properly (not sure if that is a disadvantage but is a factor for consideration)&lt;/P&gt;&lt;P&gt;If enough thought does not go into design then you end up with composites/shells that cover lots of eventualities&lt;/P&gt;&lt;P&gt;If you have a granular single-role concept then your shell role could get very cluttered by the number of assignments required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Maintain&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Use PFCG in the CUA master&lt;/P&gt;&lt;P&gt;Like any other composite role - use text comparisons etc to pull in the roles from the target systems&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jan 2010 08:55:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/shell-role-concept/m-p/6465763#M1416304</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-18T08:55:45Z</dc:date>
    </item>
  </channel>
</rss>

