Wednesday, September 8, 2010
Tuesday, September 7, 2010
Oracle CRM Service - Elementary
In Oracle CRM modules, apart from creating username it's important you create them as Resource and assign a role.
Step1. Create a new employee
(R) HRMS Manager
(N) People --> Enter and Maintain
Step 2. Create applications username
(R) System Administrator
(N) Security --> User --> Define
Step 3. Import Resource into CRM
(R) Manager
(N) Setup --> CRM Foundation --> Resource Manager --> Maintain Resources --> Import Resources
Step 4. Assign required role(s) to the resource
Navigation same as Step 3 and go to tab 'Roles'.
--------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------
The CRM 'Service Suite' components:
There are three components to this flow:
--------------------------------------------------------------------------------------------------------------------------
Issue: User Maintenance link under CRM HTML Administration throws message, "You don't have sufficient privileges to view this page."
Sol: Login with SYSADMIN account and assign JTF_SYSTEM_ADMIN_ROLE to your id.
Issue: When creating a new Service Request (SR), it throws error message, "The user-to-resource link has not be setup correctly."
Sol: Either the user is not yet defined as resource or User Name is not defined (or re-define) in the Resource Details screen (under Maintain Resources)
Step1. Create a new employee
(R) HRMS Manager
(N) People --> Enter and Maintain
Step 2. Create applications username
(R) System Administrator
(N) Security --> User --> Define
Step 3. Import Resource into CRM
(R)
(N) Setup --> CRM Foundation --> Resource Manager --> Maintain Resources --> Import Resources
Step 4. Assign required role(s) to the resource
Navigation same as Step 3 and go to tab 'Roles'.
--------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------
The CRM 'Service Suite' components:
- TeleService module
- Depot Repair module
- iSupport module
- eMail Center module
- Preventive Maintenance module - uses CMRO (Complex Maintenance, Repair and Overhaul) to create SR and tasks.
- Service Contracts module
- Install Base module
- Knowledge Management
- Common Application Components like Territory Manager, Task Manger, Resource Manager.
--------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------
Process Flows:
Service Request to Resolution
There are three components to this flow:- Service Call Intake (SR created via TeleService, iSupport, eMail Center)
- Execution Channel
- Service Execution
The Execution Channel has three alternatives:
- Technical Support
- Field Service
- Depot Repair
--------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------
Sol: Login with SYSADMIN account and assign JTF_SYSTEM_ADMIN_ROLE to your id.
Issue: When creating a new Service Request (SR), it throws error message, "The user-to-resource link has not be setup correctly."
Sol: Either the user is not yet defined as resource or User Name is not defined (or re-define) in the Resource Details screen (under Maintain Resources)
AOL - Elementary
- Use the 'Organization Access' [R -> System Administrator] form to map responsibility with access to one or more org. Backend --> org_access_v
- a
- Flexfields:
Key Flexfields (KFF) --> Owned by one application, used by many. Required to setup, usage is optional. Support intelligent keys.
Descriptive Flexfields (DFF) --> Associated with tables in specific application. Setup optional. No intelligence, stores additional info.