<?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 SAP BI authorization relevant in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577967#M861303</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I tried to create a custom authorization object for an infoobject otcaactivity (just for eg) .Before that I used RSD1 to make that infobject authorizartion relevant.But after that I inserted the infobject which is made as auth.relevant to the custom object and tried to assign value for the intervals.I got an message as the characteristic value is not authorization relevant...why is that?I tried in sand box..is it any way related to info cube which is not yet created for the particular info object in the sand box thats the reason I get error message ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Whats the reason to secure characteristics and key figure values?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Mar 2008 03:14:52 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-25T03:14:52Z</dc:date>
    <item>
      <title>SAP BI authorization relevant</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577967#M861303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I tried to create a custom authorization object for an infoobject otcaactivity (just for eg) .Before that I used RSD1 to make that infobject authorizartion relevant.But after that I inserted the infobject which is made as auth.relevant to the custom object and tried to assign value for the intervals.I got an message as the characteristic value is not authorization relevant...why is that?I tried in sand box..is it any way related to info cube which is not yet created for the particular info object in the sand box thats the reason I get error message ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Whats the reason to secure characteristics and key figure values?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2008 03:14:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577967#M861303</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-25T03:14:52Z</dc:date>
    </item>
    <item>
      <title>Re: SAP BI authorization relevant</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577968#M861304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have to activate the business content related to authorizations  before even creating custom auth object.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You hv to make the following authorization relevant and this is mandatory for BI 7.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;0TCAACTVT&lt;/P&gt;&lt;P&gt;0TCAIPROV&lt;/P&gt;&lt;P&gt;0TCAVALID&lt;/P&gt;&lt;P&gt;0TCAKYFNM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After you complete the above steps..then you can try creating your custom auth. Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2008 03:44:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577968#M861304</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-25T03:44:00Z</dc:date>
    </item>
    <item>
      <title>Re: SAP BI authorization relevant</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577969#M861305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Activating business content mean making authorization relevant? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For BW3.5 there is no need of the mandatory info objects?(0TCAACTVT ,0TCAIPROV ,0TCAVALID ,0TCAKYFNM)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whats the difference between securing through reporting authorization object and securing through BI specific object??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2008 12:36:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577969#M861305</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-25T12:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: SAP BI authorization relevant</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577970#M861306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please check this note 820183. &lt;/P&gt;&lt;P&gt;It is best practice to use these special characteristics( 0TCAACTVT ,0TCAIPROV ,0TCAVALID  &lt;/P&gt;&lt;P&gt;) in your RS object.( not mandatory)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You still have to use the RS objects like S_RS_COMP, S_RS_SCOMP1,etc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2008 18:30:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-bi-authorization-relevant/m-p/3577970#M861306</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-25T18:30:11Z</dc:date>
    </item>
  </channel>
</rss>

