<?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: Security Design Issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028712#M1609656</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;Its simple. All you need to do is, identify the infoobject that holds this data and make it authorization relevant. When an infoobject is authorization relevant, users need authorization at the data level, which you can provide using Analysis authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your BI guy may help you in identifying the infoobjects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raghu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Aug 2011 18:04:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-08-02T18:04:27Z</dc:date>
    <item>
      <title>BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028707#M1609651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We need to design a solution for BI-Security. The requirement is to provide only a specific set of users (based on Org. Unit) to have access to Annual Salary+Employee Attributes, whereas all other users need to access only Employee Attributes.&lt;/P&gt;&lt;P&gt;Any kind of pointers will help &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 16:51:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028707#M1609651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-01T16:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028708#M1609652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sudhir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Identify the Info Cubes under which the data is available and provide authorization in S_RS_COMP and S_RS_COMP1 (use the bottom up approach) and ensure that you provide complete access till the Top level Info provider.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further restrictions can be applied using Analysis authorizations, if you are on BI 7.0 and later versions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raghu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 17:44:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028708#M1609652</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-01T17:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028709#M1609653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Raghu, we are on BI 7.0 and planning to use Analysis Authorization. Do you any suggestion on how to approach it using Analysis Authorization.&lt;/P&gt;&lt;P&gt;~Sudhir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 18:34:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028709#M1609653</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-01T18:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028710#M1609654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have pasted an EXample:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Employee 	Annual Salary	Organization Unit Key	Payscale Area&lt;/P&gt;&lt;P&gt;11	500	Org_1	AA&lt;/P&gt;&lt;P&gt;22	1500	Org_2	AA&lt;/P&gt;&lt;P&gt;33	2000	Org_3	BB&lt;/P&gt;&lt;P&gt;44	2500	Org_4	CC&lt;/P&gt;&lt;P&gt;			&lt;/P&gt;&lt;P&gt;			&lt;/P&gt;&lt;P&gt;Person has access to All Data:			&lt;/P&gt;&lt;P&gt;Employee 	Annual Salary	Organization Unit Key	Payscale Area&lt;/P&gt;&lt;P&gt;11	500	Org_1	AA&lt;/P&gt;&lt;P&gt;22	1500	Org_2	AA&lt;/P&gt;&lt;P&gt;33	2000	Org_3	BB&lt;/P&gt;&lt;P&gt;44	2500	Org_4	CC&lt;/P&gt;&lt;P&gt;Note: He/She should  be able to see ALL data.			&lt;/P&gt;&lt;P&gt;			&lt;/P&gt;&lt;P&gt;			&lt;/P&gt;&lt;P&gt;Person has NO access to Annual Salary for Payscale Area = AA 			&lt;/P&gt;&lt;P&gt;Employee 	Annual Salary	Organization Unit Key	Payscale Area&lt;/P&gt;&lt;P&gt;11	 	Org_1	AA&lt;/P&gt;&lt;P&gt;22	 	Org_2	AA&lt;/P&gt;&lt;P&gt;33	2000	Org_3	BB&lt;/P&gt;&lt;P&gt;44	2500	Org_4	CC&lt;/P&gt;&lt;P&gt;Note: He/She should NOT be able to see Salary of Payscale Area = AA&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Aug 2011 19:11:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028710#M1609654</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-01T19:11:49Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028711#M1609655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sudheer,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    I would recommend you to use Generation feature of Rsecadmin, in this you can directly connect your BI system to HR system, based on their access in HR system , Access can be generated in BI system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please go through below links from help.sap.com for more information on generation feature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Single value DSO uses this SAP standard template&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw73/helpdata/en/46/8bbd2738fc429ee10000000a1553f7/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw73/helpdata/en/46/8bbd2738fc429ee10000000a1553f7/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hierarchy DSO uses this SAP standard template&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw73/helpdata/en/46/8bbe3b38fc429ee10000000a1553f7/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw73/helpdata/en/46/8bbe3b38fc429ee10000000a1553f7/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps you !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ananth&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Anantharama Shivashankar on Aug 2, 2011 4:31 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2011 14:31:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028711#M1609655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-02T14:31:09Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028712#M1609656</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;Its simple. All you need to do is, identify the infoobject that holds this data and make it authorization relevant. When an infoobject is authorization relevant, users need authorization at the data level, which you can provide using Analysis authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your BI guy may help you in identifying the infoobjects.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raghu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2011 18:04:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028712#M1609656</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-02T18:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028713#M1609657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Raghu for the comments. We cannot make Annual-Salary as authorization relevant(being an Keyfigure-attribute in Employee). We have made Employee as Authorization relevant and added Annual-Salary as well the Analysis Authorization object, as we are planning to populate the Employee values using userexit. &lt;/P&gt;&lt;P&gt;Just wanted to make sure that this is the right approach Or we can implement it via any other way as well.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;SC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2011 14:41:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028713#M1609657</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-03T14:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028714#M1609658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sudhir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;0TCAKYFNM&lt;/STRONG&gt; (if you want to restrict access to key figure)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can include this in the analysis authorization. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The alternative is as you mentioned to have a user exit. Both the approaches are okay.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raghu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2011 14:45:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028714#M1609658</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-03T14:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: BI: Security Design Issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028715#M1609659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Raghu,&lt;/P&gt;&lt;P&gt;SC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2011 20:42:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bi-security-design-issue/m-p/8028715#M1609659</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-08-04T20:42:23Z</dc:date>
    </item>
  </channel>
</rss>

