<?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: BI Auth objects in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280489#M1388170</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Aggregation authorization ("colon authorization") to view the values of an authorization-relevant characteristic in aggregated form. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example: &lt;/P&gt;&lt;P&gt;The calendar year (0CALYEAR) characteristic is authorization-relevant and is contained in the InfoProvider that is in use. You defined a query as follows:&lt;/P&gt;&lt;P&gt;1. 0CALYEAR is in the free characteristics (not in the drilldown) without any selections  (or) &lt;/P&gt;&lt;P&gt;2. 0CALYEAR does not exist in the query at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In both cases, no 0CALYEAR values are displayed in the query. Also, the query is not restricted to any 0CALYEAR values. A colon is required for the authorization check in this situation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Nov 2009 07:33:09 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-11-16T07:33:09Z</dc:date>
    <item>
      <title>BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280486#M1388167</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;I have a question on AGGREGATED authoisation&lt;/P&gt;&lt;P&gt;Why is it for authoirsaiton  NOT to  fail i ahve to add to little colans?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont know why this is?&lt;/P&gt;&lt;P&gt;aggregated?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Nov 2009 13:15:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280486#M1388167</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-14T13:15:36Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280487#M1388168</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;Have a look at OSS notes 1140831 &amp;amp; 727354.  They explain the aggregation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Nov 2009 15:25:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280487#M1388168</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-14T15:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280488#M1388169</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;Aggreegation needs to add when the particular characteristics is not being used while executing query. But that char. is used somewhere in your query design.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Imran&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 15 Nov 2009 05:45:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280488#M1388169</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-15T05:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280489#M1388170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Aggregation authorization ("colon authorization") to view the values of an authorization-relevant characteristic in aggregated form. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example: &lt;/P&gt;&lt;P&gt;The calendar year (0CALYEAR) characteristic is authorization-relevant and is contained in the InfoProvider that is in use. You defined a query as follows:&lt;/P&gt;&lt;P&gt;1. 0CALYEAR is in the free characteristics (not in the drilldown) without any selections  (or) &lt;/P&gt;&lt;P&gt;2. 0CALYEAR does not exist in the query at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In both cases, no 0CALYEAR values are displayed in the query. Also, the query is not restricted to any 0CALYEAR values. A colon is required for the authorization check in this situation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2009 07:33:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280489#M1388170</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-16T07:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280490#M1388171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As said in the previous reply, When 0CALYEAR is not used in the query the key figure values in the query gets aggregated based on 0CALYEAR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you need authorization to display aggregated data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jaya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Dec 2009 08:39:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280490#M1388171</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-07T08:39:03Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280491#M1388172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the characteristics, a row was inserted and the value is &lt;STRONG&gt;:&lt;/STRONG&gt; . This did not resolve the issue. All of the characteristics have the specific values assigned AND the &lt;STRONG&gt;:&lt;/STRONG&gt;  to allow authorization to aggregated data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Dec 2009 09:08:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280491#M1388172</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-07T09:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280492#M1388173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For authorizations not to fail, it is good to provide aggregated authorization for all the characteristics to which you have restricted authorization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jaya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2010 05:50:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280492#M1388173</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-20T05:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: BI Auth objects</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280493#M1388174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Koserk,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;: (colon)&lt;/STRONG&gt; allows access only to particular aggregated data maintained for example it allows report(authorization) on all&lt;/P&gt;&lt;P&gt;sales areas only on aggregated level u2013 not on particular sales areas).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2010 06:20:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-auth-objects/m-p/6280493#M1388174</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-01-20T06:20:41Z</dc:date>
    </item>
  </channel>
</rss>

