Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

BI Auth objects

Former Member
0 Kudos

hello all,

I have a question on AGGREGATED authoisation

Why is it for authoirsaiton NOT to fail i ahve to add to little colans?

I dont know why this is?

aggregated?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Aggregation authorization ("colon authorization") to view the values of an authorization-relevant characteristic in aggregated form.

Example:

The calendar year (0CALYEAR) characteristic is authorization-relevant and is contained in the InfoProvider that is in use. You defined a query as follows:

1. 0CALYEAR is in the free characteristics (not in the drilldown) without any selections (or)

2. 0CALYEAR does not exist in the query at all.

In both cases, no 0CALYEAR values are displayed in the query. Also, the query is not restricted to any 0CALYEAR values. A colon is required for the authorization check in this situation.

7 REPLIES 7

Former Member
0 Kudos

Hi

Have a look at OSS notes 1140831 & 727354. They explain the aggregation.

Former Member
0 Kudos

Hi,

Aggreegation needs to add when the particular characteristics is not being used while executing query. But that char. is used somewhere in your query design.

Best Regards

Imran

Former Member
0 Kudos

Aggregation authorization ("colon authorization") to view the values of an authorization-relevant characteristic in aggregated form.

Example:

The calendar year (0CALYEAR) characteristic is authorization-relevant and is contained in the InfoProvider that is in use. You defined a query as follows:

1. 0CALYEAR is in the free characteristics (not in the drilldown) without any selections (or)

2. 0CALYEAR does not exist in the query at all.

In both cases, no 0CALYEAR values are displayed in the query. Also, the query is not restricted to any 0CALYEAR values. A colon is required for the authorization check in this situation.

0 Kudos

As said in the previous reply, When 0CALYEAR is not used in the query the key figure values in the query gets aggregated based on 0CALYEAR.

So you need authorization to display aggregated data.

Regards,

Jaya

0 Kudos

In the characteristics, a row was inserted and the value is : . This did not resolve the issue. All of the characteristics have the specific values assigned AND the : to allow authorization to aggregated data.

0 Kudos

For authorizations not to fail, it is good to provide aggregated authorization for all the characteristics to which you have restricted authorization.

Regards,

Jaya

0 Kudos

Hi Koserk,

: (colon) allows access only to particular aggregated data maintained for example it allows report(authorization) on all

sales areas only on aggregated level u2013 not on particular sales areas).