<?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 3.5 and BI 7 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324313#M1537301</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dheeraj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our All query from BW 3.5 to BI 7 has been already migrated, we dont have problem in using query in BI7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now we are moving BW 3.5 Authorization to new Analysis authorization based on BI 7, in new Concept  do we have to have authorization variables in both 0COMP_CODE and 0SALESORG in the queries? as i have asked in my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Deepak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Oct 2010 08:19:33 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-10-05T08:19:33Z</dc:date>
    <item>
      <title>Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324311#M1537299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are in process of upgrading our BW 3.5 Authorization to BI 7 New&lt;/P&gt;&lt;P&gt;Analysis authorization. I have some query related to authorization&lt;/P&gt;&lt;P&gt;variable BW 3.5 and how to Use in BI 7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For an Example&lt;/P&gt;&lt;P&gt;In BW 3.5 concept, authorization is set on the info provideru2019s level.&lt;/P&gt;&lt;P&gt;For example in Cube ZBILL we have 0COMP_CODE and 0SALESORG in the&lt;/P&gt;&lt;P&gt;flow, but we chosen to only authorize on 0COMP_CODE , In this case, we&lt;/P&gt;&lt;P&gt;only have authorization variable on 0COMP_CODE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, in BW 7.0 concept, authorization is set on info object level.&lt;/P&gt;&lt;P&gt;On the example above, 0COMP_CODE and 0SALESORG becomes authorization&lt;/P&gt;&lt;P&gt;relevant.&lt;/P&gt;&lt;P&gt;How would that that impacts the maintenance of variables in the queries?i.e.: do we have to have authorization variables in both 0COMP_CODE and&lt;/P&gt;&lt;P&gt;0SALESORG in the queries?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking forward for your suggestion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Deepak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Oct 2010 06:58:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324311#M1537299</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-05T06:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324312#M1537300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Deepak ,&lt;/P&gt;&lt;P&gt;Below is the required information on migration of queries &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using Queries&lt;/P&gt;&lt;P&gt;Both versions (SAP BW 3.x and SAP NetWeaver 2004s) of Queries could be used in both versions of BEx Tools and runtimes&lt;/P&gt;&lt;P&gt;Samples&lt;/P&gt;&lt;P&gt;u2013 Queries (SAP BW 3.x) could be used without change in BEx Web Application &lt;/P&gt;&lt;P&gt;Designer (SAP NetWeaver 2004s)&lt;/P&gt;&lt;P&gt;u2013 SAP NetWeaver 2004s Queries could be used in BEx Analyzer (SAP BW 3.x)&lt;/P&gt;&lt;P&gt;Process of Migration&lt;/P&gt;&lt;P&gt;Save Query with SAP NetWeaver 2004s BEx Query Designer&lt;/P&gt;&lt;P&gt;Possible problem: reusable objects (structures, key figures, variables) might also get new version&lt;/P&gt;&lt;P&gt;Other Queries using these reusable objects could be only opened with SAP NetWeaver 2004s BEx Query Designer&lt;/P&gt;&lt;P&gt;See Note 949330 about Query backup &amp;amp; restore&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;Dheeraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Oct 2010 07:50:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324312#M1537300</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-05T07:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324313#M1537301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dheeraj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our All query from BW 3.5 to BI 7 has been already migrated, we dont have problem in using query in BI7.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now we are moving BW 3.5 Authorization to new Analysis authorization based on BI 7, in new Concept  do we have to have authorization variables in both 0COMP_CODE and 0SALESORG in the queries? as i have asked in my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Deepak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Oct 2010 08:19:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324313#M1537301</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-05T08:19:33Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324314#M1537302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepak,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With BI 7 you no longer have the option of selectively checking an authorization relevant object for an infocube. You can replicate the same behaviour by creating an authorization object with both 0COMP_CODE and 0SALESORG along with 0TCAIPROV Restrict on existing values for 0COMP_CODE, 0TCAIPROV to ZBILL and give full authorization (*) to 0SALESORG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using  0TCAIPROV in the authorization ensures that these restriction are only applicable for the particular cube. To ensure the success of this design, you must make it a point of not maintaining 0TCAIPROV as * in other analysis authorizations with either of 0COMP_CODE or 0SALESORG. This should allow you to use your queries without change&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The other option, as you yourself mentioned, is to restrict with authorization variables for both the infoobjects while maintainaing actual authorized values for them in the analysis auths. Hope this helps!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aninda&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Oct 2010 14:03:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324314#M1537302</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-05T14:03:56Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324315#M1537303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Aninda for mail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in relation to my earlier question i have another doubt. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For one User I was doing testing for Query ZZABC40 which runs on&lt;/P&gt;&lt;P&gt;Multiprovider ZABC, Multiprovider ZABC is checked only&lt;/P&gt;&lt;P&gt;on company code ( in RSSM) but when I am running the Query in BI 7 setup its&lt;/P&gt;&lt;P&gt;failing for Company code and Sales org ( for value :,) .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my question is why its just checking for Sales org where as in multiprovider there are some other Auth objects available like Profit Center but they are not checked while running the query  ZZABC40.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is bit hard for me to&lt;/P&gt;&lt;P&gt;understand why itu2019s just checking sales org and why need value Colon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for Sales org and Comp code already required value are available in&lt;/P&gt;&lt;P&gt;Analysis authorization ( CC as 1150 and Sales org as 1150 and 1151),&lt;/P&gt;&lt;P&gt;The same query working in Production  with 3.5 concept.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(I know its works when i add both the missing field as : in my analysis authorization, but this doesnt help me in understanding how it works. I have also gone through SAP note 0001140831, but still not clear.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you share me how to proceed in sitiation like this.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="----------------------------" /&gt;&lt;P&gt;RSECADMIN Log----&lt;/P&gt;&lt;HR originaltext="-----" /&gt;&lt;P&gt;Subselection (Technical SUBNR) 0   &lt;/P&gt;&lt;P&gt;Supplementation of Selection for Aggregated Characteristics &lt;/P&gt;&lt;P&gt;  Check Added for Aggregation Authorization:     0COMP_CODE   &lt;/P&gt;&lt;P&gt;  Check Added for Aggregation Authorization:     0SALESORG   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Authorizations missing for aggregation (":")   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Char.  ZVCHCCSO  &lt;/P&gt;&lt;P&gt;0COMP_CODE    I EQ 1150    &lt;/P&gt;&lt;P&gt;0SALESORG    I EQ 1151    &lt;/P&gt;&lt;P&gt;  -&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Deepak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Oct 2010 11:29:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324315#M1537303</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-06T11:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324316#M1537304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepak,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Colon(&lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt; is the minimum authorization value that is needed for ALL authorization relevant characteristic in an infoprovider which are not restricted at the query level. Off course you can restrict the characteristic to actual authorised values or give full access (*).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your query exists in production (BW 3.5) as only company code is checked for the cube in RSSM and actual values are maintined for it through reporting authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In BW, in addition to CC you need to maintain authorisation for sales org as well as you do not have the option of selectively checking objects for cubes. To check whether profit center should be checked look at the infoobject for profit center in RSD1. Is it marked as auth relevant under the Business Explorer tab? If not you need not maintain it in your authorisations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aninda&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Oct 2010 05:10:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324316#M1537304</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-08T05:10:47Z</dc:date>
    </item>
    <item>
      <title>Re: Authorization variable 3.5 and BI 7</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324317#M1537305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Aninda for Reply.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Oct 2010 14:35:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-variable-3-5-and-bi-7/m-p/7324317#M1537305</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-17T14:35:31Z</dc:date>
    </item>
  </channel>
</rss>

