Oracle® Fusion
Applications Customer Data Management Implementation Guide 11g Release 1 (11.1.2) Part Number E20433-02 |
Contents |
Previous |
Next |
This chapter contains the following:
Setting up Resources: Explained
Identifying Resources: Explained
Resource Skills and Resource Assignment: Explained
Resources: How They Work within a Team
FAQs for Define Resource Information
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:
View and modify your profile
View your organization and team membership information
View information related to other organizations and teams
View the profiles of other resources
Communicate with other resources
Setting up resources involves identifying a person as a resource and specifying optional profile details as needed. This is an important step because until you identify users as resources, you cannot assign work objects to them.
While identifying a resource is the only mandatory task in resource setup, you may also need to perform some of the following tasks while setting up resources.
Specify the end date for a resource's engagement with the deploying company
Assign roles to resources
Assign resources to organizations
Assign resources to teams
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 skills help you assign resources to organizations and teams which can best utilize a specific set of skills. For example, if a resource is skilled in a specific technology, product, or business domain, you can assign the resource to teams and organizations that need resources possessing such skills. Use skill-based resource assignment to get the best out of the resources available to the deploying company.
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.
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.
When you delete a resource, the resource is deleted from the Resource Directory and from the organizations and teams with which the resource was associated. It is always best, though, to check a resource's usage and remove the resource from all teams and organizations before deletion from the resource directory.
When you add a resource to an organization, the resource becomes a member of the organization. This positions the resource within the organization hierarchy.
Organization membership information is part of the publicly visible details of a resource profile. This means that a resource's organization membership and reporting structure are visible to all active resources within the organization.
If you assign the entire organization to a resource team, all member resources are automatically assigned to the team. This information also becomes part of the resource's publicly visible profile.
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.
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.
When resources quit, their status is set to inactive. This automatically removes these resources from all organizations and teams in the deploying company, and no new work objects can be assigned to them.
To identify specific employees, contingent workers, or partner contacts as resources, you need to search for them and enable them as resources. Once these new resources have been identified, you can assign them to organizations and teams as needed.
Oracle Fusion CRM or MDM Application Administrators can use the Manage Users setup task to create new employees or contingent worker users. New employees or contingent workers can also be identified as resources similarly.