Professional Documents
Culture Documents
Br100 Oracle Teleservice
Br100 Oracle Teleservice
Author:
Ashwin Pingali
Creation Date:
Jun. 27, 05
Last Updated:
Aug. 23, 11
Document Ref:
TSSetup - Cheetah
Version:
1.0
Approvals:
<Approver 1>
<Approver 2>
Document Control
Change Record
Date
Author
Version
Change Reference
27-Jun-05
Ashwin Pingali
1.0
No previous document
Reviewers
Name
Position
Distribution
Copy
No.
Name
Location
1
2
3
4
Library Master
Project Library
Project Manager
Note To Holders:
If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document control
purposes.
If you receive a hard copy of this document, please write your name on the
front cover, for document control purposes.
EVAL Project
File Ref: 65865541.doc
)
3 of
Contents
Document Control.......................................................................................ii
Application Set Up Control Sheet - Teleservice...........................................1
JTF: Setup Note Types.................................................................................4
JTF: Mapping Note Types to a Source.........................................................5
JTF: Profile Options......................................................................................6
JTF: Define Roles........................................................................................8
JTF: Define Role Types...............................................................................9
JTF: Create HR Employee with Correct Responsibility..............................10
JTF: Import Resources..............................................................................15
JTF: Define Task Types.............................................................................18
JTF: Define Task Statuses.........................................................................19
JTF: Define Task Priorities........................................................................21
JTF: Define Task Templates......................................................................22
JTF: Define Territories Setup Qualifiers.................................................23
JTF: Setup Territories...............................................................................24
JTF: Setup Territory Types........................................................................27
JTF: DEFINE JTFBRM User..........................................................................28
JTF: Start the Workflow Background Process...........................................29
JTF: Start the Business Rule Monitor........................................................30
JTF: Define Escalation Levels...................................................................31
JTF: Define Escalation Reasons................................................................32
JTF: Define Contact Types........................................................................33
JTF: Define Reference Types....................................................................34
JTF:
Define Escalation Statuses.......................................................................35
CSS: Define Lookups................................................................................36
AR: Receivables Lookups.........................................................................40
CSS: Setup Service Request Statuses......................................................41
CSS: Setup Service Request Types..........................................................43
CSS: Setup Service Request Severities....................................................45
CSS: Setup Service Request Urgencies....................................................46
CSS: Setup Service Request Problem Codes............................................47
CSS: Setup Service Request Resolution Codes........................................48
CSS: Setup Message Action Requests......................................................49
CSI: Setup Installed Base Customer Product Status.................................50
CSI: Setup Installed Base Customer Product Types.................................51
CSI: Setup Installed Base System Types..................................................52
CSI: Setup Installed Base Order Transaction Types.................................53
CSI: Setup Installed Base Split Product Reason.......................................55
CSI: Setup Installed Base Business Processes.........................................56
CSS: Profile Options.................................................................................57
CSC: Define Profile Rating........................................................................60
CSC: Setup Customer Profiles..................................................................61
CSC: Define Relationship Plan Groups.....................................................69
CSC: Define Relationship Plans................................................................71
CSC: Enable Relationship Plans...............................................................73
AR: Define Territory Key Flexfield............................................................74
AR: Define Sales Tax Location Key Flexfield............................................75
SA: Profile Options...................................................................................76
Open and Closed Issues for this Deliverable.............................................79
Open Issues.........................................................................................79
Closed Issues.......................................................................................79
Doc Ref:
Machine:
Workflow
SubWorkflow Name
Setup Task
JTF
JTF
JTF
Responsibility
Due Date
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Profile Options
Ashwin Pingali
01-jul-05
JTF
Define Roles
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
HR
Ashwin Pingali
01-jul-05
JTF
Import Resources
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
JTF
Setup Territories
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
(v. )
QA Responsibility
QA Due
Date
Signature Approval
3 of
Workflow
SubWorkflow Name
Setup Task
JTF
JTF
JTF
JTF
JTF
Define Escalation
Reasons
JTF
Responsibility
Due Date
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
JTF
Ashwin Pingali
01-jul-05
JTF
Define Escalation
Statuses
Ashwin Pingali
01-jul-05
CSS
Define Lookups
Ashwin Pingali
01-jul-05
AR
Receivables Lookups
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
CSS
Ashwin Pingali
01-jul-05
QA Responsibility
QA Due
Date
Signature Approval
Workflow
SubWorkflow Name
Setup Task
CSI
CSI
CSI
CSI
CSI
CSI
CSS
Responsibility
Due Date
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Ashwin Pingali
01-jul-05
Profile Options
Ashwin Pingali
01-jul-05
CSC
Ashwin Pingali
01-jul-05
CSC
Ashwin Pingali
01-jul-05
CSC
Ashwin Pingali
01-jul-05
CSC
Ashwin Pingali
01-jul-05
CSC
Ashwin Pingali
01-jul-05
CSC
Ashwin Pingali
01-jul-05
AR
Ashwin Pingali
01-jul-05
AR
Ashwin Pingali
01-jul-05
SA
Ashwin Pingali
01-jul-05
QA Responsibility
QA Due
Date
Signature Approval
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define note types lookups.
User Name
Application
Description
Access Level
JTF_NOTE_TYPE
Note Types
CRM Foundation
Extensible
Code
Meaning
Description
Tag
Effective Date
From
Effective Date To
Enabled
(Seeded?)
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to map note types to a source.
Note Type
(v. )
End Date
(Seeded?)
3 of
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set system profile values.
Site
Application
Responsibility
User
Profile
Site
Application
Responsibility
User
Escalation:Default Escalation
Level
Escalation:Default Reason Code
Escalation: Default Document
Type
Escalation:Default Reference
Type
Escalation:Default Contact Type
Escalation:Default Notify (Y/N)
Escalation:Default Customer
Contact Point
Escalation:Default New Note
Type
(v. )
3 of
Roles
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Roles
Code
Name
Role Type
Membe
r
Lead
Active
Jobs
Code
Job Name
Admin
Manager
Seeded
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
User Name
Application
Description
JTF_RS_ROLE_TYPE
JTF_RS_ROLE_TYPE
CRM Foundation
JTF_RS_ROLE_TYPE
Code
Meaning
(v. )
Description
Tag
Access Level
Effective Date
From
Effective Date
To
Enable
d
3 of
Employee
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
<Business Area>
<Priority (H, M, L)>
Description: You can use this form to create employees in Human Resources. (Optional)
Name
Last
First
Title
Prefix
Suffix
Middle
Gender
Type
Latest Hire Date
Date First Hired
D
O
Date:
<Date>
Process Owner:
<Process Owner>
Identification
Social Security
Employee
Applicant
Effective Dates
From
To
tab
Personal
Birth Date
Age
Nationality
Status
Mail To
Email
Date Last Verified
Registered Disabled
tab
Employment
Ethnic Origin
I-9 Status
Visa Type
I-9 Expiration
Veteran Status
New Hire
Child Support Obligation
Exception Reason
Opted for Medicare
tab
Office Location
Office
Location
Mailstop
tab
Exists
Applicant Resume
Last Updated
Hold Application Until
Doc Ref:
tab
Background
Background Checked
Date Checked
tab
Rehire
Recommendation
Reason
tab
Further Name
Honors
Preferred Name
Previous Last Name
tab
Medical
Blood Type
tab
Other
Availability Schedule
Student Status
Full-Time Availability
Correspondence Language
On Military Service
Date of Death
Second Passport Exists
Doc Ref:
Selection Criterion
Business Area:
Control Number:
Priority(H, M, L):
<Business Area>
<Control Number>
Job Title
Competencies
Comp Level : Max
Min
Name
Scale
Scale Level
Confirm that you are searching for the right Person! Then press the SearchButton!
Date:
<Date>
Process Owner:
<Process Owner>
Search
Search Results
Select
Category
Create Resource
Form
Name
Default Values
Default Values
Start Date
Managing
Employee
Role
Role Start Date
End Date
Role Type
Role End Date
OK
Form
Name
Selected Resources
Selected Resources
Select
Category
Name
Name
Role Type
Role
Comments
Save Resource
(v. )
3 of
Tasks
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define task types which are used in the creation of tasks.
Task Types
Type
Workflow
Rul
e
Effective
Dates From
Effective
Dates To
Effort
UOM
Task Workflow
Task Workflow
Descrioption
Resource Requirements
Name
Required Units
Enabled
Effort
Duration
Notificatio
n
Schedulab
le
Billable
Privat
e
Seede
d
Task Status
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: Use this form to define task statuses, which are used in the creation of tasks
Task Status
Status
Description
Status
On Hand
Approved
From
Completed
Canceled
To
Deletion Allowed
Usage
Assigne
d
Working
Scheduab
le
Accepte
d
Rejected
Seeded
Define Transition
(v. )
3 of
tab
Rule
Source
Application
Rule Name
Current State
tab
Next State
Responsibility
Responsibility Name
Rule Name
Task Priority
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Task Priority
Priority
Descritio
n
Importance
Effective Dates To
Seeded
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Number
Type
Status
Priority
Description
Privat
e
Multi
Book
Billabl
e
Publish
Restrict
Close
Holida
y
Mileston
e
Setup Qualifier
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to enable territory setup qualifiers.
Find Qualifiers
Usage
Enabled
Disabled
All
FIND
Qualifier
Enabled
Description
Transaction Type
Organization
Territory Details
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set up the territories. Create territory types first, if needed.
tab
Overview
Field
Value
Organisation
Field
Template
End Date
Usage
Category - Standard
Name
Description
Category Template
Start Date
Category Escalation
Rank
Parent
Escalation
Type
Number of Winners
Transaction Types
Freeze
tab
Transaction Qualifiers
Value
Name
Type
Mode
Overlap Allowed
Value Set
tab
Resource Qualifiers
Name
Type
Mode
tab
Name
Value From
Value To
Value Set
Group
Role
Resources
Type
tab
Name
Sub-Territories
Description
Start Date
End Date
Rank
Territory Type
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Date>
Process Owner:
<Control Number>
<Priority (H, M, L)>
Description: This form is used to set up the Territory Types, prior to setting up territories.
Territory Type
Field
Value
Field
Transaction Types
Transaction Types
Transaction Qualifier
Name
Transaction Type
Overlap Allowed
Value
<Process Owner>
Users
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Users
User
Name
Description
Password
Password
Expiration
JTFBRM
Escalation
Management Workflow
User
ORACLE
None
tab
Responsibilities
Responsibilities
Workflow Administrator
Workflow Uer
Effective Date
From
18-JUL_2001
18-JUL_2001
Effective Date
To
Perso
n
Custom
er
Supplie
r
Fax
Effective
Date From
18-JUL-2001
Effective Date
To
Submit Request
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
Submit the following workflow background items from the above navigation path.
<Process Owner>
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
<Business Area>
<Priority (H, M, L)>
Date:
<Date>
Process Owner:
<Process Owner>
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Type
User Name
Application
Description
Access Level
JTF_TASK_ESC_LEVEL
Escalation Levels
CRM Foundation
Escalation Levels
Extensible
Code
Meaning
Description
Tag
Effective Date
From
Effective Date To
Enabled
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define Escalation Reasons Lookups.
User Name
Application
Description
Access Level
JTF_TASK_REASON_CODES
Escalation Reasons
CRM Foundation
Escalation Reasons
Extensible
Code
Meaning
Description
Tag
Effective Date To
Enabled
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define Contact Types Lookups.
User Name
Application
Description
Access Level
JTF_TASK_CONTACT_TYPE
Contact Types
CRM Foundation
Contact Types
Extensible
Code
Meaning
Description
Tag
Effective Date To
Enabled
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define Reference Codes for the Task Lookups.
User Name
Application
Description
Access Level
JTF_TASK_REFERENCE_COD
ES
CRM Foundation
Extensible
Code
Meaning
Description
Tag
Effective Date To
Enabled
Task Status
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Task Status
Status
Description
Status
On Hand
Approved
From
Completed
To
Usage
Task
Status
Assigne
d
Cancelled
Closed
Deletion Allowed
Working
Seeded
Schedula
ble
Accept
ed
Rejected
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define customer care lookups.
Code
Meaning
Description
Tag
Effective Date
To
Enable
d
Type
User Name
Application
Description
Access Level
Code
Meaning
Description
Tag
Effective Date
To
Enable
d
Meaning
Description
Tag
Effective Date
To
Enable
d
Type
User Name
Application
Description
Access Level
Code
(v. )
3 of
Type
User Name
Application
Description
Access Level
Code
Meaning
Description
Tag
Effective Date
To
Enable
d
Type
User Name
Application
Description
Access Level
Code
Meaning
Description
Tag
Effective Date
To
Enable
d
Wincor-Nixdorf Process:
Customer Support
Business Area:
Control Number:
Priority(H, M, L):
Date:
Service
<Control Number>
05-DEC-2000
Process Owner:
<Process Owner>
Type
User Name
Application
Description
Access Level
Code
Meaning
Description
Tag
Effective Date
To
Enable
d
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define service request statuses.
Close
d
Start
Date
End
Date
Predefin
ed
Text Color
Description
Disallow
Request
Update
Disallow
Task
Update
Disallow
Charge
Update
Disallow
Owner
Update
Disallow
Product
Update
Disallow
Charge
Transitions
(v. )
3 of
Rules
Source
Rule Name
Current State
Next State
Responsibility
Responsibility Name
Rule Name
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Business Process
Start Date
Type
Auto Launch
Workflow
Abort Workflow on
Close
Type
Transaction Group
End Date
Description
Workflow
Web Entry
Start Date
End Date
[ ]
Related Statuses
Related Statuses
Type =
Status
Description
Start Date
End Date
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Importance
Level
Description
Start Date
End Date
Defect Severity
Text Color
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define service request urgencies.
Importance
Level
Description
Start Date
End Date
Defect Severity
Text Color
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set up the list of service request problem codes.
Type
User Name
Application
Description
Access Level
User
Extensible
System
Code
Meaning
Description
Tag
Effective Dates
To
Enabled
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set up the list of service request solution codes.
Type
User Name
Application
Description
Access Level
User
Extensible
System
Code
Meaning
Description
Tag
Effective Dates
From
Effective Dates
To
Enabled
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set up the list of message action request codes.
Type
User Name
Application
Description
Access Level
User
Extensible
System
Code
Meaning
Description
Tag
Effective Dates
From
Effective Dates To
Enabled
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Date>
Process Owner:
<Control Number>
<Priority (H, M, L)>
Description: Use this form to define customer product status.
Status
Cancele
d
Description
Status Description
Terminat
ed
Status Change
Allowed
Service
Allowed
<Process Owner>
Requests
Allowed
Predefined
Effective Dates To
Descriptio
n
Effective
Predefined
Oracle Service
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define your call follow-up type codes.
Type
User Name
Application
Description
Access Level
User
Extensible
System
Code
Meaning
Description
Tag
Effective Date
From
Effective Date To
Enabled
Oracle Service
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
Date:
<Business Area>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define your call system type codes.
Type
User Name
Application
Description
Access Level
User
Extensible
System
Code
Meaning
Description
Tag
Effective Date To
Enable
d
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define your order transaction types.
Transaction Types
Transaction Type
New CP
-Status
Installed
Base
Description
Effective Date From
Effective Date To
[
Seeded
Flag
Billing Types
Installed CP -Status
Name
Description
(v. )
3 of
Oracle Service
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Date>
Process Owner:
<Control Number>
<Priority (H, M, L)>
Description: You can use this form to define your split product reason types.
<Process Owner>
Type
User Name
Application
Description
Access Level
User
Extensible
System
Code
Meaning
Description
Tag
Effective Date To
Enable
d
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Business Process
Name
Description
Order Type
Depot
Repair
Service
Request
Field
Service
Org
Effective Dates
Transactions
Transaction Type
From
(v. )
To
3 of
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set system profile values.
Profile
Service: Item Flexfild (Service)
Service: Item Flexfild (Product)
Service Auto Laungh Workflow
Service: Default Service Request
Type
Service: Default Service Request
Severity
Service: Default Service Request
Urgency
Service: Default Service Request
Owner Type
Service: Default Service Request
Owner
Service: Default Service Request
Owner Status
Site
Application
Responsibility
User
Profile
Site
Application
Responsibility
User
(v. )
3 of
Profile
Service: Default Asignee on the
Service Request Tasks tab
Client Timezone
Server Timezone
Service Knowledge Base URL
ASO Product Organization
Site
Application
Responsibility
User
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set profile rating codes.
CSC_PROF_RATINGS
User Name
Application
Customer Care
Description
Access Level
User
Code
Meaning
Description
Tag
Effective Date
To
Enable
d
Business Area:
Control Number:
Priority(H, M, L):
<Business Area>
<Control Number>
<Priority (H, M, L)>
Description: Use this form to setup customer profiles.
tab
Date:
<Date>
Process Owner:
<Process Owner>
Profile Variables
Name
Code
Pre Define
Active
From
To
(v. )
3 of
Description
Select
Currency
From
Where
Other
Sql Statement
tab
Drilldown
Variable
Pre Defined
Description
Drilldown Module
Drilldown Column
Table
Alias
New
For
m
Name
Name
Description
Object Code
Seeded
From Task
Start Date
End Date
Function Name
Parameters
Url
LOV Titles
Window
Name
Details
Select Statement
Usage
Object User
Object User
Seeded
Alias
Description
Name
Display
Name
Columns
ID
Show
tab
Profile Checks
Name
Pre Define
Active
From
To
Code
Description
Description
Type
Variable
Data Type
Format Mask
Rules
Operator
Group
Variable
Condition
Expression
Variabl
e
Grou
p
Ratings
Lower
Threshold
Upper
Lower
Label
Color
Upper
Label
Color
tab
Profile Groups
Name
Pre Define
Code
Description
Customer Type
Active
From
To
Checks
Profile Checks
tab
Name
Group Checks
Dashboard Groups
Pre Define
Code
Description
Customer Type
Display On Threshold
Active
From
To
Categories
Categories
Dashboard Categories
Checks
Category
Profile Checks
Group Checks
Display On Threshold
Customer Type
Group
tab
Preferences
Module Groups
Module
Doc Ref:
Rating Labels
Rating
Color
Categories
Category
Meaning
Description
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Code
Meaning
Flexfield
Test 1
Test 2
Access Level
Description
Tag
Effective Date
From
Effective Date To
Enabled
[ ]
User
Extensible
System
(v. )
3 of
New Plan
Business Area:
Control Number:
Priority(H, M, L):
<Control Number>
<Business Area>
<Priority (H, M, L)>
Plan Headers
Plan Name
Group Name
Start Date
End Date
Account Level
Description
Plan Type
Template
Custom
Date:
<Date>
Process Owner:
<Process Owner>
Plan Criteria
Profile Check
Operator
Low Value
High Value
tab
Plan Details
(v. )
3 of
Business Area:
Date:
Control Number:
Priority(H, M, L):
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Application
OnInsert
On-Update
Custom1
Custom2
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to define Key Flexfield segements
<Key Flexfield>
Application
Flexfield Title
Oracle Receivables
Territory Flexfield
<Structures>
Title
Description
CUSTOMER_TERRITORY_FLEXFIELD
Freeze Flexfield
Definition
Enable
d
View Name
Segment Separator
Cross-Validate
Segments
Segments
<Segments Summary>
Numbe
r
Name
Window Prompt
Column
Value Set
Displaye
d
Enabled
Qualifier Name
Qualifier
Enabled
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Date>
Process Owner:
<Control Number>
<Priority (H, M, L)>
<Process Owner>
Description: Take the seeded data and make sure to compile the structure State.County.City.
<Key Flexfield>
Application
Flexfield Title
Oracle Receivables
<Structures>
Title
Description
Freeze Flexfield
Definition
Enable
d
Segment Separator
Yes
Yes
Period
View Name
Cross-Validate
Segments
Yes
Segments
<Segments Summary>
Numbe
r
Name
Window Prompt
Column
Value Set
Displaye
d
Enabled
Qualifier Name
Qualifier
Enabled
Business Area:
Control Number:
Priority(H, M, L):
Date:
<Business Area>
<Control Number>
<Date>
Process Owner:
<Process Owner>
Description: You can use this form to set system profile values.
Site
Application
Responsibility
User
Profile
Site
Application
Responsibility
User
(v. )
3 of
Profile
Customer Care: User Currency
Code
Customer Care: Critical Customer
Check
Activate Auto Selection of
Resources
Activate Contracts Preferred
Resources
Activate Installed Base Preferred
Resources
Activate Workflow Name
Site
Application
Responsibility
User
Doc Ref:
Issue
Resolution
Responsibility
Target Date
Impact Date
Resolution
Responsibility
Target Date
Impact Date
Closed Issues
ID
Issue
(v. )
3 of 0