Roles, Permissions and Data Access Control
Working with simulations and their private scenarios requires specific roles, permissions, as well as data access rights.
Simulations can be accessed by users with a planning professional license or planning standard license.
Before creating a simulation, set up the model involved. For more information, refer to Create a New Model.
To work with simulations, you'll need a role with permissions for the Compass Simulation object. For background information, refer to Privileges and Permissions.
The following permissions apply to users with planning licenses:
| Permission | Description | Standard roles | License requirement |
|---|---|---|---|
|
Create |
Lets you create simulations. |
Admin, Modeler, Planner Reporter, Viewer |
SAP Analytics Cloud for Planning, professional edition or standard edition |
|
Read |
Lets you open the compass start page and open simulations in the designer. Within a simulation, it also lets you open and view private scenarios created by you as well as public scenarios. This permission is also required to maintain private scenarios, including creating private scenarios, configuring drivers, running private scenarios, adding comparison scenarios, and changing case settings. |
Admin, Modeler, Planner Reporter, Viewer |
SAP Analytics Cloud for Planning, professional edition or standard edition |
|
Update |
Lets you edit the name and description of existing simulations. |
Admin, Modeler, Planner Reporter, Viewer |
SAP Analytics Cloud for Planning, professional edition or standard edition |
|
Delete |
Lets you delete simulations. |
Admin, Modeler, Planner Reporter, Viewer |
SAP Analytics Cloud for Planning, professional edition or standard edition |
|
Maintain |
Lets you publish private scenarios to create public scenarios and delete public scenarios. |
Admin, Modeler, Planner Reporter, Viewer |
SAP Analytics Cloud for Planning, professional edition or standard edition |
To carry out specific tasks for simulations and their scenarios, you may also need permissions for the models involved, as well as access to the model data.
|
Compass simulation permissions |
Model permission |
Model data access |
|||
|---|---|---|---|---|---|
|
Task |
Create |
Read |
Maintain |
Read |
Read |
|
Create a simulation from the compass start page |
X |
X |
X |
||
|
Create a simulation from a table data cell |
X |
X |
X |
||
|
Create a private scenario |
X |
X |
|||
|
Configure driver settings of a private scenario |
X |
X |
* |
||
|
Run a private scenario |
X |
X |
** |
||
|
View and check the simulation results of a private scenario |
X |
X |
*** |
||
|
View and change case settings |
X |
||||
|
View and maintain comparison scenarios (private scenarios) |
X |
X |
*** |
||
|
Create a public scenario |
X |
X |
X |
||
|
View and check the simulation results of a public scenario |
X |
X |
**** |
||
|
View and maintain comparison scenarios (public scenarios) |
X |
X |
**** |
||
*For any driver, its current baseline value that is displayed corresponds to the model data you have read access to.
**For any driver that has its baseline value used in the simulation calculation, the specific baseline value used corresponds to the model data you have read access to.
***You should have read access to the model data that corresponds to the target defined by its filters. For example, if the target you want to simulate is revenue of Europe for 2025, you should have read access to this slice of the model data ("Revenue", "Europe", "2025").
****You don't need read access to the model data that corresponds to the target defined by its filters in a public scenario. All the content of a public scenario is visible to any user with access to the simulation. Note that the value of the current baseline shown for each driver in a public scenario still corresponds to the model data you have read access to.
For more information on data acess control, see Set Up Data Access Control.
Example
Let's use this example to demonstrate how data access rights can affect the simulation results in private scenarios.
Two users want to simulate the "Revenue" of all phones and "Price" and "Volume" are identified as drivers based on this formula: Revenue = Price * Volume
The fact data for the volume of different phones in the model is as follows:
|
Volume |
|
|
Phone |
120 |
|
Phone A |
20 |
|
Phone B |
40 |
|
Phone C |
60 |
User A, with read access to all different types of phones, can see what is shown above in its entirety.
User B, who only has read access to Phone A and Phone B, can see the fact data below:
|
Volume |
|
|
Phone |
60 |
|
Phone A |
20 |
|
Phone B |
40 |
|
Phone C |
– |
In a specific iteration of a scenario run, the generated randomized value for driver "Volume" are 240.
For User A, this randomized value is disaggregated proportionally to different types of phones:
|
Volume |
|
|
Phone |
240 |
|
Phone A |
40 |
|
Phone B |
80 |
|
Phone C |
120 |
For User B, this randomized value is disaggregated proportionally to Phone A and Phone B only.
|
Volume |
|
|
Phone |
240 |
|
Phone A |
80 |
|
Phone B |
160 |
|
Phone C |
– |
In this example, we can see that different data access rights will lead to different data disaggregation results, in turn leading to different simulation results for a shared target.
Permissions for Simulations in the File Repository
The permissions for simulations depends on a combination of role-based permission for simulations and folder-based permissions in the file repository.
In order to have certain permissions for the simulations in a file repository folder, you need to have specific corresponding permissions for simulations that are assigned by the system administrator outside of the file repository, on the Roles page. For more information, see Create Roles and Privileges and Permissions.
If you do not have the required role-based permissions for simulations, then your permissions in the file repository for simulations are restricted.
There are different possible combinations of role-based permissions and how they impact folder-based permissions in the file repository. Two examples are simulation designer and simulation user.
If you are a simulation designer with full permissions for your role, assigned by the system administrator, then you will have full permissions for simulations you access in the file repository.
|
Create |
Read |
Update |
Delete |
Maintain |
|
|---|---|---|---|---|---|
|
Compass Simulation |
X |
X |
X |
X |
X |
|
Create files |
Read |
Copy |
Update |
Delete |
|
|---|---|---|---|---|---|
|
Compass Simulation |
X |
X |
X |
X |
X |
In the second example, if you are a simulation user with Read and Maintain permissions assigned by the system administrator for compass simulations, you have Read permission in the file repository. This permission combination does not allow you to make changes to compass simulations, but you can maintain their private and public scenarios, including creating private and public scenarios, configuring drivers, running private scenarios, adding comparison scenarios, and changing case settings.
|
Create |
Read |
Update |
Delete |
Maintain |
|
|---|---|---|---|---|---|
|
Compass Simulation |
X |
X |
|
Create files |
Read |
Copy |
Update |
Delete |
|
|---|---|---|---|---|---|
|
Compass Simulation |
X |
X |