Creating CRM Resources in Oracle E-Business Suite (Part 1 of 2)

CRM Resources are required for a variety of purposes in Oracle E-Business Suite (R12 and 11i). Here is a simple break down of the steps required to create a complete and functioning CRM Resource for you.
The first step in creating CRM Resources begins with creation of the Person record in Oracle HRMS applications. Once a valid resource has been created (Employee or a Contingent Worker) and given appropriate Job titles, then that worker can be leveraged into the CRM Applications.
Using the Resource Manager function in the CRM Administrator responsibility, the desired Worker can either be manually added or imported to create them as a CRM Resource. This import can be performed in a mass function by grouping workers into common job titles, Organizations or Competencies. During the import, you will be assigning a valid Role Type and Role to the imported resource.
Role Types are used to Group common roles together such as Field Sales, Support, Marketing and Field Service Representative. They are then further identified by assigning a working role to the Resource such as Call Center Supervisor, Collections Agent, Credit Analyst, or Sales Manager. Resources can be given numerous Role Types and associated Roles to apply against varying job tasks they perform within the company.
You can now group similar resources together within a Resource Group and if needed identify a different Role Type and Role for their position in that Group. For example Ron Burgundy may be a Salesman in the Southern California region. His primary Role Type is Field Sales with a role of Sales Agent. His assignment to the Southern California Group may be to a Role Type of Field Sales with a Role of Lead Sales Representative.
Resources may also be assigned to a higher grouping mechanism call a Team. They may be given a Different Role Type and Role for that assignment as well. For example Ron may belong to the New Product Launch Team with a Role of Field Sales and a role of National Sales Representative.
CRM Resources must also be given HTML Roles for accessing CRM HTML Forms. Using the CRM HTML Administration Responsibility, you must now search based upon a User ID. You then need to assign appropriate HTML Roles to the user such as IBE_SALESREP_ROLE or OKR_CONTRACTS_MANAGER. These assignments must be present in order for a user to gain aces and perform functions within various CRM HTML forms in Sales, Service and Marketing responsibilities.
Now that we have fully created and properly assigned Roles and HTML Roles to a resource, assigned them to Groups and Teams, We now begin the use of the resources in the various Oracle CRM Application modules.
Our next blog on this topic will describe the use in both Sales and Service applications and the interaction with base E-Business Suite CRM, including the resources created using the steps above!