<?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 variable in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818768#M918428</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, note 698401 really did solve the problem. I just had to read the note a bit more carefully!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For other readers in this forum: You have to enter a new entry in table KBEROBJ, but make sure to leave the first field (Object) empty. This is the trick that makes it work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks anyway Alex!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Christer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Aug 2008 09:51:46 GMT</pubDate>
    <dc:creator>ChrLid_Swe</dc:creator>
    <dc:date>2008-08-19T09:51:46Z</dc:date>
    <item>
      <title>Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818762#M918422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is it possible to create a role and pass a variable to the authorization data?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to create a cost center inquiry role that allows an end user access to their own cost center, but to no other cost center.  Obviously, this needs to vary for each end user.&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;Margaret&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 May 2008 19:02:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818762#M918422</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-23T19:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818763#M918423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Margaret,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What system/s do you need this in?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In BW auth variables are a standard feature &amp;amp; you can achieve this without too much trouble.&lt;/P&gt;&lt;P&gt;In R/3 is it much, much harder &amp;amp; involves significant changing of standard code just for the usual transactions.  Unless you have £'000s to available then I would not recommend going down this route.  I would add to that and say that unless absolutely necessary I would not even consider granular cost centre security.  There are enough flaws in the implementation of that part of the auth concept to cause you plenty of headaches!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Often value roles are used in this situation, unfortunately that's a role per cost centre which can be assigned to the user to give just those auths to support the more generic functional role giving the particular transactional access&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 May 2008 21:43:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818763#M918423</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-23T21:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818764#M918424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Is it possible to create a role and pass a variable to the authorization data?  &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; I am trying to create a cost center inquiry role that allows an end user access to their own cost center, but to no other cost center.  Obviously, this needs to vary for each end user.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Thanks,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Margaret&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you could manage to get your funkies to setup the cost-centers as a hierachy you will not face a probem, you could then access it using the org-levels (something with RESPAREA ...). if you proceed to setup one role and derive as many children as you need for your end-users, you would only have to adjust the org-level to the appropriate hierachy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2008 15:48:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818764#M918424</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-28T15:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818765#M918425</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;I just tried to convert the field RESPAREA to an Organizational level field, but it would not work. It would not convert correctly. I received the $ sign in front of it. But the field were never visible under the Org level field button.&lt;/P&gt;&lt;P&gt;Has anyone else experience from this?&lt;/P&gt;&lt;P&gt;(We are running ECC 6.0, SAP BASIS 700)&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;/Christer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Aug 2008 13:05:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818765#M918425</guid>
      <dc:creator>ChrLid_Swe</dc:creator>
      <dc:date>2008-08-15T13:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818766#M918426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Christer,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you use PFCG_ORGFIELD_CREATE (note 323817) and also follow note 698401 for the RESPAREA specific tasks?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am on ECC6/700 at my current client and set up RESPAREA as Org level OK with the guidance in 698401&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Aug 2008 13:17:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818766#M918426</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-15T13:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818767#M918427</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;Thanks for your answer!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, I did use the standard report PFCG_ORGFIELD_CREATE. But I can't find any reason to SAP note 698401 since everything is looking ok in the table. It looks just the way we want it.&lt;/P&gt;&lt;P&gt;Neither can I see any use of note 565436 since this should be in the system since way back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if you did any magic in table KBEROBJ. It is object K_CCA that is of most importance to us.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way there is no trace of field RESPAREA in table AGR_1252. So it is not converted correctly from the report.&lt;/P&gt;&lt;P&gt;Thanks for any additional input!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Christer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Aug 2008 15:30:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818767#M918427</guid>
      <dc:creator>ChrLid_Swe</dc:creator>
      <dc:date>2008-08-18T15:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818768#M918428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alex,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, note 698401 really did solve the problem. I just had to read the note a bit more carefully!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For other readers in this forum: You have to enter a new entry in table KBEROBJ, but make sure to leave the first field (Object) empty. This is the trick that makes it work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks anyway Alex!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Christer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2008 09:51:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818768#M918428</guid>
      <dc:creator>ChrLid_Swe</dc:creator>
      <dc:date>2008-08-19T09:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818769#M918429</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Christer,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just saw your earlier post, glad the KBEROBJ tweak worked for you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2008 10:01:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818769#M918429</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-19T10:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818770#M918430</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;There are always issues when it comes to reporting within Controlling, and I agree that granular checks are not ideal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, there is an exit that could possibly be used to solve some problems around checks for Cost Centres - namely COCCA001.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example this could be used to add a custom lookup against a table which maps users to cost centres. Although the challenge remains that standard auth checks will still apply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would only consider this if the requirement is absolutely necessary and as mentioned in previous posts I would avoid getting into hundreds of roles to control access.&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;Edited by: S Morar on Aug 20, 2008 2:14 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Aug 2008 10:47:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable/m-p/3818770#M918430</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-19T10:47:56Z</dc:date>
    </item>
  </channel>
</rss>

