cancel
Showing results for 
Search instead for 
Did you mean: 

SAC -> Live Data Connection -> BO 4.3 Universe: Security Configuration

bernhard_keimel
Active Participant
0 Kudos
767

Scenario:

  • BO 4.3 Platform, users either refresh or also create reports based on universes. Security setup to manage this.
  • SAC Users need to use BO Universes using LDC to create models or just use existing models without ability to create models
  • Users being able to create models should then only use specific universes designed for the SAC LDC, NOT other universes they could use in BO/Webi

The Problem is that i cannot find a security setup that only show the SAC-enabled universes for users in the SAC, hiding the other universes he has permissions in BO. If a user is either SAC or BO enabled for universe usage, it is not a problem. Also hiding the SAC enabled universes in BO.

But how could it be possible to restrict in SAC the list of universes to the SAC enabled ones? A User would have granted both SAC universe permissions and BO universe permissions. I would need something like a Category assigned, like it is possible for Webi Documents to be used as datasource in SAC, but for universes that does not exist.

Is anyone aware of a solution to this problem?

Addition: i added an Improvement Request for this: Improvement Request Details - Customer Influence (sap.com)
feel free to vote 🙂

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Greetings bernhard.keimel,

This is how you can do it on the BI end.

Giving BI users access to universes

Hope that helps to address your topic.

Cheers,

Luis

bernhard_keimel
Active Participant
0 Kudos

Hello Luis,

thank you, but this is not my point, this is done and working

The problem is that it is working "too good". I also see universes that i do not want to see in the SAC. This is because the user connecting to BO via LDC also has the same rights on these universes because he accesses them in BO. But when he uses the SAC, i do NOT want him to see those universes because they are not setup for the SAC use and should NOT be accessed by SAC.

Former Member

Understood bernhard.keimel,

Let's see if we find something else. 🙂