Browser version script Skip Headers

Oracle® Fusion Applications Incentive Compensation Implementation Guide
11g Release 1 (11.1.1.5.0)
Part Number E20381-01
Go to contents  page
Contents
Go to Previous  page
Previous
Go to previous page
Next

7 Common Applications Configuration: Define Resources for Incentive Compensation

This chapter contains the following:

Identifying Resources: Explained

Resource Directory: Explained

Resources: How They Work within a Team

Team Usage: Explained

Provisioning Security Roles: Explained

FAQs for Define Resources

Identifying Resources: Explained

The Identify Resources step in the Manage Resources task is only needed to identify an existing employee, contingent worker, or partner member as a resource. Usually they are identified as resource in the Manage Users task, or in the Partner Center. If you have created partner members or internal users in the system without making them resources, you can identify them as resources in the Identify Resources step. Until you identify employees, contingent workers, and partner members as resources, you cannot assign them work objects.

Note

Resources need not necessarily belong to an organization, nor do they need to have specific roles assigned. However, it is best to always associate resources with an organization either as managers or as members. Similarly resources should also have at least one role as part of their organization membership. When you identify users as resources, all you indicate is that these new resources can now be assigned work within the deploying company.

Resource Directory: Explained

The Resource Directory offers detailed information about all the resources within the deploying organization. The Resource Directory also enables you to find and communicate with other resources, and to network and collaborate with them.

Use the Resource Directory to perform the following tasks:

Resources: How They Work within a Team

You can include resources from different resource organizations to work together on a work object as members of the same resource team. You can also include entire resource organizations into a resource team. Generally what resources can do is controlled by their resource organization membership and their hierarchy. Resource teams provide a flexible way of bringing resources together without any organizational or hierarchy-based restrictions.

Assigning Resources to Teams

You can assign identified resources to teams and assign them roles within the team. Each resource can have a specific role within a team. Thus, a resource may play different roles in different teams.

Team Usage: Explained

You use teams to ensure optimal utilization of existing resources across the deploying company without changing their organizational membership and hierarchy. You can also use resource teams as a quick reference to a group of related resources. This simplifies resource assignment, and you can quickly assign an entire team to tasks in a single move. Team usage indicates the usage of a resource team. This simplifies further task assignment, ensuring that teams are assigned tasks that are associated with or related to their listed usages.

Provisioning Security Roles: Explained

Security role provisioning is the process of automating the provisioning and de-provisioning of security roles based on resource role assignment to resources. Once security roles are provisioned to resources, they can access the tasks and data enabled for the security role.

Difference between Resource Roles and Security Roles

Resource roles indicate who a person is to the deploying company. As such, resource roles are used for filtering resources and for generating reporting hierarchies in addition to being used to define security policies. A key difference between a security role and resource role is that a resource role may be assigned to a resource without a user account, while a security role can only be provisioned to a resource who has a user account. So while in some cases the resource role may be defined at the same granularity as the security role and used to automate security role provisioning, the resource role concept remains separate from security roles.

FAQs for Define Resources

What's the difference between a partner resource and an internal resource?

The main difference between an internal resource and a partner resource is the company for whom each works. While the internal resource is an employee or contingent worker of the deploying company, the partner resource is an employee of the partner company.

The methodology used to create resources of these two types is also different. While the partner administrator or channel manager creates a new partner resource through the Oracle Fusion Partner Management applications, internal resources are added using the Manage Users, Hire Employee, or Import Person and Organization task.

Another difference between partner resources and internal resources is that partner resources cannot access the Resource Directory while internal resources can.

Can I create an employee or contingent worker resource?

No. You can only identify existing employees and contingent workers as resources in the Manage Resources task, but you cannot create a new employee or contingent worker in the Manage Resources task.

You can create an employee or contingent worker using Manage Users task, Hire Employee task, or Import Person and Organization task.