Showing results for 
Search instead for 
Did you mean: 


Former Member
0 Kudos

Hi All,

I have an authorizations issue and wondering if anyone has some insight on this. I am working on an authorizations scheme based on sales organization.

For instance, Sales Group is the sales rep and the sales office is the location. A salesman can sell into his own sales office as well as others. i.e. Rep A sold to Washington D.C (home office) as well as Seattle (another one).

Now in terms of authorizations, a manager needs to run a report on revenue and needs to see all revenue within his sales office as well as sales his reps have done for other offices. Which means the manager for Washington needs to see 1,000,000 sold into his office as well as the 200,000 sold into Seattle. To make things further complicated, he needs to see the dollars that other reps from other offices have sold into his office. The authoriations should restrict him from seeing the other amounts. e.g. Rep B from Seattle sold 30,000 of the 1,000,000 into Washington. The manager should see the rep and only 30,000 and not the rest of his revenue.

So far I have tried various ways using analysis authorizations but the only way to get the "OR" statement is to use virtual characteristics. I would like to avoid this due to performance reasons.

Accepted Solutions (0)

Answers (1)

Answers (1)

Active Contributor
0 Kudos

Hi Eugene,

I reckon this is not an issue of the authorization, yet of the query design.

I doubt that you will be able to design a query that shows the values in the desired fashion.

In addition, why do you want to achieve the feat by using virtual characteristics. As long as you do not access the database (ie perfrom only calculation in the BAdI), you should not be penalized too much in the performance area. I would at least give it a go.


SAP NetWeaver BI Organisation

Former Member
0 Kudos

Hi Andreas,

Thank you for the confirmation. I already implemented the BAdI and the performance has decreased although not by much.

You are right it is mostly a query problem and a virtual characteristic did work along with an authorization variable to restrict the data.