Planning changes to Authorizations for migration to V7

[Former Member]

Hello Experts,

I researched the new authorization concept but I have 2 basic questions:

1) Do Bex reports need to have authorization variables defined on Authorization Relevant Infoobjects to force a selection within the set of authorized rows. From the PPTs I downloaded from SDN, it seems that this is no longer necessary and that the security engine will prevent the display of non authorized rows?

2) We intend to ugrade to v7 but continue to deploy V3.5 Infocubes under V7. Assuming we do not change the default and work with the new authorization concept, will the old, non upgraded infocubes be subject to the old concept authorization objects or will the new authorization concept apply to these cubes?

[Former Member]

David,

The answer to your first question is : If you need to restrict the value for the relevant Infoobject then you need to create a Authorization variable in the BEX Queries . If you have defined your Info object as Authorization relevant and if that object is a part of the query ( Not used to restirct by any values), then in your analysis authorization object you have to have that Infoobject with "*" otherwise it will give authorization error.

When you upgrade to 3.5 to BI 7 and still used the old transfer rules, update rules and old authorization functionality will still work. But it is recommended that you migrate it BI 7.

Hope it helps,

Cheers,

Balaji