Standard authorization concept versus analysis authorizations

[Former Member]

Hi

I am bit confused about the necessity of maintaining both.

Example:

I have designed an analysis authorizations for CO (Controlling), named CO_001:

InfoProvider: 0COOM_C02

Thereafter I have put the authorization object S_RS_AUTH into a role (standard authorization object) with CO_001 as value in BIAUTH.

Is there still a need to maintain authorization objects for Business Explorer or Business Planning, like:

S_RS_COMP (limiting to the InfoProvider mentioned in the analysis authorization)

S_RS_PLSE (limiting to a special aggregation level of the appropriate InfoProvider mentioned in the analysis authorization)

What happens when there is no limitations maintained in the role for these auth objects, "*"?

Which concepts dominates the other one?

Thanks

BEO

[shivraj_singh2 · Accepted solution]

BEOplanet

S_RS_COMP is still needed.

If you mention (*) in S_RS_COMP

and 0COOM_C02 in AA

user can run queries only for 0COOM_C02.

Regards

[Former Member · Accepted solution]

Singh

This means that S_RS_COMP must be used and may be filled by (*).

Query authorization is controlled by AA.

What will happen if AA is maintained by Cube 0COOM_C02 and S_RS_COMP has 0PA_C01?

Queries will only work for 0COOM_C02 (and 0PA_C01)?

Regards

BEO

[Former Member · Accepted solution]

Hi BEOplanet,

S_RS_COMP will give you access to the Infoprovidor in BEx so this will be access level security.

Then Analysis authorization will give you the data level security within the infoprovidor (like what data you can see within the infoprovidor)

There fore you need to maintain both S_RS_COMP and Analysis Authorizations.

To your question ,if you have maintained the cube 0COOM_C02 in Analysis Authorization and S_RS_COMP has only 0PA_01 then the Query will fail since you dont have access to the cube 0COOM_C02 in S_RS_COMP.

Regards,

Karthik.