<?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: Authorization - Derived roles (Organization data) in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727651#M317090</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Anders,&lt;/P&gt;&lt;P&gt;There can be two approaches for the same.&lt;/P&gt;&lt;P&gt;1. Include the Object into Organizational level by sap report ...dont really remmebr its name now but shd get it by &lt;STRONG&gt;PFCG&lt;/STRONG&gt;ORG* search...its something like OFCG add ORG Criterion ..etc...&lt;/P&gt;&lt;P&gt;2. In case of K_PCA we deleted the parent child role for these single roles.. and they are considered stand alone single roles... ( This is followed for us as the quantity is level and well under manageable limit.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Sri&lt;/P&gt;&lt;P&gt;Award points for helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Dec 2006 16:07:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-12-29T16:07:00Z</dc:date>
    <item>
      <title>Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727646#M317085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only part that will not be affected when you generate the template for derived roles is the organization data, as I know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I have values in objects/fields that I need to make specific for each derived rolls but these data fields does not exist at organization data. Any suggest?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 12:35:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727646#M317085</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T12:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727647#M317086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Make these fields organisational fields:&lt;/P&gt;&lt;P&gt;how to see sap Note 323817.&lt;/P&gt;&lt;P&gt;If you cannot (like field activity)  than consider building more template roles&lt;/P&gt;&lt;P&gt;Or be sure to maintain them after every derivation manually (not recommended)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 13:52:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727647#M317086</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T13:52:21Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727648#M317087</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;What objects/fields are you looking for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create New role with your objects/fields and assing to the user.&lt;/P&gt;&lt;P&gt;Make sure that in the generic role you dont maintain these values...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Soma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 14:03:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727648#M317087</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T14:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727649#M317088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Following are 2 areas/objects that I need to customize for each roll.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Object:M_IS_WERKS&lt;/P&gt;&lt;P&gt;Field:MCINF&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Object: K_PCA&lt;/P&gt;&lt;P&gt;Field: RESPAREA&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 14:55:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727649#M317088</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T14:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727650#M317089</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;Can you let me know what are the T-Codes you are executing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is to check for objects status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Soma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 15:55:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727650#M317089</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T15:55:18Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727651#M317090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Anders,&lt;/P&gt;&lt;P&gt;There can be two approaches for the same.&lt;/P&gt;&lt;P&gt;1. Include the Object into Organizational level by sap report ...dont really remmebr its name now but shd get it by &lt;STRONG&gt;PFCG&lt;/STRONG&gt;ORG* search...its something like OFCG add ORG Criterion ..etc...&lt;/P&gt;&lt;P&gt;2. In case of K_PCA we deleted the parent child role for these single roles.. and they are considered stand alone single roles... ( This is followed for us as the quantity is level and well under manageable limit.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Sri&lt;/P&gt;&lt;P&gt;Award points for helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 16:07:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727651#M317090</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T16:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization - Derived roles (Organization data)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727652#M317091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As already mentioned by Auke Visser:&lt;/P&gt;&lt;P&gt;Note &amp;lt;a href="https://service.sap.com/sap/support/notes/323817"&amp;gt;323817&amp;lt;/a&amp;gt; describes how to turn an ordinary authorization field into an organizational level field using report PFCG_ORGFIELD_CREATE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Frank&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 16:09:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-derived-roles-organization-data/m-p/1727652#M317091</guid>
      <dc:creator>Frank_Buchholz</dc:creator>
      <dc:date>2007-01-02T16:09:27Z</dc:date>
    </item>
  </channel>
</rss>

