Setting Up Sales Planning Cloud Security
Setting Up Sales Planning Cloud Security
Background
Planning implements several security layers:
This tutorial includes an overview of each security layer, and shows you how to manage access control and
access permissions in Oracle Sales Planning Cloud.
An Oracle Sales Planning Cloud Service instance allows you to deploy and use one
application. To deploy another application, you must request another Oracle Sales Planning
Cloud instance or remove the current application.
● Have Service Administrator access to Oracle Sales Planning Cloud. The instance should not have an
application created.
● Import the SalesPln application into your Oracle Sales Planning Cloud instance:
● If you haven't already, register for a free Oracle Cloud Customer Connect account so you can access the
required files.
● From this Idea page, download and extract the SPC_apps.zip file. The compressed file contains two
snapshots.
● Upload and import the SPC_BaseAdv.zip snapshot into your Oracle Sales Planning Cloud instance.
For more information on uploading and importing migration snapshots, refer to the
Administering Migration for Oracle Enterprise Performance Management Cloud
documentation.
Security overview
Oracle Identity Management
Single-sign on (SSO) and role-based security are managed by Oracle Identity Management, which defines a
security domain for each environment. After a successful sign-in, access to the service is determined by the role
assigned to the user.
Identity Domain
An identity domain controls the accounts of users who need access to environments. It also controls the features
that authorized users can access.
An Identity Domain Administrator creates and manages user accounts within an identity domain. The Account
Administrator, while activating the service, identifies a user who is granted the Identity Domain Administrator
role.
By default, each customer is allocated two environments of a service: test and production. The Identity Domain
Administrator uses the Security Page of My Services to manage the users who need access to these
environments, as well as managing users and their roles, configuring single sign-on, and setting up network
restricted access. While users are shared across test and production environments, they are provisioned
separately for each.
Users
Each user who needs to access an environment must have an account in the identity domain associated with the
environment.
To determine or limit what a user can do within an environment, you assign roles.
Predefined Roles
You can assign roles to a user to allow access to Oracle Cloud services (such as Oracle Sales Planning Cloud) that
have predefined roles defined in Oracle Identity Cloud Service.
Users must be assigned to predefined roles that grant them access to business functions and associated data.
Most Oracle Cloud services use a common set of four predefined functional roles to control access to service
environments. The access that a predefined role grants within an environment depends on the service type. Here
are the Oracle Sales Planning Cloud predefined roles:
● Service Administrator—Performs all functional activities, including granting roles to users. This role should be
granted to functional experts who need to create and administer the Sales Planning application and service
components.
● Power User—Views and interacts with data. This role grants high-level access to several functional areas
within an environment and should be granted to department heads and business unit managers, and
business users in charge of a region who need to control the approval process.
● User
● Enters data into forms and submits them for approval, analyzes forms using ad hoc features, controls
the ability to drill through to the source system
● Accesses and modifies (rename, delete) the Reports content stored in the Repository for which the user
has View, Modify, or Full Control permissions.
● Viewer—Views and analyzes data through forms and data access tools. Typically, this role should be assigned
to executives who need to view business plans during the budgeting process.
In Sales Planning's Access Control, you can assign roles at the application-level to enhance
the access rights of users. Privileges granted by a predefined role cannot be curtailed by roles
assigned at the application-level.
● Managing Groups
● Assigning Roles to a Group or a User
● Generating a Role Assignment Report for a User or Group
● Generating the Role Assignment Report For Your Environment
● Viewing the User Login Report
You can also set who can launch which rules: Launch and No Launch.
If a user inherits Launch permission to a rule by belonging to a group, and is also assigned No Launch
permissions by belonging to another group, the more restrictive No Launch assignment takes precedence.
You can set permissions for task lists: Assigned, Manage, Manage and Assign, None.
You can specify access permissions for users and groups. When you assign a user to a group, that user acquires
the group's access permissions. If an individual's access permissions conflict with those of a group the user
belongs to, user access permissions take precedence.
Inheriting Permissions
Instead of assigning access permissions to individual dimension members, you can use the more efficient
inheritance option to assign permissions to multiple members.
Assign access to individual members only on an exception basis. For example, for the North
America Sales group, you assign write access to North America and its descendants, and read
access to one of its children, the North America Headquarters entity.
You can specify an attribute that causes the children or descendants of that member to inherit its permissions.
Assigned permissions take precedence over inherited permissions. You can include or exclude the member from
the permissions setting.
1. Role-level security
Users with the Service Administrator role have permissions to all application elements.
2. For Power User and Planner user types, permissions that are specifically assigned to users.
3. Permission assignments that are acquired by belonging to a group.
If one member belongs to two groups with different permissions assigned to group members, the least
restrictive permission takes precedence. For example, if one group assigns the member Read permission and
another group assigns the same member Write permission, Write takes precedence. However if one of the
groups assigns no permission (None) to its members, None takes precedence over Read and Write.
Valid Intersections
You can define rules, called valid intersection rules, that filter cell intersections for users when they enter data or
select runtime prompts. For example, you can restrict product availability based on entities.
You can create valid intersection groups that contain multiple valid intersection rules.
After valid intersections are defined, cells containing invalid data are read-only. This restriction speeds the
planning process and optimizes the information available to users.
If the dimensions that are set in the valid intersection are found on the Page, the user will be presented only
with valid combinations in the member selector.
If the dimensions that are set with valid intersections are found on the column or row, the form designer can
suppress invalid intersections completely. When the suppression option isn't selected, invalid intersections are
set to read only.
This tutorial was developed using the Dark Blue theme. You can select a theme by clicking (Navigator), then
under Tools, click Appearance. For Theme, select a color option.
Opening Access Control
From the home page, click Tools, then Access Control.
Access Control is opened with Manage Groups displayed.
Managing Groups
Access Control lists the predefined roles as groups. Service users, who are assigned to predefined roles, are
listed in Access Control so that they can be added as group members.
You use Migration or EPM Automate commands to export and import groups.
Creating Groups
● Click (Move).
● From Available Users, click (Search) to display a list of users or filter the list by entering a search string,
and then clicking (Search).
● Click (Move).
Clicking Move, Move All, Remove, Remove All allows you to add or remove users to the
Assigned Users list.
6. Click Save.
7. In the Create Group message, click OK.
8. Click Close.
You cannot modify the names and description of predefined roles in Access Control.
You can modify group properties and assignments for groups that you created.
1. In Manage Groups, locate the group you created and click (Actions).
2. Select Edit.
3. Modify the name, description, assigned groups, and users in Edit Group.
4. Click Save.
5. In the Edit Group message, click OK.
6. Click Close.
Deleting Groups
1. In Manage Group, locate the group you want to delete and click (Actions).
2. Select Delete.
3. In the Delete Group prompt, click Yes.
4. In the Delete Group message, click OK.
Managing Users
You can manage a user's group assignment in Manage Users.
The users displayed in this tutorial may vary from the users displayed in your Sales Planning
application. The users listed will depend on the users you have added and provisioned in
Oracle Identity Manager.
You create users, modify user properties, and delete users in Oracle Identity Management.
● Click (Search) to display a list of available groups or filter the list by entering a search string, and then
clicking (Search).
● From Available Groups, select groups.
● Click (Move).
Clicking Move, Move All, Remove, Remove All allows you to add or remove assignments.
4. Click Save.
5. In the Edit User message, click OK.
6. Click Close.
Assigning Application Roles
Service Administrators can grant application-specific roles and data grants to users and to groups created and
managed in Access Control.
Application Roles
Only the users who are assigned to predefined roles can be assigned application-level roles to enhance the
access they have to perform tasks within Planning.
4. From the Available Application Roles, select the roles you want to assign.
5. Click (Move).
Clicking Move, Move All, Remove, Remove All allows you to add or remove assignments.
6. Click OK.
5. Click (Move).
Clicking Move, Move All, Remove, Remove All allows you to add or remove assignments.
6. Click OK.
7. In the Assign Application Roles to Group message, click OK.
8. Click Cancel.
To generate the Role Assignment Report in Access Control, click Role Assignment Report.
The report lists the predefined roles and Planning application roles assigned to the user.
Click Export to CSV to export the Role Assignment Report as a comma separated value file.
To generate the User Login Report in Access Control, click User Login Report.
Click Export to CSV to export the User Login Report as a comma separated value file.
To generate the User Group Report in Access Control, click User Group Report.
Click Export to CSV to export the User Group Report as a comma separated value file.
If you omit or clear the Apply Security setting, all users can access the dimension's members. By default, the
Account, Entity, Scenario, and Version dimensions are enabled for access permissions. Optionally, you can
enable this option for Period, Years, and Custom dimensions.
5. After selecting a cube, click the name of a dimension you want to view.
In this example, the Product dimension in the OEP_GSP cube is opened in Edit Member Properties.
7. Click Permissions.
8. Perform a task:
● To add permissions, click Add User/Group, and then select from the list of available users and groups.
● Click OK, then click Close.
● To edit the type of permissions, select an option:
● Click Read to allow the selected users and groups to view the artifact or folder in the listing, but not
allow them to create, edit, or delete the artifact or folder information.
● Click Write to allow the selected users and groups to view the artifact or folder in the listing, and to
create, edit, or delete the artifact or folder information.
● Click None if you don't want the selected users or groups to view the artifact or folder in the listing.
● Optional: Select a relationship. For example, select Children to assign access to children of the selected
member.
● To remove permissions, for the selected user or group, click (Delete).
9. When finished adding permissions to users and groups, click Save.
10. In the Information message, click OK.
11. Click Cancel to close Assign Permissions.
12. In Edit Member Properties, click Save.
13. Click Cancel to close Edit Member Properties.
3. Click (Actions) next to the artifact or folder and select Assign Permission.
4. In Assign Permission, click Permissions.
5. Perform a task:
● To add permissions, click Add User/Group, and then select from the list of available users and groups.
● Click OK, then click Close.
● To edit the type of permissions, select an option:
● Click Read to allow the selected users and groups to view the artifact or folder in the listing, but not
allow them to create, edit, or delete the artifact or folder information.
● Click Write to allow the selected users and groups to view the artifact or folder in the listing, and to
create, edit, or delete the artifact or folder information.
● Click None if you don't want the selected users or groups to view the artifact or folder in the listing.
● To remove permissions, for the selected user or group, click (Delete).
6. When finished adding permissions to users and groups, click Save.
7. In the Information message, click OK.
8. Click Save.
9. Click Cancel to close Assign Permissions.
Rules
1. Return to the home page. Click (Home).
2. From the home page, click Rules.
Business Rules are displayed. you can filter the list by cube and rule type.
3. For a rule or rule folder, click (Permission), and then select Assign Permission.
4. In Assign Permission, click Permissions.
5. Perform a task:
● To add permissions, click Add User/Group, and then select from the list of available users and groups.
● Click OK, then click Close.
● To edit the type of permissions, select an option:
● Click Launch to allow the selected users and groups to launch the selected rules.
● Click No Launch to prevent the selected users and groups from launching the selected rules.
● To remove permissions, for the selected user or group, click (Delete).
Task Lists
To complete the steps in this section, you must create a task list. For steps in creating task
lists, see the Managing Task Lists in Planning section of the Designing Forms and Managing
Task Lists in Planning tutorial.