What to Do Before Creating Channel Sales Users
When you create sales application users either in the UI or by importing them from a file, you not only provision the permissions the users need to do their jobs, but you also build the organization chart for your sales organization.
This means that you must set up not only the provisioning rules, but also the elements used to create the organization chart in the Resource Directory.
Each channel sales user must have:
-
A resource role
You must assign a resource role, a name describing the role each resource plays in the organization, to each channel sales user you create. Resource roles display right underneath user names in the resource directory and elsewhere in the UI. They are also used as the primary condition in the role provisioning rules
-
A resource organization
You must create a resource organization for every channel sales manager. Each individual contributor who is not a manager automatically inherits the manager's organization. The name of the resource organization need not be any formal department name, but you should avoid using manager names to accommodate hierarchy changes.
The resource organization hierarchy is built based on the management hierarchy you specify when you create your channel sales users. You must enter a manager for each user you create.
What Oracle Provides for You
Oracle provides you with the standard channel sales organization resource roles and the role provisioning rules that automatically assign users with the job roles and abstract roles required to do their job.
The following channel sales resource roles supplied by Oracle will trigger the automatic assignment of job and abstract roles:
-
Channel Account Manager
-
Channel Sales Manager
-
Channel Operations Manager
For each of the resource roles provided by Oracle, there is a corresponding job role with the same name.
For example, when you create a user as an employee with the provided Channel Sales Manager resource role, the application automatically provisions the Channel Sales Manager job role and the Resource abstract role. Because you are creating the user as an employee, the application also provisions the Employee abstract role.
If you are implementing your sales applications in a Global Single Instance environment, then Oracle does not provide these role-provisioning rules for you. You must create them manually.
The following table lists the channel sales role-provisioning rules provided by Oracle, the condition which triggers the provisioning, and the job and abstract roles the rule provisions. You can obtain a description of each job and abstract role from the Security Reference guide for sales applications.
|
Provisioning Rule Name |
Condition |
Job or Abstract Roles Provisioned |
|---|---|---|
|
Channel Operations Manager |
HR Assignment Status is Active Resource Role is Channel Operations Manager |
Channel OperationsManager Resource |
|
Channel Sales Manager |
HR Assignment Status is Active Resource Role is Channel Sales Manager |
Channel Sales Manager Resource |
|
Channel Account Manager |
HR Assignment Status is Active Resource Role is Channel Account Manager |
Channel Account Manager Resource |
Overview of Channel Sales Users Setup
Because you must specify the manager for each channel sales user you create, start creating users from the top of the channel sales hierarchy and work your way down.
You create channel sales users in the Create User page, which you open from the Manage Users work area. You can navigate to the work area by clicking the Users and Roles task in the Create Sales Users folder in the implementation project.
Since channel sales is a branch of your existing direct sales organization, the channel sales branch must be tied to the organizational hierarchy of your direct sales team. The following figure shows how a channel sales branch fits with the direct sales hierarchy of Vision Corp.
